docs(redesign): plan P5-15 acceptance checkpoints

This commit is contained in:
cesnimda
2026-10-09 08:29:16 +02:00
parent 46a0c0c6d2
commit 932b962b90
11 changed files with 937 additions and 2 deletions
+6 -2
View File
@@ -1,5 +1,7 @@
# Phase 5 implementation plan
**Acceptance-planning successor — 2026-10-09:** [P5-15-00](p5-15/README.md) audits the implemented source at `46a0c0c` and defines bounded acceptance checkpoints. It does not start their execution, qualify P5-13 or authorize production. Historical proposal language below is reconciled by linked implementation/readiness successors; all original requirements remain. Every completed logical P5-15 change/evidence checkpoint must be committed, immediately pushed to development, and checked against the remote before continuing. Stop after 00 for owner review.
**Documentation only. No implementation slice is authorized or started by this checkpoint.** Start from `2a2f9e48052c562ef599825458d0d3a6f9f9fc61` on `codex/ui-redesign-phase4`. Each row below is a separately reviewable implementation checkpoint when explicitly requested. Stop after each; never run automatically into the next slice.
Sources: [Phase 3 sequencing](../phase-3/PHASE4_IMPLEMENTATION_PLAN.md), [P4-06 conditional acceptance](../phase-4/p4-06/README.md), [readiness gates](READINESS_GATES.md), [navigation contract](NAVIGATION_MIGRATION.md), [57-contract impact](PRESERVATION_IMPACT.md), [visual acceptance](VISUAL_ACCEPTANCE.md). This plan makes Phase 3 proposals concrete; it does not supersede preserved functionality or turn missing APIs into existing capabilities.
@@ -38,7 +40,7 @@ Sources: [Phase 3 sequencing](../phase-3/PHASE4_IMPLEMENTATION_PLAN.md), [P4-06
- Use existing MUI/Emotion, semantic focus/color/status roles, PageHeader/PageSection and width/density aliases. No new theme, table framework, provider tree, persistent private store, generic save framework, or final brand/font/logo decision.
- Retain all 31 current routes and compatibility paths. Add `/analytics` only in P5-07 with meaningful existing content. P5-04b preserves `/kanban` as an alias only after parity; never remove it. Deep-link and dirty/account lifetimes are acceptance conditions, not cleanup.
- Every slice applies [visual acceptance](VISUAL_ACCEPTANCE.md), including light/dark × EN/NB, real populated/error data, desktop/phone and keyboard checks. All migrations are mobile-capable immediately; P5-14 is additional end-to-end review.
- After final code change run full inherited backend/frontend/browser/type/lint/build/security/config/secret/whitespace checks per [README](README.md#validation-baseline). Explain added/removed case counts, retain P2-D01 until separately proven fixed. Update a slice trace with actual commit/tests/evidence, not this plan's future tense.
- After final code change run full inherited backend/frontend/browser/type/lint/build/security/config/secret/whitespace checks per [README](README.md#validation-baseline). Explain added/removed case counts. **P2-D01 is an ordinary passing regression after P5-08b readiness**, not a current expected failure; retain the historical failing evidence and the passing native contract. Update a slice trace with actual commit/tests/evidence, not this plan's future tense.
- Roll back a slice's presentation and adapters together, retaining original data and URLs. No schema migration is included. Keep regression tests that describe still-required behavior; do not disable security gates to revert UI. A later compatibility URL already shared must continue resolving during rollback.
- Stop on unknown ownership/product semantics, newly required schema/provider/renderer replacement, unsafe query truncation or a failing preserved workflow. Document the affected scope; independent slices may proceed only by a subsequent instruction.
@@ -110,7 +112,9 @@ Sources: [Phase 3 sequencing](../phase-3/PHASE4_IMPLEMENTATION_PLAN.md), [P4-06
**Dependency/rollback:** P5-03 styling contract; independent of G-PACKAGE/CV. Revert board presentation while retaining its current API/path.
## P5-04b — Table/Board integration (blocked contract)
## P5-04b — Table/Board integration (read prerequisite satisfied)
Current status: [separate query readiness](p5-04b-readiness/README.md) and [integration](p5-04b/README.md) supply the accepted scoped implementation. The original dependency below remains the requirement; it is no longer an unexecuted blocker. Full-result scaling and physical-touch acceptance remain explicit gaps.
**Objective/scope:** once G-JOBS read parity is separately accepted, introduce one presentation `view=table|board` choice and compatible `/kanban` alias. Shared committed filter/query state, explicit selection lifetime, refresh and return context; reuse both renderers and the accepted read contract.