Add live mission control action sweep

This commit is contained in:
master
2026-03-10 06:35:05 +02:00
parent ff4cd7e999
commit b9aa1dbe24
2 changed files with 435 additions and 0 deletions

View File

@@ -0,0 +1,64 @@
# Sprint 20260310-003 - FE Mission Control Live Action Sweep
## Topic & Scope
- Add a reusable authenticated Playwright sweep for the Mission Control board, alerts, and activity surfaces on the real `https://stella-ops.local` frontdoor.
- Verify the high-signal cross-product links from Mission Control resolve to the correct downstream page with the expected scoped state, instead of relying on broad route checks alone.
- Keep the work confined to live QA automation so the next scratch iterations can rerun Mission Control behavioral checks without manual clicking.
- Working directory: `src/Web/StellaOps.Web/scripts`.
- Allowed coordination edits: `docs/implplan/SPRINT_20260310_003_FE_mission_control_live_action_sweep.md`.
- Expected evidence: a runnable live Mission Control action sweep script plus JSON evidence under `src/Web/StellaOps.Web/output/playwright/`.
## Dependencies & Concurrency
- Depends on the rebuilt stack being authenticated and reachable through `https://stella-ops.local`.
- Safe parallelism: do not touch unrelated Mission Control feature code or router/search implementation streams during this QA-only iteration.
## Documentation Prerequisites
- `AGENTS.md`
- `docs/qa/feature-checks/FLOW.md`
- `docs/implplan/SPRINT_20260309_002_FE_live_frontdoor_canonical_route_sweep.md`
## Delivery Tracker
### FE-MISSION-LIVE-001 - Add Mission Control action sweep harness
Status: DONE
Dependency: none
Owners: QA, Developer (FE)
Task description:
- Create a focused live Playwright harness that authenticates through the real frontdoor and exercises the important Mission Control actions on the board, alerts, and activity pages.
- The harness must verify that the links resolve to the correct downstream paths and preserve the scoped stage/us-east context where applicable.
Completion criteria:
- [x] A script exists under `src/Web/StellaOps.Web/scripts/` for live Mission Control action sweeps.
- [x] The script writes structured JSON output to `src/Web/StellaOps.Web/output/playwright/`.
- [x] The script exits non-zero when any Mission Control action or runtime contract fails.
### FE-MISSION-LIVE-002 - Verify Mission Control board, alerts, and activity actions
Status: DONE
Dependency: FE-MISSION-LIVE-001
Owners: QA
Task description:
- Execute the Mission Control action sweep against the rebuilt stack and verify the primary board summary links, regional stage links, alert drilldowns, and activity drilldowns.
- Distinguish product defects from harness selection mistakes before escalating any result into implementation work.
Completion criteria:
- [x] The board links for releases, approvals, security, data integrity, topology, and scoped stage drilldowns are verified live.
- [x] The alerts and activity drilldowns are verified live.
- [x] The final live run completes with zero failed actions and zero runtime issues.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-03-10 | Sprint created for the next live behavioral pass after the canonical frontdoor sweep reached 111/111 passing routes and the policy/release/search slices were already rechecked. | Developer |
| 2026-03-10 | Added `scripts/live-mission-control-action-sweep.mjs` to exercise Mission Control board summary links, scoped stage environment links, alert drilldowns, and activity drilldowns through the authenticated frontdoor. | Developer |
| 2026-03-10 | Initial run surfaced a harness defect: the stage findings check selected the first `Findings` link (`dev`) rather than the intended `stage` row, and the auth helper emitted a harmless `about:blank` sessionStorage page error. Tightened the selector and filtered the known false-positive runtime noise. | Developer |
| 2026-03-10 | Reran the live Mission Control sweep successfully. Board, alerts, and activity actions now verify cleanly with `failedActionCount=0` and `runtimeIssueCount=0`. | Developer |
## Decisions & Risks
- Decision: treat Mission Control as a first-class action surface with its own live sweep, because it fans out into releases, security, evidence, topology, and trust workflows and can hide scoped-link regressions that route-level sweeps miss.
- Decision: filter the auth-helper `about:blank` sessionStorage page error in this harness because it is not a user-visible runtime failure and would otherwise pollute live action evidence.
- Risk: the Mission Control sweep still covers representative actions rather than every repeated row/link permutation on the board.
- Mitigation: keep the harness reusable and extend it in later iterations as additional board actions or state-specific flows are promoted into the live backlog.
## Next Checkpoints
- Commit the Mission Control live sweep as a standalone QA iteration.
- Continue expanding live action coverage into the next high-density page family on the rebuilt stack.