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

docs(ui): update task board and plan for orphan revival batch [SPRINT-013..023]

Browse Source 
Sync TASKS.md, implementation_plan.md, and orphan-revival-batch README
to reflect all 11 shipped orphan component adoption sprints.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
master
2026-03-08 19:25:48 +02:00
parent 2a25e7b2b0
commit d6b2e354f0
3 changed files with 94 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/modules/ui/TASKS.md
View File

@@ -2,6 +2,22 @@
## Active Sprint Links
- None currently. Completed UI delivery and verification sprints are archived under `docs-archived/implplan/`.
- [DONE] `docs/implplan/SPRINT_20260308_014_FE_orphan_copy_inline_truncate_adoption.md` - CopyToClipboard, InlineCode, TruncatePipe adoption on console-admin, offline-kit, and triage replay-command surfaces.
- [DONE] `docs/implplan/SPRINT_20260308_015_FE_orphan_filter_bar_unification.md` - FilterBarComponent adoption on 7 mounted list pages (audit-log-table, secret-findings-list, console-admin audit-log, release-list, evidence-pack-list, trust-audit-log, certificate-inventory).
## Queued Sprint Links
- `docs/modules/ui/orphan-revival-batch/README.md` - review index for the orphan shared-component and disconnected-route revival batch.
- `docs/implplan/SPRINT_20260308_013_FE_orphan_domain_signal_chips_adoption.md`
- `docs/implplan/SPRINT_20260308_014_FE_orphan_copy_inline_truncate_adoption.md`
- `docs/implplan/SPRINT_20260308_015_FE_orphan_filter_bar_unification.md`
- `docs/implplan/SPRINT_20260308_016_FE_orphan_persona_visibility_directives.md`
- `docs/implplan/SPRINT_20260308_017_FE_orphan_glossary_tooltips_adoption.md`
- `docs/implplan/SPRINT_20260308_018_FE_orphan_evidence_proof_component_adoption.md`
- `docs/implplan/SPRINT_20260308_019_FE_orphan_policy_component_adoption.md`
- `docs/implplan/SPRINT_20260308_020_FE_orphan_finding_list_consolidation.md`
- `docs/implplan/SPRINT_20260308_021_FE_unreachable_evidence_thread_and_persona_workspaces_routes.md`
- `docs/implplan/SPRINT_20260308_022_FE_unreachable_release_investigation_routes.md`
- `docs/implplan/SPRINT_20260308_023_FE_unreachable_registry_admin_route.md`
## Delivery Tasks
- [DONE] 041-T1 Root IA/nav rewrite (Mission Control + Ops + Setup)
@@ -144,3 +160,7 @@
- [DONE] FE-CA-004 Context header and return-to-context contract
- [DONE] FE-CA-005 Grouped overview-card and submenu patterns
- [DONE] FE-CA-006 Adoption map, QA, and docs sync for contextual action patterns
- [DONE] FE-OFB-001 Freeze adopted list-page set and shared filter-bar contract
- [DONE] FE-OFB-002 Migrate security and audit list pages to FilterBarComponent
- [DONE] FE-OFB-003 Migrate release, evidence, and trust list pages to FilterBarComponent
- [DONE] FE-OFB-004 Verify and document filter-bar revival

8
docs/modules/ui/implementation_plan.md
View File

