S02 UI Verification Plan - Sprint 040

Status: SUPERSEDED for current UI verification (2026-07-13); historical plan Date: 2026-02-20
Working directory: src/Web/StellaOps.Web/

Use the directory currency notice for current navigation, route inventory, and scope authorities.

Scope under verification

• Canonical root IA labels and route ownership (Mission Control + 5 domain roots)
• RBAC-gated visibility for root and major alias-window surfaces
• Global scope URL synchronization (regions, environments, timeWindow)
• Mobile/tablet scope control entry point
• Legacy route telemetry alignment with redirect templates
• Global search API wiring
• Release run-detail live refresh + degraded-state contract

Deterministic verification sequence

1. Unit and route tests:
   • src/tests/navigation/nav-model.spec.ts
   • src/tests/navigation/nav-route-integrity.spec.ts
   • src/tests/navigation/legacy-redirects.spec.ts
   • src/tests/navigation/legacy-route-telemetry.service.spec.ts
   • src/tests/context/platform-context-url-sync.service.spec.ts
   • src/tests/global_search/global-search.component.spec.ts
   • src/tests/releases/release-detail.live-refresh.spec.ts
2. Manual route checks:
   • /dashboard renders Mission Control label in sidebar and breadcrumb.
   • /security/posture, /security/disposition, /security/sbom/lake, /security/reachability resolve without alias errors.
   • /topology/promotion-graph is canonical; /topology/promotion-paths redirects.
3. Alias telemetry checks:
   • Navigate to /ops/health, /security-risk/sbom-lake, /release-control/setup.
   • Confirm a legacy_route_hit event is emitted with expected oldPath and resolved newPath.
4. Scope synchronization checks:
   • Open /security/posture?regions=us-east&environments=prod&timeWindow=7d; verify context hydrates.
   • Change scope selectors; verify URL query updates without losing unrelated query keys.
5. Run live-refresh checks:
   • Open active run detail (/releases/runs/:runId/timeline) and verify periodic refresh status transitions (LIVE -> SYNCING).
   • Simulate backend failure and verify degraded banner shows retry + correlation ID.
   • Verify terminal run status stops polling.

Evidence capture requirements

• Record test pass/fail and command outputs in sprint execution log.
• Include failing scenario notes for any non-deterministic behavior or flaky assertions.
• If a route alias is intentionally preserved, document the retention reason and next removal checkpoint.