docs: update scanner roadmap after merge

This commit is contained in:
AzuTear
2026-07-09 08:53:57 +02:00
parent c025daa4f1
commit 13fd46c104
5 changed files with 94 additions and 46 deletions
+6 -1
View File
@@ -258,6 +258,10 @@ Current live limitation:
in the current live environment. 3 artifacts/second is not proven; remaining
speed work needs a larger OCR or capture-pipeline change, not more click
tuning.
- The visible-inventory ownership/lock extension is also live-proven in this
environment: equipped footer reads for `Citlali` and `Linnea`, unlocked
`locked: false`, positive locked `locked: true`, and locked/equipped
persistence all passed on 2026-07-09.
## Inventory Kamera Comparison
@@ -359,7 +363,8 @@ Expected bottleneck sequence:
than click timing.
3. Grow the eval corpus with confirmed real review samples before tightening
parser thresholds further.
4. Validate a positive locked-artifact sample.
4. Repeat equipped/locked live samples in later sessions if confidence or UI
behavior changes, but the first positive locked proof has passed.
5. Keep recommendations secondary until scanner quality remains stable across
repeated live sessions.