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

compoennts consolidation and avoid dropping of functionality work in progress

Browse Source
This commit is contained in:
master
2026-03-07 16:45:18 +02:00
parent 80aa16d5a1
commit 12d7eda923
403 changed files with 25343 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

100
docs/implplan/SPRINT_20260307_009_DOCS_ui_component_preservation_map.md Normal file
View File

@@ -0,0 +1,100 @@
# Sprint 20260307-009 - UI Component Preservation Map
## Topic & Scope
- Build a durable map of unused and weakly surfaced Angular components in the Stella Ops web console.
- Capture first-pass preservation guidance for each component: archive, merge, preserve, wire in, or investigate.
- Create a per-component dossier tree so later iterations can deepen the judgment without restarting discovery.
- Working directory: `docs/modules/ui/component-preservation-map`.
- Expected evidence: generated inventory, per-component markdown dossiers, summary tree, and task-board links.
## Dependencies & Concurrency
- Depends on:
- `docs/modules/ui/README.md`
- `docs/modules/ui/architecture.md`
- `docs/modules/ui/implementation_plan.md`
- `docs/modules/platform/architecture-overview.md`
- Safe parallelism:
- Static inventory generation can run in parallel with manual review of high-value clusters.
- Later dossier enrichment can be split by feature family once the index format is frozen.
## Documentation Prerequisites
- `docs/modules/ui/README.md`
- `docs/modules/ui/architecture.md`
- `docs/modules/ui/implementation_plan.md`
- `docs/modules/ui/v2-rewire/source-of-truth.md`
- `docs/modules/platform/architecture-overview.md`
## Delivery Tracker
### DOCS-UCM-001 - Preservation map scaffold and inventory
Status: DONE
Dependency: none
Owners: Documentation author, Project Manager
Task description:
- Create the preservation-map doc tree under `docs/modules/ui/` with a stable index, a machine-readable inventory, and one markdown dossier per candidate component.
- Inventory should distinguish high-confidence dead components from routed-but-weakly-surfaced components so later review does not conflate them.
Completion criteria:
- [x] Root index exists for the preservation map.
- [x] Inventory is deterministic and grouped by feature family.
- [x] Each candidate component has a dossier file named after the component.
### DOCS-UCM-002 - First-pass preservation judgments
Status: DONE
Dependency: DOCS-UCM-001
Owners: Documentation author, Product Manager
Task description:
- For every inventoried component, document what the component appears to do, why it likely fell out of the active product, and whether its ideas are worth preserving.
- Use a constrained recommendation set: `archive`, `merge`, `preserve`, `wire-in`, `investigate`.
Completion criteria:
- [x] Every dossier has a first-pass recommendation.
- [x] Recommendations identify likely successor surfaces or merge targets when they exist.
- [x] High-value clusters have explicit rationale for preservation vs retirement.
### DOCS-UCM-003 - Summary tree and iteration plan
Status: DONE
Dependency: DOCS-UCM-002
Owners: Documentation author, Project Manager
Task description:
- Produce a summary tree that shows the feature branches, what each branch is, and what appears worth keeping in the final product.
- Record the remaining gaps that require later iterations and deeper cross-doc validation.
Completion criteria:
- [x] Summary tree exists and is linked from the root index.
- [x] Branch-level keep/merge/archive guidance is captured.
- [x] Follow-up investigation areas are listed for the next pass.
### DOCS-UCM-004 - Deep enrichment against Stella Ops dossiers
Status: TODO
Dependency: DOCS-UCM-003
Owners: Documentation author, Product Manager
Task description:
- Enrich the first-pass dossiers with stronger linkage to product docs, runbooks, contracts, and route-migration decisions.
- Resolve ambiguous components whose current value cannot be judged from frontend code alone.
Completion criteria:
- [ ] High-value branches have corroborating doc links.
- [ ] Ambiguous components are reduced to a smaller explicit investigate set.
- [ ] Final keep/merge/wire recommendations can be defended against current product documentation.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-03-07 | Sprint created for a multi-iteration preservation map of unused and weakly surfaced UI components. | Project Manager |
| 2026-03-07 | Generated first-pass preservation map artifacts under `docs/modules/ui/component-preservation-map/`: root index, summary tree, deterministic inventory, 303 component dossiers, and 89 branch indexes. | Documentation author |
## Decisions & Risks
- Decision: first iteration will prioritize a complete map and first-pass judgment over exhaustive historical certainty.
- Decision: preservation guidance uses five stable labels only: `archive`, `merge`, `preserve`, `wire-in`, `investigate`.
- Decision: first-pass artifact set is now rooted at `docs/modules/ui/component-preservation-map/README.md`, with `SUMMARY_TREE.md` and `inventory.json` as the stable entry points.
- Risk: routed child pages can appear unreachable in static analysis when they are only exposed through relative tab navigation.
- Mitigation: record routed-but-weakly-surfaced components separately from high-confidence dead components.
- Risk: some components express product intent that lives mostly in docs rather than current route wiring.
- Mitigation: keep a follow-up enrichment task that cross-links module docs, contracts, and runbooks before final retirement decisions.
- Evidence snapshot: first pass produced 167 `dead` components and 136 `weak-route` components, each with a markdown dossier for later enrichment.
## Next Checkpoints
- 2026-03-08: Preservation-map scaffold and initial inventory complete.
- 2026-03-09: First-pass recommendations written for all inventoried components.
- 2026-03-10: Summary tree reviewed and next-pass deep-dive list cut.

