Document scanner product roadmap and Gitea workflow

docs/CONVENTIONS.md

@@ -22,8 +22,11 @@ This document defines project engineering standards.
 ## UI Rules
 
 - The scan page should prioritize the capture workspace over secondary status content.
+- The active scan view should read as preview plus compact result rail, not as a dashboard of live diagnostics.
 - Details and debug information belong in modals or secondary panels.
 - Avoid long, overfilled cards on scanner pages.
+- Do not collapse OCR/extraction confidence and artifact value into one ambiguous UI state; uncertain reads should be visibly `Review`.
+- Artifact value pills should be short, stable labels backed by deterministic data, with detailed reasons behind click-through detail.
 - The design direction is dark purple fintech glassmorphism with premium, focused controls.
 - Disable buttons when their required data does not exist.
 
@@ -52,3 +55,8 @@ This document defines project engineering standards.
 - Update `docs/PROJECT.md` when product scope changes.
 - Update `docs/ARCHITECTURE.md` when module boundaries or flows change.
 - Add an ADR to `docs/DECISIONS.md` for durable technical trade-offs.
+- Keep workflow/runbook docs linked from `docs/PROJECT.md` so future sessions
+  do not depend on chat history.
+- Do not store tokens, passwords, cookies, or generated credentials in project
+  files. Use Git Credential Manager for Gitea HTTPS credentials; document only
+  the setup path in `docs/GITEA_AUTH.md`.