docs(theme): record deterministic state evidence
This commit is contained in:
@@ -16,7 +16,7 @@ Allowed statuses are `NOT STARTED`, `IN PROGRESS`, `IMPLEMENTED — NOT VERIFIED
|
||||
|
||||
`DONE` requires every applicable acceptance criterion, focused and regression tests, browser/accessibility/theme/mobile checks, tenant and entitlement checks, documentation, migration/rollback evidence, and production verification. Repository-only work that still requires production is at most `VERIFIED LOCALLY`.
|
||||
|
||||
Exactly one implementation item may be `IN PROGRESS`. As of this revision it is **UX-002**.
|
||||
Exactly one implementation item may be `IN PROGRESS`. As of this revision it is **QA-001**.
|
||||
|
||||
## Consolidated dependency order
|
||||
|
||||
@@ -577,11 +577,11 @@ Ordering differences from the suggested list:
|
||||
- **Required tests:** Light/Dark/System, login/logout/refresh/navigation/storage/preference listeners/tabs.
|
||||
- **Required browser verification:** 375/768/1440, light/dark/system, refresh/navigation/two tabs/reduced motion.
|
||||
- **Required production verification:** normal browser smoke after deploy.
|
||||
- **Status:** `IN PROGRESS`.
|
||||
- **Blocker:** none.
|
||||
- **Evidence:** source requirement re-read is next; UX-001 browser storage limitation makes deterministic anonymous preference/refresh behavior the immediate dependency.
|
||||
- **Commit:** none.
|
||||
- **Remaining work:** trace root precedence before changing UI.
|
||||
- **Status:** `IMPLEMENTED — NOT VERIFIED`.
|
||||
- **Blocker:** production and live authenticated multi-user browser environments are unavailable; repository/browser work is complete.
|
||||
- **Evidence:** `docs/verification/ux-002-deterministic-theme-state.md`; V-111–V-113; focused 6/6, full frontend 48/48 suites and 172/172 tests, build, Light/Dark/System/navigation/refresh/two-tab browser checks and 375/768/1440 captures.
|
||||
- **Commit:** `11734ee` (`fix(theme): make preference state deterministic`).
|
||||
- **Remaining work:** live User A/User B preference switching and production browser smoke; retain existing preference keys during rollout.
|
||||
|
||||
### QA-001 — Job-analysis and keyword quality
|
||||
|
||||
@@ -595,9 +595,9 @@ Ordering differences from the suggested list:
|
||||
- **Required tests:** seven specified Norwegian/English/mixed/short/noisy/tech/filler fixtures.
|
||||
- **Required browser verification:** result presentation/empty/error/long Norwegian text at three widths/themes.
|
||||
- **Required production verification:** synthetic analysis comparison; no silent historical rewrite.
|
||||
- **Status:** `NOT STARTED`.
|
||||
- **Status:** `IN PROGRESS`.
|
||||
- **Blocker:** none.
|
||||
- **Evidence:** reported examples not yet reproduced.
|
||||
- **Evidence:** source requirements and deterministic fixture contract are next for complete pipeline/caching trace; PROD-002 fixtures are available.
|
||||
- **Commit:** none.
|
||||
- **Remaining work:** deterministic fix before considering model help.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user