82
docs/implplan/SPRINT_20260307_016_FE_mission_control_scope_preserving_actions.md Normal file
View File

@@ -0,0 +1,82 @@
# Sprint 20260307-016 - FE Mission Control Scope-Preserving Actions
## Topic & Scope
- Repair mission-control and mission-board summary/action links so they preserve the active tenant, region, environment, and time-window scope when routing into downstream surfaces.
- Eliminate reliance on target-route redirects accidentally keeping or dropping query parameters depending on the destination module.
- Add focused Angular coverage for the affected mission links, then replay the broken actions with live Playwright from `https://stella-ops.local`.
- Working directory: `src/Web/StellaOps.Web`.
- Expected evidence: focused Angular tests, live Playwright action checks on mission board/alerts/activity links, and sprint execution log updates.
## Dependencies & Concurrency
- Depends on the earlier mission-board route and environment-scope fixes (`SPRINT_20260307_012`, `SPRINT_20260307_013`, and `SPRINT_20260307_015`) because this iteration preserves the already-correct global scope instead of redefining it.
- Safe parallelism: stay inside `src/Web/StellaOps.Web` plus this sprint file; do not touch unrelated navigation/settings/sidebar/user-menu work that other agents are editing.
- Scope is limited to mission-control and mission-board action links, not downstream page data models.
## Documentation Prerequisites
- `src/Web/StellaOps.Web/AGENTS.md`
- `src/Web/StellaOps.Web/src/app/features/dashboard-v3/dashboard-v3.component.ts`
- `src/Web/StellaOps.Web/src/app/features/mission-control/mission-alerts-page.component.ts`
- `src/Web/StellaOps.Web/src/app/features/mission-control/mission-activity-page.component.ts`
## Delivery Tracker
### FE-MISSION-001 - Reproduce scope loss from mission action links
Status: DOING
Dependency: none
Owners: QA
Task description:
- Replay the live mission alerts/activity actions from the authenticated shell with Playwright.
- Capture which links drop `tenant`, `regions`, and `environments` when leaving mission-control surfaces.
Completion criteria:
- [ ] Live Playwright evidence shows the exact mission actions that lose active scope.
- [ ] The defect is reduced to a specific link-contract pattern instead of a generic downstream page issue.
### FE-MISSION-002 - Make mission action links explicitly preserve active scope
Status: TODO
Dependency: FE-MISSION-001
Owners: Developer
Task description:
- Update mission-board and mission-control action links so they use explicit query-param merge semantics.
- Keep the fix scoped to the action layer so downstream pages receive the already-selected global context without route-specific patches.
Completion criteria:
- [ ] Mission-board summary, alert, activity, and cross-domain action links preserve active scope during navigation.
- [ ] Mission-control alerts and activity action links preserve active scope during navigation.
### FE-MISSION-003 - Add focused Angular coverage for scope-preserving links
Status: TODO
Dependency: FE-MISSION-002
Owners: Test Automation
Task description:
- Add focused tests that assert the affected mission action links use the explicit query-param merge contract.
- Keep the coverage under `src/app/core/testing` so it remains in the focused Angular test include set.
Completion criteria:
- [ ] Focused Angular tests assert the relevant mission links use `queryParamsHandling="merge"`.
- [ ] The tests fail before the fix and pass after it.
### FE-MISSION-004 - Replay mission actions live after the patch
Status: TODO
Dependency: FE-MISSION-003
Owners: QA
Task description:
- Re-run the previously broken mission alerts/activity actions against the live authenticated shell.
- Confirm the downstream pages keep the original tenant/region/environment scope after navigation.
Completion criteria:
- [ ] Live Playwright confirms approvals, disposition, data-integrity, and release-runs actions retain the scoped query string.
- [ ] Live Playwright confirms the fixed links no longer depend on destination-route behavior to keep context.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-03-07 | Sprint created after live Playwright from `/mission-control/alerts` and `/mission-control/activity` showed several actions dropping `tenant=demo-prod&regions=us-east&environments=stage` on navigation, while others kept it only by route-specific accident. | QA |
## Decisions & Risks
- Decision: fix scope preservation at the mission-link layer with explicit query-param merge semantics rather than modifying every downstream route that currently receives an empty or partial query string.
- Risk: the main dashboard uses the same static mission links, so the fix must cover both the dedicated mission-control pages and the mission-board surface in the same iteration.
## Next Checkpoints
- 2026-03-07: land the scope-preserving mission action patch and focused Angular coverage.
- 2026-03-07: replay the affected mission actions with live Playwright and continue the authenticated page/action sweep.