stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

docs(web): archive mission control release health sprint

Browse Source
This commit is contained in:
master
2026-03-08 15:27:54 +02:00
parent ac14e8fb38
commit 42b761d471
1 changed files with 0 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

73
docs-archived/implplan/SPRINT_20260307_012_FE_mission_control_release_health_environment_resolution.md Normal file
View File

@@ -0,0 +1,73 @@
# Sprint 20260307-012 - FE Mission Control Release Health Environment Resolution
## Topic & Scope
- Repair `/mission-control/release-health` so it resolves and displays the active environment instead of rendering an empty environment header shell.
- Reuse the already-synced global query context (`environment`, `environments`, `env`) as a fallback when the route has no `:environmentId` segment.
- Add focused Web tests for query-driven environment resolution and the explicit no-environment empty state, then verify the live route with Playwright.
- Working directory: `src/Web/StellaOps.Web`.
- Expected evidence: focused Web unit tests, live Playwright verification on `https://stella-ops.local`, and sprint execution log updates.
## Dependencies & Concurrency
- Depends on the earlier Topology context persistence iterations (`SPRINT_20260307_010` and `SPRINT_20260307_011`) because `/mission-control/release-health` now receives stable synced query context from the global platform context store.
- Safe parallelism: stay inside `src/Web/StellaOps.Web` plus sprint updates; do not touch unrelated settings/sidebar/user-menu work already in progress from other agents.
- QA lead: route was previously listed as FALLBACK in `docs/qa/baseline-test-results-2026-02-26.md`, so this pass revalidates that route at current runtime behavior instead of treating the old baseline as the final truth.
## Documentation Prerequisites
- `src/Web/StellaOps.Web/AGENTS.md`
- `src/Web/StellaOps.Web/src/app/routes/mission-control.routes.ts`
- `src/Web/StellaOps.Web/src/app/features/topology/environment-posture-page.component.ts`
## Delivery Tracker
### FE-RH-001 - Reproduce the live release-health context resolution gap
Status: DONE
Dependency: none
Owners: QA
Task description:
- Replay `/mission-control/release-health` with live Playwright after the Topology context persistence fix landed.
- Confirm whether the page resolves an environment or still renders the generic header/empty summaries.
Completion criteria:
- [x] Live Playwright captures the current `release-health` page behavior.
- [x] The route defect is isolated to environment resolution rather than route existence.
### FE-RH-002 - Resolve environment context from route or synced query state
Status: DONE
Dependency: FE-RH-001
Owners: Developer
Task description:
- Update `EnvironmentPosturePageComponent` so it falls back to query-context environment identifiers when the route lacks `:environmentId`.
- Show an explicit guidance message when no environment can be resolved instead of rendering a misleading empty summary.
- Add focused unit tests for query fallback and the no-environment state.
Completion criteria:
- [x] `/mission-control/release-health` resolves `dev` from synced query context and loads posture data.
- [x] The component shows an explicit empty-state/error message when no environment is available.
- [x] Focused unit tests cover both the query fallback and missing-environment behavior.
### FE-RH-003 - Replay the live mission-control release-health route
Status: DONE
Dependency: FE-RH-002
Owners: QA
Task description:
- Replay the live route with Playwright after the Web patch is built into the running stack.
- Confirm the page shows a resolved environment label/region and that the quick links remain user-reachable.
Completion criteria:
- [x] Live Playwright shows the resolved environment label instead of the generic header shell.
- [x] Quick links from `release-health` remain reachable without degraded state.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-03-07 | Sprint created after live Playwright on `/mission-control/release-health` showed the route no longer fell back, but still rendered a generic environment header with empty summaries because the component expected a route param that the mission-control route never provided. | QA |
| 2026-03-07 | Added query-context environment fallback plus explicit no-environment guidance in `EnvironmentPosturePageComponent`; focused Angular specs for query fallback and missing-context behavior passed via `npx ng test --watch=false --include src/app/core/testing/environment-posture-page.component.spec.ts --include src/app/core/testing/global-context-http.interceptor.spec.ts`. | Developer |
| 2026-03-07 | Replayed `/mission-control/release-health` with live Playwright after rebuilding the Web bundle. The route resolved `Development · us-east`, Pack22 requests returned `200`, and the action links to Release Runs, Findings, and Decision Capsules stayed reachable without degraded state. | QA |
## Decisions & Risks
- Decision: fix the component at the environment-resolution layer rather than adding a route parameter to mission-control, because the route is already fed by the global query context sync and should honor that state.
- Decision: keep the shared multi-scope/evidence contract work in Sprint `20260307-013` because the component fix alone did not address narrowed region scope or the missing evidence adapter.
- Risk: other routes may still mount shared components with mismatched parameter expectations, so the broader mission-control sweep should continue after this fix.
## Next Checkpoints
- 2026-03-07: continue the mission-control/topology Playwright sweep for the next live defects outside this component-specific environment-resolution fix.