@@ -8,7 +8,11 @@ Provide a living plan for UI deliverables, dependencies, and evidence.
- Update this file when new scoped work is approved.
## Near-term deliverables
- No active UI deliverables are currently staged in `docs/implplan`; refresh this section when the next approved sprint batch is opened.
- No active UI deliverables are currently staged in `docs/implplan`.
- The next queued batch is `docs/modules/ui/orphan-revival-batch/README.md`, which stages independent review-ready sprints for orphan shared-component adoption and disconnected-route integration.
- The queued orphan batch currently spans `SPRINT_20260308_013` through `SPRINT_20260308_023` and is intentionally not marked active until product review approves staffing.
- Sprint `014` (CopyToClipboard, InlineCode, TruncatePipe adoption) is DONE. See `docs/features/checked/web/orphan-copy-inline-truncate-adoption.md`.
- Sprint `015` (FilterBarComponent adoption on 7 mounted list pages) is DONE. See `docs/features/checked/web/filter-bar-unification.md`.
## Latest evidence
- `docs/modules/ui/component-preservation-map/README.md` - root index for the first-pass preservation map.
@@ -49,6 +53,8 @@ Provide a living plan for UI deliverables, dependencies, and evidence.
- `docs/modules/ui/workflow-visualization-replay/README.md` - detailed run-detail graph, timeline, replay, and evidence UX dossier.
- `docs/modules/ui/contextual-actions-patterns/README.md` - shared placement contract for stray actions, pages, drawers, and tabs.
- `docs/modules/ui/unified-audit-surfaces/README.md` - shipped canonical audit owner, alias contract, and secondary entry-point rules for cross-module audit browsing.
- `docs/modules/ui/orphan-revival-batch/README.md` - queued execution batch for reviving selected orphan shared components and reconnecting disconnected route families without reopening duplicate top-level products.
- `docs/features/checked/web/filter-bar-unification.md` - shipped verification note for the shared FilterBarComponent adoption on 7 mounted list pages (audit, security, release, evidence, trust families).
## Dependencies
- `docs/modules/ui/architecture.md`

67
docs/modules/ui/orphan-revival-batch/README.md Normal file
View File

