UI v2 Rewire Multi Sprint Plan (Draft 2 - Pack 22)

Status: SUPERSEDED (2026-07-13); do not author current work from this historical plan Date: 2026-02-20 Source set: source-of-truth.md, authority-matrix.md, sprint-planning-guide.md, S00_endpoint_contract_ledger_v2_pack22.md

Current source and the active documentation program are linked from the directory currency notice.

Scope and intent

This plan decomposes the Pack 22 advisory into execution sprints with explicit backend dependency ordering.

Precedence rule: higher pack number wins for overlap.

Mandatory contract workflow (all sprints)

For each screen in sprint scope, classify backend readiness:

Each sprint must produce or update a contract ledger with:

Wave map

WaveSprintsGoal
Wave 0S22-00Freeze Pack 22 canonical doc set and contract baseline
Wave 1S22-01, S22-02, S22-03Backend dependencies and DB migrations
Wave 2S22-04, S22-05FE nav shell and Releases consolidation
Wave 3S22-06, S22-07, S22-08Topology/Operations, Security/Evidence, Integrations/Admin alignment
Wave 4S22-09, S22-10Redirect cutover, Playwright conformity, release readiness

Sprint catalog

S22-00 - Spec freeze for Pack 22

S22-01 - Backend context and releases read models (dependency sprint)

S22-02 - Backend topology inventory contracts (dependency sprint)

S22-03 - Backend security disposition contracts (dependency sprint)

S22-04 - FE nav shell migration

S22-05 - FE Releases module consolidation

S22-06 - FE Topology and Operations boundary alignment

S22-07 - FE Security consolidation

S22-08 - FE Evidence/Integrations/Admin alignment

S22-09 - Route deprecation and redirect cutover

S22-10 - E2E conformity and release readiness

Cross-module backend ownership map (planning)

These modules are expected to receive backend contract work during Pack 22 migration:

Each sprint that touches these must include explicit cross-module allowance in its sprint file.

Initial sequencing recommendation

  1. Complete S22-00 documentation freeze.
  2. Execute S22-01, S22-02, S22-03 as backend dependency lane.
  3. Start FE with S22-04 and S22-05 after S22-01 API availability.
  4. Run S22-06, S22-07, S22-08 with dependency gating.
  5. Finish with S22-09 migration cutover and S22-10 QA signoff.

Proposed sprint filename seeds (for docs/implplan authoring)