Align mission control with shared context scope

This commit is contained in:
master
2026-03-10 13:13:57 +02:00
parent fc7aaf4d37
commit 0e764da736
5 changed files with 172 additions and 135 deletions

View File

@@ -0,0 +1,59 @@
# Sprint 20260310-023 - FE Mission Control Shared Context Scope Alignment
## Topic & Scope
- Align Mission Control board and alert drilldowns with the shared Platform context so scoped sessions only surface matching environments and preserve tenant/region/environment state in downstream routes.
- Keep the work inside the Mission Control feature and its focused regression specs, with only sprint coordination outside the Web working directory.
- Working directory: `src/Web/StellaOps.Web`.
- Allowed coordination edits: `docs/implplan/SPRINT_20260310_023_FE_mission_control_shared_context_scope_alignment.md`.
- Expected evidence: focused Angular tests, a live authenticated Mission Control Playwright sweep, and rebuilt Web assets already synced into the running stack.
## Dependencies & Concurrency
- Depends on the authenticated local stack being reachable through `https://stella-ops.local`.
- Depends on the frontdoor evidence routing fix in `SPRINT_20260310_022_Router_platform_v2_evidence_frontdoor_mapping.md` so downstream posture pages do not emit false Mission Control runtime failures.
- Safe parallelism: do not mix unrelated layout/search cleanup into this commit.
## Documentation Prerequisites
- `AGENTS.md`
- `docs/qa/feature-checks/FLOW.md`
- `docs/implplan/SPRINT_20260310_003_FE_mission_control_live_action_sweep.md`
## Delivery Tracker
### FE-MISSION-SCOPE-001 - Align board environment selection with shared context
Status: DONE
Dependency: none
Owners: QA, Developer, Product Manager
Task description:
- Remove the Mission Control board's drift from the shared Platform context so scoped sessions only show the matching environment cards and downstream topology/findings links inherit the correct region and environment.
- Keep the implementation centered on the shared context store instead of duplicating local filter state inside the board component.
Completion criteria:
- [x] Mission Control board environment cards reflect the active `PlatformContextStore` region scope.
- [x] Scoped downstream links from the board preserve the expected region and environment query state.
- [x] Focused regression specs cover the shared-context behavior.
### FE-MISSION-SCOPE-002 - Preserve alert drilldown scope when leaving Mission Control
Status: DONE
Dependency: FE-MISSION-SCOPE-001
Owners: QA, Developer
Task description:
- Ensure Mission Control alert drilldowns merge the active query scope so Watchlist and adjacent surfaces do not drop the current tenant/region/environment window when the user pivots from alerts.
Completion criteria:
- [x] Mission Control alert links use merged query params where needed.
- [x] Live Mission Control action sweep completes with zero failed actions and zero runtime issues.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-03-10 | Sprint created after live Mission Control QA showed stage drilldowns resolving against the wrong region because the board was not honoring the active shared context scope. | Developer |
| 2026-03-10 | Updated the board and alert drilldowns to rely on shared query scope, refreshed the focused specs, rebuilt/synced the Web assets, and reran `scripts/live-mission-control-action-sweep.mjs` cleanly with `failedActionCount=0` and `runtimeIssueCount=0`. | QA |
## Decisions & Risks
- Decision: Mission Control should consume the global context store instead of keeping a separate board-local region/window state. That avoids dual sources of truth and keeps deep links aligned with the rest of the shell.
- Risk: other mission surfaces could still rely on stale local scope defaults.
- Mitigation: keep expanding the live action sweeps for Mission Control-adjacent pages and add focused spec coverage whenever a new scope regression is found.
## Next Checkpoints
- Commit the Mission Control scope repair as its own FE iteration.
- Continue into the next page-family action sweep on the rebuilt stack.