cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

feat(ui): establish semantic colors and focus foundation

Browse Source
This commit is contained in:
cesnimda
2026-09-11 09:04:55 +02:00
parent f696f23fc5
commit 115441a409
26 changed files with 1689 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/redesign/phase-2/TRACEABILITY.md
+2 -2
View File
@@ -1,6 +1,6 @@
# Redesign traceability
Successor planning checkpoint: [Phase 3 impact matrix and architecture](../phase-3/PRESERVATION_IMPACT_MATRIX.md). It maps all 57 contracts to proposed destinations/validation, without changing their requirements or claiming implemented/visual parity. Phase 4 has not started.
Successor planning checkpoint: [Phase 3 impact matrix and architecture](../phase-3/PRESERVATION_IMPACT_MATRIX.md). It maps all 57 contracts to proposed destinations/validation, without changing their requirements or claiming implemented/visual parity. The subsequent [P4-01 implementation trace sheet](../phase-4/p4-01/TRACEABILITY.md) links shared semantic/focus changes to executed regression and representative visual evidence; P4-02 has not started.
Phase 2 starts at `2d0f131`. The [preservation matrix](PRESERVATION_MATRIX.md) is the stable baseline: **PRES-E01…PRES-A03**, in the original ledger's groups (not one contiguous numeric range). Old references such as C07 remain valid aliases. Subdivide a later workflow with a suffix, for example `PRES-C07.override-reset`; do not reuse an ID or silently change its meaning.
@@ -55,4 +55,4 @@ Before Phase 4/5 code, require an approved route/preservation plan, targeted reg
- Before migrating shared controls, validate EN/NB × light/dark × desktop/mobile, keyboard focus, error/empty/dirty states and representative loaded data. Real screen reader/touch/reflow tests remain manual.
- Do not label a release healthy until the previously failed CI browser runner is diagnosed and the required pipeline passes. F04 requires actual production ingress evidence.
Future trace sheets must link here. There are **no Phase 3+ implementation commits or visual sign-offs** in this checkpoint.
Future trace sheets must link here. The original Phase 2 checkpoint contains **no Phase 3+ implementation commits or visual sign-offs**. Subsequent implementation evidence is linked above and does not overwrite this historical baseline.