Prepare scanner branch for merge

2026-07-09 08:44:50 +02:00
parent f791d1464c
commit 8b73c01e46
69 changed files with 6700 additions and 3773 deletions
@@ -11,10 +11,13 @@ This document defines project engineering standards.
 ## File Organization

 - Keep Electron OS integration in `electron/`.
+- Keep Electron `main.ts` as composition/wiring. Move durable window, file, helper, capture, OCR, or dev-control responsibilities into named modules under `electron/`.
 - Keep React components in `src/`, with extraction when `App.tsx` becomes hard to review.
+- Keep feature controller hooks small enough to review. If a hook owns persistence, import/export, entry choreography, scan-loop orchestration, and UI state at once, split those concerns into feature-local hooks or services.
 - Keep pure domain logic in `src/lib/`.
 - Keep shared contracts in `src/types/`.
 - Keep generated outputs in `dist/`, `dist-electron/`, and `outputs/`.
+- Keep `src/styles/global.css` as the stylesheet entrypoint. Put broad app styles in `base.css` and dev/diagnostic-only styling in `diagnostics.css` unless a more specific style module is introduced.

 ## UI Rules

@@ -30,6 +33,7 @@ This document defines project engineering standards.
 - Confidence and raw OCR details must remain inspectable.
 - Heuristics should fail safely into unknown fields or review notes.
 - Do not add irreversible game actions.
+- Keep auto-entry choreography separate from scan-loop execution. Entry code may navigate to a readable artifact detail state; loop code should process verified grid targets.

 ## TypeScript Rules