Document scanner product roadmap and Gitea workflow

This commit is contained in:
AzuTear
2026-07-09 10:28:17 +02:00
parent eb666febb6
commit 28d60eb915
9 changed files with 558 additions and 19 deletions
+33
View File
@@ -42,6 +42,21 @@
- [ ] Desktop viewport is checked manually.
- [ ] `npm run build` passes.
## Scan Results And Inventory UX
- [ ] The scan page keeps preview, Stop/status, and the live result rail visible without page-level scrolling.
- [ ] The live rail shows finished artifact rows only, not intermediate OCR/debug state.
- [ ] Each live row has scan number, artifact name or compact fallback, value score, and a short status pill.
- [ ] Extraction confidence and artifact value remain separate in the data model.
- [ ] Low-confidence or conflicting reads show `Review` instead of a normal weak/strong value decision.
- [ ] Duplicate state is represented separately from artifact quality.
- [ ] The artifact inventory view can browse stored scan results without opening diagnostics.
- [ ] Inventory filters/sorting cover review, score, set, slot, equipped, locked, and newest scan where data exists.
- [ ] Artifact detail shows screenshot/crop, parsed fields, OCR confidence, parser notes, value reasons, and review state.
- [ ] Upgrade projection, if shown, is labeled as a projection and includes worst/middle/best cases.
- [ ] Unit tests cover score/status derivation and projection edge cases when those modules change.
- [ ] Scanner safety rules and existing quality gates are unchanged.
## Parser Or Scoring Change
- [ ] Known-good OCR samples still parse correctly.
@@ -56,3 +71,21 @@
- [ ] App starts outside browser preview.
- [ ] Smart Capture bridge is available.
- [ ] No generated debug artifacts are included accidentally.
## Git Merge And Gitea Push
- [ ] `git status --short --branch` is checked before switching branches,
committing, merging, or pushing.
- [ ] Work is committed on the intended feature branch before merging into
`main`.
- [ ] Merge into `main` uses fast-forward when possible, or a deliberate merge
commit when the history requires it.
- [ ] `main` is clean before push except for explicitly ignored or deliberately
untracked local files.
- [ ] `git remote -v` points to the intended Gitea remote before pushing.
- [ ] Gitea HTTPS credentials are stored through Git Credential Manager, not in
repository files or remote URLs.
- [ ] If authentication fails, refresh the credential using
[GITEA_AUTH.md](GITEA_AUTH.md), then rerun the same `git push`.
- [ ] After push, `git status --short --branch` shows `main...origin/main`
without ahead/behind drift.