Document scanner product roadmap and Gitea workflow
This commit is contained in:
@@ -4,6 +4,8 @@ Progress on the approved scanner/OCR rework. See ADR-007/008/009/010 in
|
||||
[DECISIONS.md](DECISIONS.md) for the decisions behind these. For the current
|
||||
live automation runbook, see
|
||||
[AUTOMATION_LIVE_SCAN.md](AUTOMATION_LIVE_SCAN.md).
|
||||
For the next result/inventory product phase, see
|
||||
[scanner-results-inventory-roadmap.md](scanner-results-inventory-roadmap.md).
|
||||
|
||||
## Current Scanner Status
|
||||
|
||||
@@ -35,6 +37,10 @@ Current status after the 2026-07-09 merge to `main`:
|
||||
equipped characters (`Citlali`, `Linnea`), unlocked artifacts reported
|
||||
`locked: false`, a visibly locked artifact reported `locked: true`, and a
|
||||
bounded auto-scan persisted the locked/equipped state.
|
||||
- Current speed is acceptable for the next product phase. The next work should
|
||||
prioritize correct artifact content extraction, a minimal live result rail,
|
||||
scanned artifact inventory, detail evaluation, and review-safe value scoring
|
||||
before another broad speed pass.
|
||||
|
||||
## Done (implemented, unit-tested, build green)
|
||||
|
||||
@@ -223,7 +229,26 @@ Current status after the 2026-07-09 merge to `main`:
|
||||
pixels because Electron's native bitmap channel order was ambiguous in live
|
||||
captures.
|
||||
|
||||
## Remaining — needs the live environment or a UI pass
|
||||
## Next product phase - result rail and inventory
|
||||
|
||||
The next implementation pass is planned in
|
||||
[scanner-results-inventory-roadmap.md](scanner-results-inventory-roadmap.md).
|
||||
Summary:
|
||||
|
||||
1. Add result data contracts that preserve extraction confidence separately from
|
||||
artifact value score.
|
||||
2. Rework the scan view into screenshot/preview plus a compact right-side live
|
||||
result rail.
|
||||
3. Add a scanned artifact inventory menu with minimal list/grid rows and
|
||||
score/review pills.
|
||||
4. Add click-through artifact detail with screenshot/crops, parsed fields, OCR
|
||||
confidence, value reasons, and review state.
|
||||
5. Add upgrade projection later as a detail-only feature with worst/middle/best
|
||||
cases and explicit uncertainty.
|
||||
6. Defer the full screenshot queue/worker pipeline until the result/inventory
|
||||
contracts are stable or timing evidence shows the current loop is the blocker.
|
||||
|
||||
## Remaining - needs the live environment or a UI pass
|
||||
|
||||
These cannot be finished/validated without Genshin running at the user's
|
||||
resolution or without UI work best tested live:
|
||||
|
||||
Reference in New Issue
Block a user