@@ -0,0 +1,67 @@
# Orphan Revival Batch
## Purpose
- Convert the verified orphan and disconnected UI findings into execution-ready frontend sprints.
- Keep the batch parallel where possible so multiple agents can work without stepping on the same route parents or shared primitives.
- Make the merge direction explicit so later implementation does not accidentally reintroduce dead product brands, duplicate shells, or stale route aliases.
## Current Position
- The preservation-map and restoration-topic work already resolved the major product-shape questions for Policy Decisioning Studio, Reachability Witnessing, Workflow Visualization, Watchlist, Triage Explainability, and the consolidated Operations and Setup shells.
- This batch covers the remaining lower-level orphaned shared components and disconnected route files that still look worth reviving after those larger product merges landed.
- These sprints are intentionally queued for review. They are not started by default.
## Corrections To The External Scan
- `EvidenceDrawerComponent` is already mounted in `features/vulnerabilities/vulnerability-detail.component.html`; it is not a valid "finish the wiring" target in the current repo snapshot.
- `WitnessStatusChipComponent` is not truly isolated. It is used by `witness-comparison` and `unwitnessed-advisory`, which still sit inside a dormant witness chain and need separate product review.
- Route-file findings must be treated as candidate disconnected routes, not auto-approved reconnects. Every route reconnection sprint below requires a fresh parent-route verification pass before implementation begins.
- `timeline.routes.ts` cannot simply be mounted at `/releases/runs/:runId/timeline` because that path is already owned by the shipped run workspace. The relevant sprint must decide whether to absorb the old timeline surface into the current run detail experience or mount it as a secondary investigation route.
- Several "safe to remove" conclusions from the external scan should not be accepted without checking current consumers inside active shells first.
## Batch Design Rules
- No sprint in this batch may restore an abandoned product brand as a new top-level menu.
- Shared-component revival sprints must land on mounted UI paths, not only on QA fixtures or dead route trees.
- Route reconnection sprints each own a different parent route family so they can run in parallel.
- When a sprint touches a shared primitive and consumer pages, the consumer list is frozen inside that sprint to avoid cross-agent overlap.
- Each sprint below is independently staffable. If a sprint has external prerequisites, they are already satisfied by shipped work outside this batch.
## Queued Sprint Matrix
| Sprint | Theme | Primary owners | Hard dependency inside batch | Concurrency notes |
| --- | --- | --- | --- | --- |
| `SPRINT_20260308_013_FE_orphan_domain_signal_chips_adoption.md` | Revive `DigestChipComponent` and `ReachabilityStateChipComponent` | `shared/domain`, compare, change-trace, vulnerabilities, reachability | none | Parallel with every sprint below; do not touch finding-list consumers reserved for sprint `020` |
| `SPRINT_20260308_014_FE_orphan_copy_inline_truncate_adoption.md` | Revive `CopyToClipboardComponent`, `InlineCodeComponent`, and `TruncatePipe` | `shared/ui`, `shared/pipes`, mounted admin and operator consumers | none | Parallel with sprint `013` and route sprints; avoid proof and evidence consumers reserved for sprint `018` |
| `SPRINT_20260308_015_FE_orphan_filter_bar_unification.md` | Adopt `FilterBarComponent` on active list pages | `shared/ui/filter-bar` plus adopter pages | none | Independent, but no other sprint should edit `shared/ui/filter-bar` while it is staffed |
| `SPRINT_20260308_016_FE_orphan_persona_visibility_directives.md` | Adopt `stellaAuditorOnly` and `stellaOperatorOnly` | `shared/directives`, release, evidence, and promotion shells | none | Parallel with all route sprints and the other shared-component sprints because it excludes findings and policy adopters |
| `SPRINT_20260308_017_FE_orphan_glossary_tooltips_adoption.md` | Adopt glossary tooltips on jargon-heavy mounted shells | `shared/directives`, policy, findings, trust, and VEX | none | Parallel with all route sprints; avoid overlapping exact templates if the consumer set changes during staffing |
| `SPRINT_20260308_018_FE_orphan_evidence_proof_component_adoption.md` | Adopt proof and verification widgets | shared proof-verification components plus Evidence, Triage, and Releases consumers | none | Parallel with `013`, `014`, `015`, `021`, `022`, and `023`; reserve proof-chain and DSSE consumers for this sprint |
| `SPRINT_20260308_019_FE_orphan_policy_component_adoption.md` | Adopt policy evaluation and pack-editing widgets | shared policy components plus active policy and release-decisioning consumers | none | Parallel with all route sprints; uses the already shipped policy shell as its host |
| `SPRINT_20260308_020_FE_orphan_finding_list_consolidation.md` | Adopt `FindingListComponent` and `FindingRowComponent` | shared finding-list components plus findings, triage, and release-review consumers | none | Parallel with sprint `013` because it excludes vulnerability-explorer consumers |
| `SPRINT_20260308_021_FE_unreachable_evidence_thread_and_persona_workspaces_routes.md` | Reconnect evidence threads and persona workspaces | evidence route family | none | Parallel with `022` and `023` because parent route ownership does not overlap |
| `SPRINT_20260308_022_FE_unreachable_release_investigation_routes.md` | Integrate disconnected release-investigation routes | releases and deployment-investigation route family | none | Parallel with `021` and `023` because it owns the releases route tree |
| `SPRINT_20260308_023_FE_unreachable_registry_admin_route.md` | Reconnect registry-admin | integration-hub route family | none | Parallel with `021` and `022` because it owns a different route family |
## Dependency Summary
- Hard dependencies between queued sprints: none.
- External prerequisites that are already satisfied:
- Sprint `018` assumes the current Evidence and Releases shells remain canonical hosts.
- Sprint `019` assumes the current `/ops/policy` Decisioning Studio shell remains canonical.
- Sprint `021` assumes the current `/evidence` shell remains the canonical host for evidence-centric drill-ins.
- Sprint `022` assumes the current `/releases` run workspace and deployment history remain the canonical hosts for release investigation flows.
- Sprint `023` assumes the current integration hub remains the canonical host for registry management.
- Soft concurrency constraints:
- Sprint `015` should be the only sprint editing `shared/ui/filter-bar`.
- Sprint `018` should be the only sprint editing proof-chain and DSSE adoption targets.
- Sprint `016` and sprint `017` remain independent as planned, but staffing should keep their final template lists disjoint.
## Not Queued In This Batch
- `agents.routes.ts` is not queued because topology already owns agent-fleet surfacing.
- `issuer-trust.routes.ts` is not queued because trust administration already owns that capability.
- `policy.routes.ts` is not queued because the active Policy Decisioning shell supersedes it.
- `security.routes.ts` as a disconnected consolidation shell is not queued because the sub-capabilities already live under active security routes.
- `release-control` legacy shells are not queued because they should continue to be harvested into active products, not revived.
- `analytics.routes.ts`, `control-plane.routes.ts`, and `vex-timeline.routes.ts` are not queued because their best host shell is still ambiguous and they need a separate product-fit review before execution planning.
## Review Outcome Expected From User
- Confirm the queued sprint list is the right cut of the orphan backlog.
- Drop any sprint that feels too legacy or too duplicate-heavy before staffing.
- Mark which sprints can be staffed immediately and which should wait for later product review.