Finalize topbar status chip ownership split

This commit is contained in:
master
2026-03-10 13:20:17 +02:00
parent 0e764da736
commit 1fe3f489f1
5 changed files with 269 additions and 191 deletions

View File

@@ -0,0 +1,44 @@
# Sprint 20260310-024 - FE Topbar Status Chip Ownership Split
## Topic & Scope
- Finish and verify the topbar/context-controls split so global scope selectors stay in `ContextChipsComponent` while status chips live in the authenticated topbar row.
- Capture the missed verification work for the already-implemented layout refactor and keep the commit scoped to the Web layout layer.
- Working directory: `src/Web/StellaOps.Web`.
- Allowed coordination edits: `docs/implplan/SPRINT_20260310_024_FE_topbar_status_chip_ownership_split.md`.
- Expected evidence: focused Angular layout specs and a live authenticated Playwright shell check.
## Dependencies & Concurrency
- Depends on the rebuilt local shell being reachable through `https://stella-ops.local`.
- Safe parallelism: avoid mixing unrelated Mission Control or search work into this layout cleanup iteration.
## Documentation Prerequisites
- `AGENTS.md`
- `docs/qa/feature-checks/FLOW.md`
## Delivery Tracker
### FE-TOPBAR-SPLIT-001 - Finalize topbar ownership for status chips
Status: DONE
Dependency: none
Owners: QA, Developer, Product Manager
Task description:
- Verify the refactor that moved system-status chips out of `ContextChipsComponent` and into the authenticated topbar row, then bring the stale unit tests and component comments in line with the new ownership split.
Completion criteria:
- [x] `ContextChipsComponent` describes and renders only shared scope controls.
- [x] `AppTopbarComponent` focused spec covers the authenticated status-chip row.
- [x] Live authenticated shell check confirms tenant, context controls, and status chips render together without console errors.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-03-10 | Sprint created while auditing forgotten uncommitted Web files; confirmed the live shell already renders tenant, context controls, and five status chips after authentication. | Developer |
| 2026-03-10 | Updated the stale topbar/context-chips specs to match the ownership split, aligned the `ContextChipsComponent` contract text/ARIA label, and reran the focused Angular layout tests with `7/7` passing. | QA |
## Decisions & Risks
- Decision: keep status chips in the topbar rather than `ContextChipsComponent` so layout can separate persistent shell health state from the interactive scope controls.
- Risk: unit tests can drift again when shell ownership changes without matching spec updates.
- Mitigation: keep focused topbar/context-chips specs near the components and validate the live authenticated shell with Playwright when ownership changes.
## Next Checkpoints
- Run the focused layout specs and commit the topbar/context-control split as its own FE iteration.