Document scanner product roadmap and Gitea workflow

docs/DECISIONS.md

@@ -17,6 +17,7 @@ This document contains Architecture Decision Records.
 | ADR-009 | Resolution-anchored layout profiles and OCR preprocessing over color detection | Accepted | 2026-07-05 |
 | ADR-010 | Elevated dev runner and bounded live automation probes | Accepted | 2026-07-07 |
 | ADR-011 | Quality-gated Inventory Kamera comparison before OCR default changes | Accepted | 2026-07-07 |
+| ADR-012 | Separate live scan results, artifact inventory, and value evaluation | Accepted | 2026-07-09 |
 
 ## ADR-001: Build A Local Electron App First
 
@@ -339,3 +340,60 @@ winner and a complete `current` vs. `ik-traineddata` comparison.
 - The validated `:wait` scan scripts are acceptable for manual post-UAC startup;
   non-waiting scripts remain useful when automation should fail fast.
 - The goal remains open until the 100-artifact qualified comparison is captured.
+
+## ADR-012: Separate Live Scan Results, Artifact Inventory, And Value Evaluation
+
+### Status
+
+Accepted
+
+### Context
+
+The visible-inventory scanner baseline is fast enough for the current product
+phase. The next user value comes from better artifact content extraction and a
+clearer surface for scanned artifacts, not from another broad speed pass.
+
+The scan page currently has more diagnostic/result detail than the operator
+needs during a live scan. Showing every stat, confidence value, and evaluation
+while the scanner is running makes the main workspace noisy and increases the
+risk that a user treats uncertain OCR as a final artifact judgment.
+
+The desired product flow is:
+
+- left side: screenshot/preview,
+- right side: compact live list of finished artifact results,
+- later menu item: browsable scanned artifact inventory,
+- click-through detail: screenshot, parsed stats, OCR confidence, evaluation
+  reasons, and upgrade projection.
+
+### Decision
+
+Adopt a split scan/result/inventory model:
+
+- The active scan page shows the latest screenshot/preview and a compact live
+  result rail.
+- The live rail shows only scan number, artifact name or compact fallback,
+  artifact value score `0-100`, and a result pill after evaluation has finished.
+- Extraction confidence and artifact value are separate data concepts. A low
+  confidence read becomes `Review`; it must not be silently displayed as a
+  normal weak artifact.
+- Debug stats, raw OCR, confidence breakdowns, and detailed evaluation belong in
+  diagnostics, scan summary, or artifact detail.
+- Add a scanned artifact inventory view for browsing, filtering, sorting, and
+  opening details.
+- Add artifact detail evaluation before promoting broad recommendations.
+- Add upgrade projection only as a detail-level feature, with worst/middle/best
+  projected value scores and clear uncertainty labeling.
+- Keep the producer/consumer screenshot queue as a later implementation phase:
+  one game-control worker may click/scroll/capture, while OCR/parse/evaluation
+  workers can process bounded queued jobs once the UI/data contracts are stable.
+
+### Consequences
+
+- The scan page becomes calmer and more task-focused.
+- The app can surface useful artifact outcomes without hiding OCR uncertainty.
+- Inventory and detail views become the natural place for richer analysis.
+- Recommendation work has a cleaner dependency chain: trusted scans, compact
+  results, artifact inventory, detail evaluation, then build recommendations.
+- Speed work remains possible, but it is secondary unless measured timings show
+  a real regression.