jobtrackingapp/docs/redesign/phase-6/EXECUTION_PLAN.md

Phase 6 execution plan

Goal: Finish the approved design/UX review with bounded shared repairs, fresh regression evidence and a reconciled Phase 7 handoff. Architecture: Retain MUI/Emotion, React Router, existing theme/layout/state providers and domain owners. Application chrome changes must preserve document geometry, source/override history, frozen packages and authorization. Authority: The owner's 2026-10-11 P6-00–P6-05 instructions and original plan. The historical P6-00–P6-06 proposal is superseded by the owner's six checkpoints; prior audit evidence remains available.

Entry and constraints

Fetched development HEAD/remote: 9d6d29dba4733778e478909d4ff74a25409b3115, codex/ui-redesign-phase4. Seven pre-existing modified files are retained: company dialog + tests, language provider/translations/toast + tests and responsive audit. No reset/stash/discard. Phase 5 final implemented-scope decision is CONDITIONAL GO at 9528504866054da10e20d5196e65de536c4c9499 (1,033 backend / 498 frontend / 148 browser; separate lanes remain separate). Production stays NO-GO. Do not implement Phase 7/8, qualify models, enable P5-13 or push main.

Checkpoints

• P6-00: Review Phase 3/4/5 records, all 57 original PRES contracts and actual source; record surface/state coverage, prioritized findings, preserved dirty intake and baseline. Audit pushed at 7da083c, remote=HEAD.
• P6-01: Shared semantic/contrast/tab associations verified; final521 unit cases and4 native panel cases pass. Pushed a94ea0a, remote=HEAD; full native cross-route acceptance follows in P6-05.
• P6-02: Verify navigation/query/history/source/override and save/retry workflows; finish retained company-dialog error feedback and language persistence feedback with localized tests and native HTTP readback. Review approved AI purpose/provenance/review/conflict patterns without activating withheld work. Commit/push.
• P6-03: Collect EN/Bokmål, light/dark, 320–wide desktop, orientation, keyboard, zoom/reflow and all-enabled axe evidence. Triage every remaining violation/incomplete category; inspect representative screenshots. Retain M01–M13 and physical-device requirements. Commit/push.
• P6-04: Record production bundle bytes and reproducible native route/data/long-CV performance, requests, long tasks/CLS and memory where tooling supports them. Audit shared consumers and O(N) scaling; optimize only a demonstrated bounded cause. Do not invent budgets. Commit/push measured findings.
• P6-05: Run fresh full frontend/backend/browser/sidecar/security/HTTP/rendering lanes, explain count changes, reconcile 57 groups, record secret/link/whitespace/build evidence and every commit/push. Report independent Phase 6, production and Phase 7 decisions; prepare migration order and mandatory dependencies. Commit/push final acceptance.

Review focus

Persisted language failures must not silently claim account success; modal save failures must remain discoverable with draft retained. Tabs must name/own visible panels on desktop and mobile. Heading/contrast fixes must not change paper rendering. Navigation/filter improvements must keep query membership, Back and keyboard focus. Finite browser/axe evidence must never be described as human screen-reader or production qualification.

Unavailable operator evidence is documented and independent work continues. All native browser lanes run serially after API Release build and the final UI build to avoid apphost locks and stale exports. Each completed checkpoint is validated and pushed without force; successor ledger rows record hashes to avoid self-reference.