Stabilize release confidence approval decision journey

docs/implplan/SPRINT_20260315_002_Platform_release_confidence_operator_journey_audit.md

@@ -0,0 +1,76 @@
+# Sprint 20260315_002 - Platform Release Confidence Operator Journey Audit
+
+## Topic & Scope
+- Use Stella Ops as a release operator trying to gain confidence in a production promotion decision.
+- Drive the release-control journey end to end: mission control to approvals, promotions, deployments, release health, hotfixes, release evidence, and the adjacent security/evidence pivots a release operator actually uses while deciding.
+- Treat Playwright as retained evidence only after manual discovery. Every newly discovered release-confidence step or defect becomes retained coverage before the sprint closes.
+- Group fixes by root cause so the iteration closes whole release-confidence behavior slices, not isolated page patches.
+- Working directory: `.`.
+- Expected evidence: operator journey notes, retained Playwright additions, grouped defect analysis, focused regression tests where code changes land, rebuilt-stack retest results, and live journey evidence.
+
+## Dependencies & Concurrency
+- Depends on local commit `4a5185121` as the closed baseline from the setup/admin operator journey.
+- Safe parallelism: avoid environment resets while the live release-confidence journey is being exercised because releases, approvals, and evidence surfaces share the same stack state.
+
+## Documentation Prerequisites
+- `AGENTS.md`
+- `docs/INSTALL_GUIDE.md`
+- `docs/dev/DEV_ENVIRONMENT_SETUP.md`
+- `docs/qa/feature-checks/FLOW.md`
+- `docs/modules/platform/architecture-overview.md`
+
+## Delivery Tracker
+
+### PLATFORM-RELEASE-CONFIDENCE-001 - Define and execute the release-confidence operator journey
+Status: DONE
+Dependency: none
+Owners: QA, Product Manager
+Task description:
+- Act as a release operator preparing to promote or hotfix with confidence. Walk the visible release-control flow the way a user would: entry from mission control, release health, approvals, promotions, deployment detail, version detail, hotfix flow, and evidence hand-offs needed to justify a decision.
+
+Completion criteria:
+- [x] The release-confidence operator journey is explicitly listed before fixes begin.
+- [x] Playwright is used to execute the journey as an operator would, not only as a route sweep.
+- [x] Every broken route, page-load, data-load, hand-off, validation rule, or action encountered on the release path is recorded before any fix starts.
+
+### PLATFORM-RELEASE-CONFIDENCE-002 - Convert newly discovered release steps into retained coverage
+Status: DONE
+Dependency: PLATFORM-RELEASE-CONFIDENCE-001
+Owners: QA, Test Automation
+Task description:
+- Add or deepen retained Playwright coverage for every newly discovered release-confidence step so future iterations automatically recheck the same operator behavior.
+
+Completion criteria:
+- [x] Every newly discovered operator/release step is mapped to retained Playwright coverage or an explicit backlog gap.
+- [x] Retained coverage additions are organized by user journey, not only by route.
+- [x] The next aggregate run would exercise the newly discovered release-confidence path automatically.
+
+### PLATFORM-RELEASE-CONFIDENCE-003 - Repair grouped release-confidence defects and retest
+Status: DONE
+Dependency: PLATFORM-RELEASE-CONFIDENCE-002
+Owners: 3rd line support, Architect, Developer
+Task description:
+- Diagnose the grouped failures exposed by the release-confidence journey, choose the clean product/architecture-conformant fix, implement it, add retained Playwright coverage for the new behavior when needed, and rerun the affected journeys plus the aggregate audit before committing.
+
+Completion criteria:
+- [x] Root causes are recorded for the grouped failures.
+- [x] Fixes land with focused regression coverage and retained Playwright scenario updates where practical.
+- [x] The live stack is retested through the same release-confidence journeys before the iteration commit.
+
+## Execution Log
+| Date (UTC) | Update | Owner |
+| --- | --- | --- |
+| 2026-03-15 | Sprint created immediately after local commit `4a5185121` closed the setup/admin operator journey. | QA |
+| 2026-03-15 | Executed the release-confidence operator path from releases overview through deployments, approval detail, decision capsules, triage, advisories/VEX, reachability, security reports, promotions, and hotfix creation before fixing anything. | QA |
+| 2026-03-15 | Converted the approval-detail operator handoffs into retained Playwright coverage in `live-release-confidence-journey.mjs`, including the real decision cockpit route and scope-preservation assertions for Reachability, Ops/Data, and gate-fix pivots. | Test Automation |
+| 2026-03-15 | Root-caused the release-confidence defect set to the approval detail route loading a legacy placeholder component and the real cockpit dropping active operator scope on handoff links. Fixed the canonical route, centralized handoff query-param preservation in `approval-detail-page.component.ts`, added focused Angular regression coverage, rebuilt the web bundle, redeployed, and reran the live release-confidence journey clean with `failedStepCount=0` and `runtimeIssueCount=0`. | QA / 3rd line support / Architect / Developer |
+
+## Decisions & Risks
+- Decision: this iteration prioritizes release-confidence behavior over broad route counts.
+- Risk: several release-control surfaces already have route/action sweeps, but the full operator decision journey may still have hand-off gaps that only appear when used sequentially as a real user.
+- Decision: operator scope (`tenant`, `regions`, `environments`, `timeWindow`) must survive approval-detail pivots the same way it survives deployment-detail pivots; preserving that scope is part of the release-confidence contract, not optional UI state.
+- Root cause: `/releases/approvals/:id` still pointed at a legacy placeholder `approval-detail.component` while the actual decision cockpit lived in `approval-detail-page.component`; once the route was corrected, the retained journey exposed that cockpit handoffs generated canonical paths but discarded current operator scope because plain `routerLink` anchors and gate-fix links were not built from a shared scope-preserving query-param contract.
+
+## Next Checkpoints
+- Define the exact release-confidence path before fixing anything.
+- Run the journey manually with Playwright, then convert newly discovered steps into retained coverage.