compoennts consolidation and avoid dropping of functionality work in progress
This commit is contained in:
master
@@ -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.
|
||||||
@@ -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®ions=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.
|
||||||
@@ -8,6 +8,11 @@
|
|||||||
|
|
||||||
The Console presents operator dashboards for scans, policies, VEX evidence, runtime posture, and admin workflows.
|
The Console presents operator dashboards for scans, policies, VEX evidence, runtime posture, and admin workflows.
|
||||||
|
|
||||||
|
## Latest updates (2026-03-07)
|
||||||
|
- Generated the first-pass UI component preservation map at `component-preservation-map/README.md`.
|
||||||
|
- The preservation map currently tracks 303 candidate components: 167 high-confidence dead surfaces and 136 routed-but-weakly-surfaced surfaces.
|
||||||
|
- Each candidate now has a stable markdown dossier so later iterations can deepen keep / merge / wire / archive decisions without rebuilding the inventory.
|
||||||
|
|
||||||
## Latest updates (2026-02-21)
|
## Latest updates (2026-02-21)
|
||||||
- Runtime mock cutover completed for policy simulation history/conflict/batch flows and graph explorer data loading in `src/Web/StellaOps.Web/src/app/**`.
|
- Runtime mock cutover completed for policy simulation history/conflict/batch flows and graph explorer data loading in `src/Web/StellaOps.Web/src/app/**`.
|
||||||
- Runtime bindings now resolve to backend APIs for:
|
- Runtime bindings now resolve to backend APIs for:
|
||||||
@@ -43,10 +48,11 @@ The Console presents operator dashboards for scans, policies, VEX evidence, runt
|
|||||||
- Console architecture doc for layout and SSE fan-out.
|
- Console architecture doc for layout and SSE fan-out.
|
||||||
- Operator guide: `../../UI_GUIDE.md`. Accessibility: `../../accessibility.md`. Security: `../../security/`.
|
- Operator guide: `../../UI_GUIDE.md`. Accessibility: `../../accessibility.md`. Security: `../../security/`.
|
||||||
|
|
||||||
## Related resources
|
## Related resources
|
||||||
- ./operations/auth-smoke.md
|
- ./operations/auth-smoke.md
|
||||||
- ./operations/observability.md
|
- ./operations/observability.md
|
||||||
- ./console-architecture.md
|
- ./console-architecture.md
|
||||||
|
- ./component-preservation-map/README.md
|
||||||
|
|
||||||
## Backlog references
|
## Backlog references
|
||||||
- DOCS-CONSOLE-23-001 … DOCS-CONSOLE-23-003 baseline (done).
|
- DOCS-CONSOLE-23-001 … DOCS-CONSOLE-23-003 baseline (done).
|
||||||
|
|||||||
@@ -6,6 +6,7 @@
|
|||||||
- `docs/implplan/SPRINT_20260306_002_FE_search_advisory_quality_ux.md`
|
- `docs/implplan/SPRINT_20260306_002_FE_search_advisory_quality_ux.md`
|
||||||
- `docs/implplan/SPRINT_20260307_004_FE_self_serve_search_answer_first.md`
|
- `docs/implplan/SPRINT_20260307_004_FE_self_serve_search_answer_first.md`
|
||||||
- `docs/implplan/SPRINT_20260307_006_FE_self_serve_rollout_and_gap_closure.md`
|
- `docs/implplan/SPRINT_20260307_006_FE_self_serve_rollout_and_gap_closure.md`
|
||||||
|
- `docs/implplan/SPRINT_20260307_009_DOCS_ui_component_preservation_map.md`
|
||||||
|
|
||||||
## Delivery Tasks
|
## Delivery Tasks
|
||||||
- [DONE] 041-T1 Root IA/nav rewrite (Mission Control + Ops + Setup)
|
- [DONE] 041-T1 Root IA/nav rewrite (Mission Control + Ops + Setup)
|
||||||
@@ -44,3 +45,7 @@
|
|||||||
- [DONE] FE-UX-E2E Playwright coverage for mode switching, rescue flows, and AdvisoryAI next-step cards
|
- [DONE] FE-UX-E2E Playwright coverage for mode switching, rescue flows, and AdvisoryAI next-step cards
|
||||||
- [DONE] WEB-CTX-NONOBVIOUS Strategic non-obvious suggestion recipes (cross-domain + action-aware)
|
- [DONE] WEB-CTX-NONOBVIOUS Strategic non-obvious suggestion recipes (cross-domain + action-aware)
|
||||||
- [DOING] FE-QA-LOOP-001 Web-only Playwright full-iteration loop at stella-ops.local (fresh route/action evidence, triage, fix, retest)
|
- [DOING] FE-QA-LOOP-001 Web-only Playwright full-iteration loop at stella-ops.local (fresh route/action evidence, triage, fix, retest)
|
||||||
|
- [DONE] DOCS-UCM-001 UI component preservation map scaffold and inventory
|
||||||
|
- [DONE] DOCS-UCM-002 First-pass preservation judgments for unused and weakly surfaced UI components
|
||||||
|
- [DONE] DOCS-UCM-003 Summary tree for keep / merge / wire / archive decisions
|
||||||
|
- [TODO] DOCS-UCM-004 Deep enrichment against Stella Ops product and module docs
|
||||||
|
|||||||
115
docs/modules/ui/component-preservation-map/README.md
Normal file
115
docs/modules/ui/component-preservation-map/README.md
Normal file
@@ -0,0 +1,115 @@
|
|||||||
|
# UI Component Preservation Map
|
||||||
|
|
||||||
|
Generated on 2026-03-07. This map captures Angular components that currently look either high-confidence dead or routed-but-weakly-surfaced in the Stella Ops web console.
|
||||||
|
|
||||||
|
## How To Read This Map
|
||||||
|
- `dead`: no active route target and no runtime references outside tests/stories.
|
||||||
|
- `weak-route`: still routed, but the current static scan found no menu entry and no obvious absolute page-action path to the route.
|
||||||
|
- Recommendation labels are intentionally constrained: `archive`, `merge`, `preserve`, `wire-in`, `investigate`.
|
||||||
|
|
||||||
|
## Counts
|
||||||
|
- Dead components: 167
|
||||||
|
- Weak-route components: 136
|
||||||
|
- Total candidates: 303
|
||||||
|
|
||||||
|
## Main Artifacts
|
||||||
|
- [Summary Tree](./SUMMARY_TREE.md)
|
||||||
|
- [Inventory JSON](./inventory.json)
|
||||||
|
|
||||||
|
## Branch Index
|
||||||
|
### Dead
|
||||||
|
- [Admin Notifications](./components/dead/admin-notifications/README.md) - 1 components, default `investigate`
|
||||||
|
- [Advisory Ai](./components/dead/advisory-ai/README.md) - 5 components, default `investigate`
|
||||||
|
- [Aoc](./components/dead/aoc/README.md) - 1 components, default `investigate`
|
||||||
|
- [Approvals](./components/dead/approvals/README.md) - 3 components, default `investigate`
|
||||||
|
- [Binary Index](./components/dead/binary-index/README.md) - 1 components, default `investigate`
|
||||||
|
- [Change Trace](./components/dead/change-trace/README.md) - 1 components, default `investigate`
|
||||||
|
- [Compare](./components/dead/compare/README.md) - 2 components, default `investigate`
|
||||||
|
- [Components](./components/dead/components/README.md) - 10 components, default `investigate`
|
||||||
|
- [Cvss](./components/dead/cvss/README.md) - 1 components, default `investigate`
|
||||||
|
- [Dashboard](./components/dead/dashboard/README.md) - 2 components, default `investigate`
|
||||||
|
- [Deployments](./components/dead/deployments/README.md) - 1 components, default `investigate`
|
||||||
|
- [Doctor](./components/dead/doctor/README.md) - 1 components, default `investigate`
|
||||||
|
- [Environments](./components/dead/environments/README.md) - 1 components, default `investigate`
|
||||||
|
- [Evidence](./components/dead/evidence/README.md) - 3 components, default `investigate`
|
||||||
|
- [Evidence Thread](./components/dead/evidence-thread/README.md) - 2 components, default `investigate`
|
||||||
|
- [Findings](./components/dead/findings/README.md) - 1 components, default `investigate`
|
||||||
|
- [Graph](./components/dead/graph/README.md) - 3 components, default `investigate`
|
||||||
|
- [Home](./components/dead/home/README.md) - 1 components, default `investigate`
|
||||||
|
- [Lineage](./components/dead/lineage/README.md) - 14 components, default `investigate`
|
||||||
|
- [Operations](./components/dead/operations/README.md) - 1 components, default `investigate`
|
||||||
|
- [Overlays](./components/dead/overlays/README.md) - 2 components, default `investigate`
|
||||||
|
- [Platform](./components/dead/platform/README.md) - 1 components, default `investigate`
|
||||||
|
- [Platform Ops Legacy](./components/dead/platform-ops/README.md) - 5 components, default `merge`
|
||||||
|
- [Policy](./components/dead/policy/README.md) - 3 components, default `investigate`
|
||||||
|
- [Policy Studio Legacy](./components/dead/policy-studio/README.md) - 11 components, default `merge`
|
||||||
|
- [Promotions](./components/dead/promotions/README.md) - 2 components, default `investigate`
|
||||||
|
- [Proof Chain](./components/dead/proof-chain/README.md) - 1 components, default `investigate`
|
||||||
|
- [Proof Studio](./components/dead/proof-studio/README.md) - 1 components, default `investigate`
|
||||||
|
- [Qa](./components/dead/qa/README.md) - 1 components, default `investigate`
|
||||||
|
- [Reachability Witnessing](./components/dead/reachability/README.md) - 2 components, default `merge`
|
||||||
|
- [Registry Admin](./components/dead/registry-admin/README.md) - 4 components, default `investigate`
|
||||||
|
- [Release Control Legacy](./components/dead/release-control/README.md) - 9 components, default `archive`
|
||||||
|
- [Release Orchestrator](./components/dead/release-orchestrator/README.md) - 12 components, default `investigate`
|
||||||
|
- [Releases](./components/dead/releases/README.md) - 2 components, default `investigate`
|
||||||
|
- [Scores](./components/dead/scores/README.md) - 1 components, default `investigate`
|
||||||
|
- [Security](./components/dead/security/README.md) - 13 components, default `investigate`
|
||||||
|
- [Security Risk](./components/dead/security-risk/README.md) - 1 components, default `investigate`
|
||||||
|
- [Settings](./components/dead/settings/README.md) - 2 components, default `investigate`
|
||||||
|
- [Slo Monitoring](./components/dead/slo-monitoring/README.md) - 4 components, default `investigate`
|
||||||
|
- [Snapshot](./components/dead/snapshot/README.md) - 1 components, default `investigate`
|
||||||
|
- [Timeline](./components/dead/timeline/README.md) - 1 components, default `investigate`
|
||||||
|
- [Triage Workbench](./components/dead/triage/README.md) - 8 components, default `merge`
|
||||||
|
- [Triage Inbox](./components/dead/triage-inbox/README.md) - 1 components, default `investigate`
|
||||||
|
- [Ui](./components/dead/ui/README.md) - 8 components, default `investigate`
|
||||||
|
- [Unknowns](./components/dead/unknowns/README.md) - 1 components, default `investigate`
|
||||||
|
- [VEX Studio](./components/dead/vex-studio/README.md) - 1 components, default `merge`
|
||||||
|
- [Vuln Explorer](./components/dead/vuln-explorer/README.md) - 7 components, default `investigate`
|
||||||
|
- [Vulnerabilities](./components/dead/vulnerabilities/README.md) - 2 components, default `investigate`
|
||||||
|
- [Watchlist](./components/dead/watchlist/README.md) - 1 components, default `wire-in`
|
||||||
|
- [Workflow Visualization Prototype](./components/dead/workflow-visualization/README.md) - 3 components, default `investigate`
|
||||||
|
- [Workspaces](./components/dead/workspaces/README.md) - 1 components, default `investigate`
|
||||||
|
|
||||||
|
### Weak Route
|
||||||
|
- [Ai Runs](./components/weak-route/ai-runs/README.md) - 2 components, default `preserve`
|
||||||
|
- [Aoc Compliance](./components/weak-route/aoc-compliance/README.md) - 5 components, default `preserve`
|
||||||
|
- [Audit Log](./components/weak-route/audit-log/README.md) - 10 components, default `preserve`
|
||||||
|
- [Bundles](./components/weak-route/bundles/README.md) - 2 components, default `preserve`
|
||||||
|
- [Console](./components/weak-route/console/README.md) - 1 components, default `preserve`
|
||||||
|
- [Console Admin](./components/weak-route/console-admin/README.md) - 6 components, default `preserve`
|
||||||
|
- [Deadletter](./components/weak-route/deadletter/README.md) - 3 components, default `preserve`
|
||||||
|
- [Evidence Export](./components/weak-route/evidence-export/README.md) - 2 components, default `preserve`
|
||||||
|
- [Evidence Pack](./components/weak-route/evidence-pack/README.md) - 1 components, default `preserve`
|
||||||
|
- [Exceptions](./components/weak-route/exceptions/README.md) - 1 components, default `preserve`
|
||||||
|
- [Graph](./components/weak-route/graph/README.md) - 1 components, default `preserve`
|
||||||
|
- [Integration Hub](./components/weak-route/integration-hub/README.md) - 1 components, default `preserve`
|
||||||
|
- [Issuer Trust](./components/weak-route/issuer-trust/README.md) - 3 components, default `preserve`
|
||||||
|
- [Jobengine](./components/weak-route/jobengine/README.md) - 4 components, default `preserve`
|
||||||
|
- [Mission Control](./components/weak-route/mission-control/README.md) - 2 components, default `preserve`
|
||||||
|
- [Notify](./components/weak-route/notify/README.md) - 1 components, default `preserve`
|
||||||
|
- [Offline Kit](./components/weak-route/offline-kit/README.md) - 4 components, default `preserve`
|
||||||
|
- [Pack Registry](./components/weak-route/pack-registry/README.md) - 1 components, default `preserve`
|
||||||
|
- [Platform](./components/weak-route/platform/README.md) - 7 components, default `preserve`
|
||||||
|
- [Platform Health](./components/weak-route/platform-health/README.md) - 3 components, default `preserve`
|
||||||
|
- [Platform Ops Legacy](./components/weak-route/platform-ops/README.md) - 8 components, default `merge`
|
||||||
|
- [Policy Governance](./components/weak-route/policy-governance/README.md) - 14 components, default `preserve`
|
||||||
|
- [Policy Studio Legacy](./components/weak-route/policy-studio/README.md) - 1 components, default `merge`
|
||||||
|
- [Quota Dashboard](./components/weak-route/quota-dashboard/README.md) - 6 components, default `preserve`
|
||||||
|
- [Release Orchestrator](./components/weak-route/release-orchestrator/README.md) - 1 components, default `preserve`
|
||||||
|
- [Releases](./components/weak-route/releases/README.md) - 2 components, default `preserve`
|
||||||
|
- [Sbom Sources](./components/weak-route/sbom-sources/README.md) - 1 components, default `preserve`
|
||||||
|
- [Scanner Ops](./components/weak-route/scanner-ops/README.md) - 6 components, default `preserve`
|
||||||
|
- [Scheduler Ops](./components/weak-route/scheduler-ops/README.md) - 2 components, default `preserve`
|
||||||
|
- [Security](./components/weak-route/security/README.md) - 1 components, default `preserve`
|
||||||
|
- [Security Risk](./components/weak-route/security-risk/README.md) - 5 components, default `preserve`
|
||||||
|
- [Settings](./components/weak-route/settings/README.md) - 8 components, default `preserve`
|
||||||
|
- [Signals](./components/weak-route/signals/README.md) - 1 components, default `preserve`
|
||||||
|
- [Topology](./components/weak-route/topology/README.md) - 8 components, default `preserve`
|
||||||
|
- [Triage Workbench](./components/weak-route/triage/README.md) - 1 components, default `merge`
|
||||||
|
- [Trivy Db Settings](./components/weak-route/trivy-db-settings/README.md) - 1 components, default `preserve`
|
||||||
|
- [Trust Admin](./components/weak-route/trust-admin/README.md) - 6 components, default `preserve`
|
||||||
|
- [Unknowns Tracking](./components/weak-route/unknowns-tracking/README.md) - 4 components, default `preserve`
|
||||||
|
|
||||||
|
## Notes
|
||||||
|
- This is a first-pass map. The weak-route bucket especially needs follow-up review against relative tab navigation and Stella Ops product docs.
|
||||||
|
- Per-component dossiers are intentionally stable so later iterations can deepen the judgment rather than recreate the inventory.
|
||||||
544
docs/modules/ui/component-preservation-map/SUMMARY_TREE.md
Normal file
544
docs/modules/ui/component-preservation-map/SUMMARY_TREE.md
Normal file
@@ -0,0 +1,544 @@
|
|||||||
|
# Summary Tree
|
||||||
|
|
||||||
|
Generated on 2026-03-07. This is the branch-level view of candidate unused or weakly surfaced UI families.
|
||||||
|
|
||||||
|
## Dead
|
||||||
|
|
||||||
|
- Admin Notifications
|
||||||
|
what: Admin Notifications components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Advisory Ai
|
||||||
|
what: Advisory Ai components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 5 components
|
||||||
|
- Aoc
|
||||||
|
what: Aoc components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Approvals
|
||||||
|
what: Approvals components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 3 components
|
||||||
|
- Binary Index
|
||||||
|
what: Binary Index components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Change Trace
|
||||||
|
what: Change Trace components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Compare
|
||||||
|
what: Compare components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 2 components
|
||||||
|
- Components
|
||||||
|
what: Components components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 10 components
|
||||||
|
- Cvss
|
||||||
|
what: Cvss components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Dashboard
|
||||||
|
what: Dashboard components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 2 components
|
||||||
|
- Deployments
|
||||||
|
what: Deployments components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Doctor
|
||||||
|
what: Doctor components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Environments
|
||||||
|
what: Environments components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Evidence
|
||||||
|
what: Evidence components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 3 components
|
||||||
|
- Evidence Thread
|
||||||
|
what: Evidence Thread components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 2 components
|
||||||
|
- Findings
|
||||||
|
what: Findings components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Graph
|
||||||
|
what: Graph components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 3 components
|
||||||
|
- Home
|
||||||
|
what: Home components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Lineage
|
||||||
|
what: Lineage components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 14 components
|
||||||
|
- Operations
|
||||||
|
what: Operations components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Overlays
|
||||||
|
what: Overlays components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 2 components
|
||||||
|
- Platform
|
||||||
|
what: Platform components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Platform Ops Legacy
|
||||||
|
what: Older operations console pages from before the current `/ops` shell consolidation.
|
||||||
|
keep: Keep distinctive observability widgets, platform state views, and telemetry interactions that are still missing from the current ops pages.
|
||||||
|
action: `merge`
|
||||||
|
why: Ops views were consolidated under the newer platform and operations route families, leaving the older platform-ops pages behind.
|
||||||
|
count: 5 components
|
||||||
|
- Policy
|
||||||
|
what: Policy components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 3 components
|
||||||
|
- Policy Studio Legacy
|
||||||
|
what: Legacy all-in-one policy authoring, approvals, dashboard, and simulation surfaces from the older IA.
|
||||||
|
keep: Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces.
|
||||||
|
action: `merge`
|
||||||
|
why: The current route tree moved policy work into newer governance and simulation surfaces, leaving the old `/policy-studio` family unmounted.
|
||||||
|
count: 11 components
|
||||||
|
- Promotions
|
||||||
|
what: Promotions components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 2 components
|
||||||
|
- Proof Chain
|
||||||
|
what: Proof Chain components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Proof Studio
|
||||||
|
what: Proof Studio components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Qa
|
||||||
|
what: Qa components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Reachability Witnessing
|
||||||
|
what: Reachability proof, witness, and proof-of-exploit supporting surfaces.
|
||||||
|
keep: Keep witness capture, proof overlays, and explainability flows that can reinforce policy and evidence decisions.
|
||||||
|
action: `merge`
|
||||||
|
why: The supporting pages and drawers are not mounted even though reachability remains a core Stella Ops differentiator.
|
||||||
|
count: 2 components
|
||||||
|
- Registry Admin
|
||||||
|
what: Registry Admin components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 4 components
|
||||||
|
- Release Control Legacy
|
||||||
|
what: Pre-rewire release-control setup, governance, and landing pages retained after the route migration.
|
||||||
|
keep: Preserve only reusable copy, sequencing, or setup checklists that still improve the newer release and topology flows.
|
||||||
|
action: `archive`
|
||||||
|
why: The canonical IA now redirects old `release-control/*` concepts into `/releases`, `/ops`, and `/setup`, so the original surfaces no longer anchor the product.
|
||||||
|
count: 9 components
|
||||||
|
- Release Orchestrator
|
||||||
|
what: Release Orchestrator components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 12 components
|
||||||
|
- Releases
|
||||||
|
what: Releases components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 2 components
|
||||||
|
- Scores
|
||||||
|
what: Scores components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Security
|
||||||
|
what: Security components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 13 components
|
||||||
|
- Security Risk
|
||||||
|
what: Security Risk components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Settings
|
||||||
|
what: Settings components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 2 components
|
||||||
|
- Slo Monitoring
|
||||||
|
what: Slo Monitoring components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 4 components
|
||||||
|
- Snapshot
|
||||||
|
what: Snapshot components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Timeline
|
||||||
|
what: Timeline components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Triage Workbench
|
||||||
|
what: Triage experiments, workbenches, and audit-bundle side surfaces around artifact analysis.
|
||||||
|
keep: Keep any explainability, quiet-lane, or audit-bundle interactions that meaningfully shorten operator triage loops.
|
||||||
|
action: `merge`
|
||||||
|
why: Several triage surfaces read as design experiments that were never folded cleanly into the main artifact workspace.
|
||||||
|
count: 8 components
|
||||||
|
- Triage Inbox
|
||||||
|
what: Triage Inbox components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- Ui
|
||||||
|
what: Ui components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 8 components
|
||||||
|
- Unknowns
|
||||||
|
what: Unknowns components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
- VEX Studio
|
||||||
|
what: Conflict-resolution and authoring surfaces around VEX decisions.
|
||||||
|
keep: Keep conflict resolution workflows, rationale capture, and consensus tooling that could strengthen VEX Hub.
|
||||||
|
action: `merge`
|
||||||
|
why: The standalone studio is not mounted, but related VEX concepts and data structures still appear to matter elsewhere.
|
||||||
|
count: 1 components
|
||||||
|
- Vuln Explorer
|
||||||
|
what: Vuln Explorer components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 7 components
|
||||||
|
- Vulnerabilities
|
||||||
|
what: Vulnerabilities components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 2 components
|
||||||
|
- Watchlist
|
||||||
|
what: Operator watchlist and monitoring surfaces backed by a real client/provider but not wired into navigation.
|
||||||
|
keep: Keep the operational watchlist concept, status views, and monitoring workflows; this looks closer to productizable than many other dead branches.
|
||||||
|
action: `wire-in`
|
||||||
|
why: The feature appears partially implemented but never surfaced in the current route tree or menu.
|
||||||
|
count: 1 components
|
||||||
|
- Workflow Visualization Prototype
|
||||||
|
what: A prototype workflow explorer with time-travel and step drill-down concepts.
|
||||||
|
keep: Keep the timeline, step-diff, and replay ideas if they can strengthen evidence or release run introspection.
|
||||||
|
action: `investigate`
|
||||||
|
why: The route file exists, but nothing mounts the workflow visualization branch in the active shell.
|
||||||
|
count: 3 components
|
||||||
|
- Workspaces
|
||||||
|
what: Workspaces components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `investigate`
|
||||||
|
why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
count: 1 components
|
||||||
|
|
||||||
|
## Weak Route
|
||||||
|
|
||||||
|
- Ai Runs
|
||||||
|
what: Ai Runs components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 2 components
|
||||||
|
- Aoc Compliance
|
||||||
|
what: Aoc Compliance components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 5 components
|
||||||
|
- Audit Log
|
||||||
|
what: Audit Log components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 10 components
|
||||||
|
- Bundles
|
||||||
|
what: Bundles components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 2 components
|
||||||
|
- Console
|
||||||
|
what: Console components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 1 components
|
||||||
|
- Console Admin
|
||||||
|
what: Console Admin components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 6 components
|
||||||
|
- Deadletter
|
||||||
|
what: Deadletter components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 3 components
|
||||||
|
- Evidence Export
|
||||||
|
what: Evidence Export components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 2 components
|
||||||
|
- Evidence Pack
|
||||||
|
what: Evidence Pack components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 1 components
|
||||||
|
- Exceptions
|
||||||
|
what: Exceptions components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 1 components
|
||||||
|
- Graph
|
||||||
|
what: Graph components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 1 components
|
||||||
|
- Integration Hub
|
||||||
|
what: Integration Hub components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 1 components
|
||||||
|
- Issuer Trust
|
||||||
|
what: Issuer Trust components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 3 components
|
||||||
|
- Jobengine
|
||||||
|
what: Jobengine components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 4 components
|
||||||
|
- Mission Control
|
||||||
|
what: Mission Control components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 2 components
|
||||||
|
- Notify
|
||||||
|
what: Notify components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 1 components
|
||||||
|
- Offline Kit
|
||||||
|
what: Offline Kit components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 4 components
|
||||||
|
- Pack Registry
|
||||||
|
what: Pack Registry components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 1 components
|
||||||
|
- Platform
|
||||||
|
what: Platform components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 7 components
|
||||||
|
- Platform Health
|
||||||
|
what: Platform Health components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 3 components
|
||||||
|
- Platform Ops Legacy
|
||||||
|
what: Older operations console pages from before the current `/ops` shell consolidation.
|
||||||
|
keep: Keep distinctive observability widgets, platform state views, and telemetry interactions that are still missing from the current ops pages.
|
||||||
|
action: `merge`
|
||||||
|
why: Ops views were consolidated under the newer platform and operations route families, leaving the older platform-ops pages behind.
|
||||||
|
count: 8 components
|
||||||
|
- Policy Governance
|
||||||
|
what: Current policy governance admin subtree that looks real but still needs surface verification.
|
||||||
|
keep: Preserve the full governance branch; the main question is wiring quality, not product value.
|
||||||
|
action: `preserve`
|
||||||
|
why: These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
|
||||||
|
count: 14 components
|
||||||
|
- Policy Studio Legacy
|
||||||
|
what: Legacy all-in-one policy authoring, approvals, dashboard, and simulation surfaces from the older IA.
|
||||||
|
keep: Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces.
|
||||||
|
action: `merge`
|
||||||
|
why: The current route tree moved policy work into newer governance and simulation surfaces, leaving the old `/policy-studio` family unmounted.
|
||||||
|
count: 1 components
|
||||||
|
- Quota Dashboard
|
||||||
|
what: Quota Dashboard components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 6 components
|
||||||
|
- Release Orchestrator
|
||||||
|
what: Release Orchestrator components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 1 components
|
||||||
|
- Releases
|
||||||
|
what: Releases components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 2 components
|
||||||
|
- Sbom Sources
|
||||||
|
what: Sbom Sources components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 1 components
|
||||||
|
- Scanner Ops
|
||||||
|
what: Scanner Ops components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 6 components
|
||||||
|
- Scheduler Ops
|
||||||
|
what: Scheduler Ops components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 2 components
|
||||||
|
- Security
|
||||||
|
what: Security components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 1 components
|
||||||
|
- Security Risk
|
||||||
|
what: Security Risk components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 5 components
|
||||||
|
- Settings
|
||||||
|
what: Settings components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 8 components
|
||||||
|
- Signals
|
||||||
|
what: Signals components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 1 components
|
||||||
|
- Topology
|
||||||
|
what: Topology components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 8 components
|
||||||
|
- Triage Workbench
|
||||||
|
what: Triage experiments, workbenches, and audit-bundle side surfaces around artifact analysis.
|
||||||
|
keep: Keep any explainability, quiet-lane, or audit-bundle interactions that meaningfully shorten operator triage loops.
|
||||||
|
action: `merge`
|
||||||
|
why: Several triage surfaces read as design experiments that were never folded cleanly into the main artifact workspace.
|
||||||
|
count: 1 components
|
||||||
|
- Trivy Db Settings
|
||||||
|
what: Trivy Db Settings components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 1 components
|
||||||
|
- Trust Admin
|
||||||
|
what: Trust Admin components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 6 components
|
||||||
|
- Unknowns Tracking
|
||||||
|
what: Unknowns Tracking components grouped from the static unused-component scan.
|
||||||
|
keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
action: `preserve`
|
||||||
|
why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
|
||||||
|
count: 4 components
|
||||||
|
|
||||||
1038
docs/modules/ui/component-preservation-map/_tools/generate-map.cjs
Normal file
1038
docs/modules/ui/component-preservation-map/_tools/generate-map.cjs
Normal file
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,18 @@
|
|||||||
|
# Admin Notifications
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 1
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Admin Notifications components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [AdminNotificationsComponent](../features/admin-notifications/AdminNotificationsComponent.md) - `investigate`, features/admin-notifications/admin-notifications.component.ts
|
||||||
@@ -0,0 +1,22 @@
|
|||||||
|
# Advisory Ai
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 5
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Advisory Ai components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [AutofixWorkbenchComponent](../features/advisory-ai/AutofixWorkbenchComponent.md) - `investigate`, features/advisory-ai/autofix-workbench.component.ts
|
||||||
|
- [ChipShowcaseComponent](../features/advisory-ai/ChipShowcaseComponent.md) - `investigate`, features/advisory-ai/chip-showcase.component.ts
|
||||||
|
- [EvidenceDrilldownComponent](../features/advisory-ai/EvidenceDrilldownComponent.md) - `investigate`, features/advisory-ai/evidence-drilldown.component.ts
|
||||||
|
- [ExplainButtonComponent](../features/advisory-ai/ExplainButtonComponent.md) - `investigate`, features/advisory-ai/explain-button.component.ts
|
||||||
|
- [ExplanationPanelComponent](../features/advisory-ai/ExplanationPanelComponent.md) - `investigate`, features/advisory-ai/explanation-panel.component.ts
|
||||||
@@ -0,0 +1,18 @@
|
|||||||
|
# Aoc
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 1
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Aoc components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [AocVerificationWorkbenchComponent](../features/aoc/AocVerificationWorkbenchComponent.md) - `investigate`, features/aoc/aoc-verification-workbench.component.ts
|
||||||
@@ -0,0 +1,20 @@
|
|||||||
|
# Approvals
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 3
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Approvals components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [ApprovalDetailPageComponent](../features/approvals/ApprovalDetailPageComponent.md) - `investigate`, features/approvals/approval-detail-page.component.ts
|
||||||
|
- [ApprovalsInboxPageComponent](../features/approvals/ApprovalsInboxPageComponent.md) - `investigate`, features/approvals/approvals-inbox-page.component.ts
|
||||||
|
- [RequestExceptionModalComponent](../features/approvals/modals/RequestExceptionModalComponent.md) - `investigate`, features/approvals/modals/request-exception-modal.component.ts
|
||||||
@@ -0,0 +1,18 @@
|
|||||||
|
# Binary Index
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 1
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Binary Index components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [BinaryIndexOpsComponent](../features/binary-index/BinaryIndexOpsComponent.md) - `investigate`, features/binary-index/binary-index-ops.component.ts
|
||||||
@@ -0,0 +1,18 @@
|
|||||||
|
# Change Trace
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 1
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Change Trace components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [ChangeTraceViewerComponent](../features/change-trace/ChangeTraceViewerComponent.md) - `investigate`, features/change-trace/change-trace-viewer.component.ts
|
||||||
@@ -0,0 +1,19 @@
|
|||||||
|
# Compare
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 2
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Compare components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [DegradedModeBannerComponent](../features/compare/components/degraded-mode-banner/DegradedModeBannerComponent.md) - `investigate`, features/compare/components/degraded-mode-banner/degraded-mode-banner.component.ts
|
||||||
|
- [GraphMiniMapComponent](../features/compare/components/graph-mini-map/GraphMiniMapComponent.md) - `investigate`, features/compare/components/graph-mini-map/graph-mini-map.component.ts
|
||||||
@@ -0,0 +1,27 @@
|
|||||||
|
# Components
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 10
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Components components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [ActionWaterfallComponent](../shared/components/action-waterfall/ActionWaterfallComponent.md) - `investigate`, shared/components/action-waterfall/action-waterfall.component.ts
|
||||||
|
- [EvidenceChecklistComponent](../shared/components/evidence-checklist/EvidenceChecklistComponent.md) - `investigate`, shared/components/evidence-checklist/evidence-checklist.component.ts
|
||||||
|
- [FixVerdictBadgeComponent](../shared/components/FixVerdictBadgeComponent.md) - `investigate`, shared/components/fix-verdict-badge.component.ts
|
||||||
|
- [GraphSplitViewComponent](../shared/components/graph-diff/GraphSplitViewComponent.md) - `investigate`, shared/components/graph-diff/graph-split-view.component.ts
|
||||||
|
- [OfflineBannerComponent](../shared/components/OfflineBannerComponent.md) - `investigate`, shared/components/offline-banner.component.ts
|
||||||
|
- [PlaceholderPageComponent](../shared/components/placeholder-page/PlaceholderPageComponent.md) - `investigate`, shared/components/placeholder-page/placeholder-page.component.ts
|
||||||
|
- [SourceStatusBadgeComponent](../shared/components/SourceStatusBadgeComponent.md) - `investigate`, shared/components/source-status-badge.component.ts
|
||||||
|
- [SourceTypeIconComponent](../shared/components/SourceTypeIconComponent.md) - `investigate`, shared/components/source-type-icon.component.ts
|
||||||
|
- [ThemeToggleComponent](../shared/components/theme-toggle/ThemeToggleComponent.md) - `investigate`, shared/components/theme-toggle/theme-toggle.component.ts
|
||||||
|
- [ViewModeToggleComponent](../shared/components/view-mode-toggle/ViewModeToggleComponent.md) - `investigate`, shared/components/view-mode-toggle/view-mode-toggle.component.ts
|
||||||
@@ -0,0 +1,18 @@
|
|||||||
|
# Cvss
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 1
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Cvss components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [CvssReceiptComponent](../features/cvss/CvssReceiptComponent.md) - `investigate`, features/cvss/cvss-receipt.component.ts
|
||||||
@@ -0,0 +1,19 @@
|
|||||||
|
# Dashboard
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 2
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Dashboard components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [AiRiskDriversComponent](../features/dashboard/AiRiskDriversComponent.md) - `investigate`, features/dashboard/ai-risk-drivers.component.ts
|
||||||
|
- [SourcesDashboardComponent](../features/dashboard/SourcesDashboardComponent.md) - `investigate`, features/dashboard/sources-dashboard.component.ts
|
||||||
@@ -0,0 +1,18 @@
|
|||||||
|
# Deployments
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 1
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Deployments components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [DeploymentDetailPageComponent](../features/deployments/DeploymentDetailPageComponent.md) - `investigate`, features/deployments/deployment-detail-page.component.ts
|
||||||
@@ -0,0 +1,18 @@
|
|||||||
|
# Doctor
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 1
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Doctor components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [RegistryChecksPanelComponent](../features/doctor/components/registry/RegistryChecksPanelComponent.md) - `investigate`, features/doctor/components/registry/registry-checks-panel.component.ts
|
||||||
@@ -0,0 +1,18 @@
|
|||||||
|
# Environments
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 1
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Environments components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [EnvironmentsListPageComponent](../features/environments/EnvironmentsListPageComponent.md) - `investigate`, features/environments/environments-list-page.component.ts
|
||||||
@@ -0,0 +1,19 @@
|
|||||||
|
# Evidence Thread
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 2
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Evidence Thread components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [EvidenceThreadListComponent](../features/evidence-thread/components/evidence-thread-list/EvidenceThreadListComponent.md) - `investigate`, features/evidence-thread/components/evidence-thread-list/evidence-thread-list.component.ts
|
||||||
|
- [EvidenceThreadViewComponent](../features/evidence-thread/components/evidence-thread-view/EvidenceThreadViewComponent.md) - `investigate`, features/evidence-thread/components/evidence-thread-view/evidence-thread-view.component.ts
|
||||||
@@ -0,0 +1,20 @@
|
|||||||
|
# Evidence
|
||||||
|
|
||||||
|
## Branch Summary
|
||||||
|
- Classification bucket: `dead`
|
||||||
|
- Components in branch: 3
|
||||||
|
- Default recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
|
||||||
|
Evidence components grouped from the static unused-component scan.
|
||||||
|
|
||||||
|
## Why This Branch Matters
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Destination
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Components
|
||||||
|
- [EvidenceCenterPageComponent](../features/evidence/EvidenceCenterPageComponent.md) - `investigate`, features/evidence/evidence-center-page.component.ts
|
||||||
|
- [EvidencePacketPageComponent](../features/evidence/EvidencePacketPageComponent.md) - `investigate`, features/evidence/evidence-packet-page.component.ts
|
||||||
|
- [AuditBundleCreateModalComponent](../features/evidence/modals/AuditBundleCreateModalComponent.md) - `investigate`, features/evidence/modals/audit-bundle-create-modal.component.ts
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# AdminNotificationsComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Admin Notifications`
|
||||||
|
- Source: `features/admin-notifications/admin-notifications.component.ts`
|
||||||
|
- Selector: `app-admin-notifications`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Admin Notifications appears to be a dedicated feature surface in the Admin Notifications area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# AutofixWorkbenchComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Advisory Ai`
|
||||||
|
- Source: `features/advisory-ai/autofix-workbench.component.ts`
|
||||||
|
- Selector: `stellaops-autofix-workbench`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Autofix Workbench appears to be a dedicated feature surface in the Advisory Ai area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# ChipShowcaseComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Advisory Ai`
|
||||||
|
- Source: `features/advisory-ai/chip-showcase.component.ts`
|
||||||
|
- Selector: `stellaops-ai-chip-showcase`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Chip Showcase appears to be a dedicated feature surface in the Advisory Ai area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# EvidenceDrilldownComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Advisory Ai`
|
||||||
|
- Source: `features/advisory-ai/evidence-drilldown.component.ts`
|
||||||
|
- Selector: `stellaops-evidence-drilldown`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Evidence Drilldown appears to be a dedicated feature surface in the Advisory Ai area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# ExplainButtonComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Advisory Ai`
|
||||||
|
- Source: `features/advisory-ai/explain-button.component.ts`
|
||||||
|
- Selector: `stellaops-explain-button`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Explain Button appears to be a dedicated feature surface in the Advisory Ai area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# ExplanationPanelComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Advisory Ai`
|
||||||
|
- Source: `features/advisory-ai/explanation-panel.component.ts`
|
||||||
|
- Selector: `stellaops-explanation-panel`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Explanation Panel appears to be a detail panel or supporting drill-down surface in the Advisory Ai area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# AocVerificationWorkbenchComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Aoc`
|
||||||
|
- Source: `features/aoc/aoc-verification-workbench.component.ts`
|
||||||
|
- Selector: `stellaops-aoc-verification-workbench`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Aoc Verification Workbench appears to be a dedicated feature surface in the Aoc area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# ApprovalDetailPageComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Approvals`
|
||||||
|
- Source: `features/approvals/approval-detail-page.component.ts`
|
||||||
|
- Selector: `app-approval-detail-page`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Approval Detail Page appears to be a approval and review surface in the Approvals area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# ApprovalsInboxPageComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Approvals`
|
||||||
|
- Source: `features/approvals/approvals-inbox-page.component.ts`
|
||||||
|
- Selector: `app-approvals-inbox-page`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Approvals Inbox Page appears to be a approval and review surface in the Approvals area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# RequestExceptionModalComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Approvals`
|
||||||
|
- Source: `features/approvals/modals/request-exception-modal.component.ts`
|
||||||
|
- Selector: `app-request-exception-modal`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Request Exception Modal appears to be a dedicated feature surface in the Approvals / Modals area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# BinaryIndexOpsComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Binary Index`
|
||||||
|
- Source: `features/binary-index/binary-index-ops.component.ts`
|
||||||
|
- Selector: `app-binary-index-ops`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Binary Index Ops appears to be a dedicated feature surface in the Binary Index area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# ChangeTraceViewerComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Change Trace`
|
||||||
|
- Source: `features/change-trace/change-trace-viewer.component.ts`
|
||||||
|
- Selector: `stella-change-trace-viewer`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Change Trace Viewer appears to be a dedicated feature surface in the Change Trace area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# DegradedModeBannerComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Compare`
|
||||||
|
- Source: `features/compare/components/degraded-mode-banner/degraded-mode-banner.component.ts`
|
||||||
|
- Selector: `stella-degraded-mode-banner`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Degraded Mode Banner appears to be a dedicated feature surface in the Compare / Components / Degraded Mode Banner area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# GraphMiniMapComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Compare`
|
||||||
|
- Source: `features/compare/components/graph-mini-map/graph-mini-map.component.ts`
|
||||||
|
- Selector: `stella-graph-mini-map`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Graph Mini Map appears to be a visualization or exploration surface in the Compare / Components / Graph Mini Map area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# CvssReceiptComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Cvss`
|
||||||
|
- Source: `features/cvss/cvss-receipt.component.ts`
|
||||||
|
- Selector: `app-cvss-receipt`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Cvss Receipt appears to be a dedicated feature surface in the Cvss area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# AiRiskDriversComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Dashboard`
|
||||||
|
- Source: `features/dashboard/ai-risk-drivers.component.ts`
|
||||||
|
- Selector: `stella-ai-risk-drivers`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Ai Risk Drivers appears to be a dedicated feature surface in the Dashboard area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# SourcesDashboardComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Dashboard`
|
||||||
|
- Source: `features/dashboard/sources-dashboard.component.ts`
|
||||||
|
- Selector: `app-sources-dashboard`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Sources Dashboard appears to be a landing or overview surface in the Dashboard area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# DeploymentDetailPageComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Deployments`
|
||||||
|
- Source: `features/deployments/deployment-detail-page.component.ts`
|
||||||
|
- Selector: `app-deployment-detail-page`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Deployment Detail Page appears to be a detail panel or supporting drill-down surface in the Deployments area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# RegistryChecksPanelComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Doctor`
|
||||||
|
- Source: `features/doctor/components/registry/registry-checks-panel.component.ts`
|
||||||
|
- Selector: `st-registry-checks-panel`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Registry Checks Panel appears to be a detail panel or supporting drill-down surface in the Doctor / Components / Registry area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# EnvironmentsListPageComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Environments`
|
||||||
|
- Source: `features/environments/environments-list-page.component.ts`
|
||||||
|
- Selector: `app-environments-list-page`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Environments List Page appears to be a dedicated feature surface in the Environments area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# EvidenceThreadListComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Evidence Thread`
|
||||||
|
- Source: `features/evidence-thread/components/evidence-thread-list/evidence-thread-list.component.ts`
|
||||||
|
- Selector: `stella-evidence-thread-list`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Evidence Thread List appears to be a dedicated feature surface in the Evidence Thread / Components / Evidence Thread List area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# EvidenceThreadViewComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Evidence Thread`
|
||||||
|
- Source: `features/evidence-thread/components/evidence-thread-view/evidence-thread-view.component.ts`
|
||||||
|
- Selector: `stella-evidence-thread-view`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Evidence Thread View appears to be a dedicated feature surface in the Evidence Thread / Components / Evidence Thread View area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# EvidenceCenterPageComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Evidence`
|
||||||
|
- Source: `features/evidence/evidence-center-page.component.ts`
|
||||||
|
- Selector: `app-evidence-center-page`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Evidence Center Page appears to be a dedicated feature surface in the Evidence area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# EvidencePacketPageComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Evidence`
|
||||||
|
- Source: `features/evidence/evidence-packet-page.component.ts`
|
||||||
|
- Selector: `app-evidence-packet-page`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Evidence Packet Page appears to be a dedicated feature surface in the Evidence area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# AuditBundleCreateModalComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Evidence`
|
||||||
|
- Source: `features/evidence/modals/audit-bundle-create-modal.component.ts`
|
||||||
|
- Selector: `app-audit-bundle-create-modal`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Audit Bundle Create Modal appears to be a audit and evidence surface in the Evidence / Modals area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# FindingDetailLayoutComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Findings`
|
||||||
|
- Source: `features/findings/detail/finding-detail-layout.component.ts`
|
||||||
|
- Selector: `stella-finding-detail-layout`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Finding Detail Layout appears to be a detail panel or supporting drill-down surface in the Findings / Detail area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# GraphFiltersComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Graph`
|
||||||
|
- Source: `features/graph/graph-filters.component.ts`
|
||||||
|
- Selector: `app-graph-filters`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Graph Filters appears to be a visualization or exploration surface in the Graph area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# GraphHotkeyHelpComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Graph`
|
||||||
|
- Source: `features/graph/graph-hotkey-help.component.ts`
|
||||||
|
- Selector: `app-graph-hotkey-help`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Graph Hotkey Help appears to be a visualization or exploration surface in the Graph area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# GraphSidePanelsComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Graph`
|
||||||
|
- Source: `features/graph/graph-side-panels.component.ts`
|
||||||
|
- Selector: `app-graph-side-panels`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Graph Side Panels appears to be a detail panel or supporting drill-down surface in the Graph area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# HomeDashboardComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Home`
|
||||||
|
- Source: `features/home/home-dashboard.component.ts`
|
||||||
|
- Selector: `app-home-dashboard`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Home Dashboard appears to be a landing or overview surface in the Home area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# AuditPackExportComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/audit-pack-export/audit-pack-export.component.ts`
|
||||||
|
- Selector: `app-audit-pack-export`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Audit Pack Export appears to be a audit and evidence surface in the Lineage / Components / Audit Pack Export area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# ExplainerTimelineComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/explainer-timeline/explainer-timeline.component.ts`
|
||||||
|
- Selector: `app-explainer-timeline`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Explainer Timeline appears to be a visualization or exploration surface in the Lineage / Components / Explainer Timeline area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# LineageComparePanelComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/lineage-compare-panel/lineage-compare-panel.component.ts`
|
||||||
|
- Selector: `app-lineage-compare-panel`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Lineage Compare Panel appears to be a detail panel or supporting drill-down surface in the Lineage / Components / Lineage Compare Panel area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# LineageDetailPanelComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/lineage-detail-panel/lineage-detail-panel.component.ts`
|
||||||
|
- Selector: `app-lineage-detail-panel`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Lineage Detail Panel appears to be a detail panel or supporting drill-down surface in the Lineage / Components / Lineage Detail Panel area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# LineageEdgeComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/lineage-edge/lineage-edge.component.ts`
|
||||||
|
- Selector: `[app-lineage-edge]`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Lineage Edge appears to be a dedicated feature surface in the Lineage / Components / Lineage Edge area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# LineageExportButtonsComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/lineage-export-buttons/lineage-export-buttons.component.ts`
|
||||||
|
- Selector: `app-lineage-export-buttons`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Lineage Export Buttons appears to be a dedicated feature surface in the Lineage / Components / Lineage Export Buttons area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# LineageExportDialogComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/lineage-export-dialog/lineage-export-dialog.component.ts`
|
||||||
|
- Selector: `app-lineage-export-dialog`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Lineage Export Dialog appears to be a dedicated feature surface in the Lineage / Components / Lineage Export Dialog area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# LineageMobileCompareComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/lineage-mobile-compare/lineage-mobile-compare.component.ts`
|
||||||
|
- Selector: `app-lineage-mobile-compare`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Lineage Mobile Compare appears to be a dedicated feature surface in the Lineage / Components / Lineage Mobile Compare area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# LineageNodeComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/lineage-node/lineage-node.component.ts`
|
||||||
|
- Selector: `[app-lineage-node]`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Lineage Node appears to be a dedicated feature surface in the Lineage / Components / Lineage Node area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# LineageProvenanceCompareComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/lineage-provenance-compare/lineage-provenance-compare.component.ts`
|
||||||
|
- Selector: `app-lineage-provenance-compare`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Lineage Provenance Compare appears to be a dedicated feature surface in the Lineage / Components / Lineage Provenance Compare area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# LineageSbomDiffComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/lineage-sbom-diff/lineage-sbom-diff.component.ts`
|
||||||
|
- Selector: `app-lineage-sbom-diff`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Lineage Sbom Diff appears to be a dedicated feature surface in the Lineage / Components / Lineage Sbom Diff area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# LineageVexDiffComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/lineage-vex-diff/lineage-vex-diff.component.ts`
|
||||||
|
- Selector: `app-lineage-vex-diff`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Lineage Vex Diff appears to be a dedicated feature surface in the Lineage / Components / Lineage Vex Diff area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# NodeDiffTableComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/node-diff-table/diff-table.component.ts`
|
||||||
|
- Selector: `app-node-diff-table`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Node Diff Table appears to be a dedicated feature surface in the Lineage / Components / Node Diff Table area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PinnedPanelComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Lineage`
|
||||||
|
- Source: `features/lineage/components/pinned-explanation/pinned-panel/pinned-panel.component.ts`
|
||||||
|
- Selector: `app-pinned-panel`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Pinned Panel appears to be a detail panel or supporting drill-down surface in the Lineage / Components / Pinned Explanation / Pinned Panel area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# SearchQualityDashboardComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Operations`
|
||||||
|
- Source: `features/operations/search-quality/search-quality-dashboard.component.ts`
|
||||||
|
- Selector: `app-search-quality-dashboard`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Search Quality Dashboard appears to be a landing or overview surface in the Operations / Search Quality area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# BundleExplorerComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Platform Ops Legacy`
|
||||||
|
- Source: `features/platform-ops/federation-telemetry/bundle-explorer.component.ts`
|
||||||
|
- Selector: `app-bundle-explorer`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Bundle Explorer appears to be a dedicated feature surface in the Platform Ops / Federation Telemetry area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
Ops views were consolidated under the newer platform and operations route families, leaving the older platform-ops pages behind.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep distinctive observability widgets, platform state views, and telemetry interactions that are still missing from the current ops pages.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/ops and /ops/platform-setup
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/platform/architecture-overview.md](../../../../../../../platform/architecture-overview.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# ConsentManagementComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Platform Ops Legacy`
|
||||||
|
- Source: `features/platform-ops/federation-telemetry/consent-management.component.ts`
|
||||||
|
- Selector: `app-consent-management`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Consent Management appears to be a dedicated feature surface in the Platform Ops / Federation Telemetry area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
Ops views were consolidated under the newer platform and operations route families, leaving the older platform-ops pages behind.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep distinctive observability widgets, platform state views, and telemetry interactions that are still missing from the current ops pages.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/ops and /ops/platform-setup
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/platform/architecture-overview.md](../../../../../../../platform/architecture-overview.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# FederationOverviewComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Platform Ops Legacy`
|
||||||
|
- Source: `features/platform-ops/federation-telemetry/federation-overview.component.ts`
|
||||||
|
- Selector: `app-federation-overview`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Federation Overview appears to be a landing or overview surface in the Platform Ops / Federation Telemetry area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
Ops views were consolidated under the newer platform and operations route families, leaving the older platform-ops pages behind.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep distinctive observability widgets, platform state views, and telemetry interactions that are still missing from the current ops pages.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/ops and /ops/platform-setup
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/platform/architecture-overview.md](../../../../../../../platform/architecture-overview.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# IntelligenceViewerComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Platform Ops Legacy`
|
||||||
|
- Source: `features/platform-ops/federation-telemetry/intelligence-viewer.component.ts`
|
||||||
|
- Selector: `app-intelligence-viewer`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Intelligence Viewer appears to be a dedicated feature surface in the Platform Ops / Federation Telemetry area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
Ops views were consolidated under the newer platform and operations route families, leaving the older platform-ops pages behind.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep distinctive observability widgets, platform state views, and telemetry interactions that are still missing from the current ops pages.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/ops and /ops/platform-setup
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/platform/architecture-overview.md](../../../../../../../platform/architecture-overview.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PrivacyBudgetMonitorComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Platform Ops Legacy`
|
||||||
|
- Source: `features/platform-ops/federation-telemetry/privacy-budget-monitor.component.ts`
|
||||||
|
- Selector: `app-privacy-budget-monitor`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Privacy Budget Monitor appears to be a dedicated feature surface in the Platform Ops / Federation Telemetry area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
Ops views were consolidated under the newer platform and operations route families, leaving the older platform-ops pages behind.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep distinctive observability widgets, platform state views, and telemetry interactions that are still missing from the current ops pages.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/ops and /ops/platform-setup
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/platform/architecture-overview.md](../../../../../../../platform/architecture-overview.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PlatformHomePageComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Platform`
|
||||||
|
- Source: `features/platform/platform-home-page.component.ts`
|
||||||
|
- Selector: `app-platform-home-page`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Platform Home Page appears to be a landing or overview surface in the Platform area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# ConflictVisualizerComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `high`
|
||||||
|
- Feature branch: `Policy Studio Legacy`
|
||||||
|
- Source: `features/policy-studio/ai/conflict-visualizer.component.ts`
|
||||||
|
- Selector: `stellaops-conflict-visualizer`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Conflict Visualizer appears to be a visualization or exploration surface in the Policy Studio / Ai area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The current route tree moved policy work into newer governance and simulation surfaces, leaving the old `/policy-studio` family unmounted.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/admin/policy/governance and /admin/policy/simulation
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/contracts/policy-studio.md](../../../../../../../../contracts/policy-studio.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# LiveRulePreviewComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `high`
|
||||||
|
- Feature branch: `Policy Studio Legacy`
|
||||||
|
- Source: `features/policy-studio/ai/live-rule-preview.component.ts`
|
||||||
|
- Selector: `stellaops-live-rule-preview`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Live Rule Preview appears to be a approval and review surface in the Policy Studio / Ai area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The current route tree moved policy work into newer governance and simulation surfaces, leaving the old `/policy-studio` family unmounted.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/admin/policy/governance and /admin/policy/simulation
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/contracts/policy-studio.md](../../../../../../../../contracts/policy-studio.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# TestCasePanelComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `high`
|
||||||
|
- Feature branch: `Policy Studio Legacy`
|
||||||
|
- Source: `features/policy-studio/ai/test-case-panel.component.ts`
|
||||||
|
- Selector: `stellaops-test-case-panel`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Test Case Panel appears to be a detail panel or supporting drill-down surface in the Policy Studio / Ai area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The current route tree moved policy work into newer governance and simulation surfaces, leaving the old `/policy-studio` family unmounted.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/admin/policy/governance and /admin/policy/simulation
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/contracts/policy-studio.md](../../../../../../../../contracts/policy-studio.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# VersionHistoryComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `high`
|
||||||
|
- Feature branch: `Policy Studio Legacy`
|
||||||
|
- Source: `features/policy-studio/ai/version-history.component.ts`
|
||||||
|
- Selector: `stellaops-version-history`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Version History appears to be a dedicated feature surface in the Policy Studio / Ai area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The current route tree moved policy work into newer governance and simulation surfaces, leaving the old `/policy-studio` family unmounted.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/admin/policy/governance and /admin/policy/simulation
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/contracts/policy-studio.md](../../../../../../../../contracts/policy-studio.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PolicyApprovalsComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `high`
|
||||||
|
- Feature branch: `Policy Studio Legacy`
|
||||||
|
- Source: `features/policy-studio/approvals/policy-approvals.component.ts`
|
||||||
|
- Selector: `app-policy-approvals`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Policy Approvals appears to be a approval and review surface in the Policy Studio / Approvals area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The current route tree moved policy work into newer governance and simulation surfaces, leaving the old `/policy-studio` family unmounted.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/admin/policy/governance and /admin/policy/simulation
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/contracts/policy-studio.md](../../../../../../../../contracts/policy-studio.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PolicyDashboardComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `high`
|
||||||
|
- Feature branch: `Policy Studio Legacy`
|
||||||
|
- Source: `features/policy-studio/dashboard/policy-dashboard.component.ts`
|
||||||
|
- Selector: `app-policy-dashboard`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Policy Dashboard appears to be a landing or overview surface in the Policy Studio / Dashboard area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The current route tree moved policy work into newer governance and simulation surfaces, leaving the old `/policy-studio` family unmounted.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/admin/policy/governance and /admin/policy/simulation
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/contracts/policy-studio.md](../../../../../../../../contracts/policy-studio.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PolicyEditorComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `high`
|
||||||
|
- Feature branch: `Policy Studio Legacy`
|
||||||
|
- Source: `features/policy-studio/editor/policy-editor.component.ts`
|
||||||
|
- Selector: `app-policy-editor`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Policy Editor appears to be a authoring or editing surface in the Policy Studio / Editor area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The current route tree moved policy work into newer governance and simulation surfaces, leaving the old `/policy-studio` family unmounted.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/admin/policy/governance and /admin/policy/simulation
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/contracts/policy-studio.md](../../../../../../../../contracts/policy-studio.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PolicyExplainComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `high`
|
||||||
|
- Feature branch: `Policy Studio Legacy`
|
||||||
|
- Source: `features/policy-studio/explain/policy-explain.component.ts`
|
||||||
|
- Selector: `app-policy-explain`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Policy Explain appears to be a dedicated feature surface in the Policy Studio / Explain area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The current route tree moved policy work into newer governance and simulation surfaces, leaving the old `/policy-studio` family unmounted.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/admin/policy/governance and /admin/policy/simulation
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/contracts/policy-studio.md](../../../../../../../../contracts/policy-studio.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PolicyNlInputComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `high`
|
||||||
|
- Feature branch: `Policy Studio Legacy`
|
||||||
|
- Source: `features/policy-studio/nl-input/policy-nl-input.component.ts`
|
||||||
|
- Selector: `stellaops-policy-nl-input`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Policy Nl Input appears to be a dedicated feature surface in the Policy Studio / Nl Input area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The current route tree moved policy work into newer governance and simulation surfaces, leaving the old `/policy-studio` family unmounted.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/admin/policy/governance and /admin/policy/simulation
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/contracts/policy-studio.md](../../../../../../../../contracts/policy-studio.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PolicyRuleBuilderComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `high`
|
||||||
|
- Feature branch: `Policy Studio Legacy`
|
||||||
|
- Source: `features/policy-studio/rule-builder/policy-rule-builder.component.ts`
|
||||||
|
- Selector: `app-policy-rule-builder`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Policy Rule Builder appears to be a authoring or editing surface in the Policy Studio / Rule Builder area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The current route tree moved policy work into newer governance and simulation surfaces, leaving the old `/policy-studio` family unmounted.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/admin/policy/governance and /admin/policy/simulation
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/contracts/policy-studio.md](../../../../../../../../contracts/policy-studio.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PolicyYamlEditorComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `high`
|
||||||
|
- Feature branch: `Policy Studio Legacy`
|
||||||
|
- Source: `features/policy-studio/yaml/policy-yaml-editor.component.ts`
|
||||||
|
- Selector: `app-policy-yaml-editor`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Policy Yaml Editor appears to be a authoring or editing surface in the Policy Studio / Yaml area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The current route tree moved policy work into newer governance and simulation surfaces, leaving the old `/policy-studio` family unmounted.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/admin/policy/governance and /admin/policy/simulation
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/contracts/policy-studio.md](../../../../../../../../contracts/policy-studio.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# AttestationBadgeComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Policy`
|
||||||
|
- Source: `features/policy/components/attestation-badge/attestation-badge.component.ts`
|
||||||
|
- Selector: `app-attestation-badge`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Attestation Badge appears to be a dedicated feature surface in the Policy / Components / Attestation Badge area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# EvidenceChainViewerComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Policy`
|
||||||
|
- Source: `features/policy/components/evidence-chain-viewer/evidence-chain-viewer.component.ts`
|
||||||
|
- Selector: `app-evidence-chain-viewer`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Evidence Chain Viewer appears to be a dedicated feature surface in the Policy / Components / Evidence Chain Viewer area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# VerdictProofPanelComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Policy`
|
||||||
|
- Source: `features/policy/components/verdict-proof-panel/verdict-proof-panel.component.ts`
|
||||||
|
- Selector: `app-verdict-proof-panel`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Verdict Proof Panel appears to be a detail panel or supporting drill-down surface in the Policy / Components / Verdict Proof Panel area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# CreatePromotionComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Promotions`
|
||||||
|
- Source: `features/promotions/create-promotion.component.ts`
|
||||||
|
- Selector: `app-create-promotion`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Create Promotion appears to be a dedicated feature surface in the Promotions area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PromotionDetailComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Promotions`
|
||||||
|
- Source: `features/promotions/promotion-detail.component.ts`
|
||||||
|
- Selector: `app-promotion-detail`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Promotion Detail appears to be a detail panel or supporting drill-down surface in the Promotions area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# ProofDetailPanelComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Proof Chain`
|
||||||
|
- Source: `features/proof-chain/components/proof-detail-panel.component.ts`
|
||||||
|
- Selector: `stella-proof-detail-panel`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Proof Detail Panel appears to be a detail panel or supporting drill-down surface in the Proof Chain / Components area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# ProofStudioContainerComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Proof Studio`
|
||||||
|
- Source: `features/proof-studio/components/proof-studio-container/proof-studio-container.component.ts`
|
||||||
|
- Selector: `app-proof-studio-container`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Proof Studio Container appears to be a dedicated feature surface in the Proof Studio / Components / Proof Studio Container area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# WebFeatureRecheckWorkbenchComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Qa`
|
||||||
|
- Source: `features/qa/web-feature-recheck-workbench.component.ts`
|
||||||
|
- Selector: `app-web-feature-recheck-workbench`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Web Feature Recheck Workbench appears to be a dedicated feature surface in the Qa area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PoEDrawerComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `high`
|
||||||
|
- Feature branch: `Reachability Witnessing`
|
||||||
|
- Source: `features/reachability/poe-drawer.component.ts`
|
||||||
|
- Selector: `app-poe-drawer`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Po EDrawer appears to be a detail panel or supporting drill-down surface in the Reachability area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The supporting pages and drawers are not mounted even though reachability remains a core Stella Ops differentiator.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep witness capture, proof overlays, and explainability flows that can reinforce policy and evidence decisions.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/security/reachability or /evidence
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/platform/architecture-overview.md](../../../../../../platform/architecture-overview.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# WitnessPageComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `merge`
|
||||||
|
- Preservation value: `high`
|
||||||
|
- Feature branch: `Reachability Witnessing`
|
||||||
|
- Source: `features/reachability/witness-page.component.ts`
|
||||||
|
- Selector: `app-witness-page`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Witness Page appears to be a dedicated feature surface in the Reachability area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The supporting pages and drawers are not mounted even though reachability remains a core Stella Ops differentiator.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Keep witness capture, proof overlays, and explainability flows that can reinforce policy and evidence decisions.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/security/reachability or /evidence
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/platform/architecture-overview.md](../../../../../../platform/architecture-overview.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# RegistryAdminComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Registry Admin`
|
||||||
|
- Source: `features/registry-admin/registry-admin.component.ts`
|
||||||
|
- Selector: `app-registry-admin`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Registry Admin appears to be a dedicated feature surface in the Registry Admin area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PlanAuditComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Registry Admin`
|
||||||
|
- Source: `features/registry-admin/components/plan-audit.component.ts`
|
||||||
|
- Selector: `app-plan-audit`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Plan Audit appears to be a audit and evidence surface in the Registry Admin / Components area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PlanEditorComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Registry Admin`
|
||||||
|
- Source: `features/registry-admin/components/plan-editor.component.ts`
|
||||||
|
- Selector: `app-plan-editor`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Plan Editor appears to be a authoring or editing surface in the Registry Admin / Components area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# PlanListComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `investigate`
|
||||||
|
- Preservation value: `medium`
|
||||||
|
- Feature branch: `Registry Admin`
|
||||||
|
- Source: `features/registry-admin/components/plan-list.component.ts`
|
||||||
|
- Selector: `app-plan-list`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Plan List appears to be a dedicated feature surface in the Registry Admin / Components area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
Needs branch-level review against current IA
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/README.md](../../../../../../README.md)
|
||||||
|
- [docs/modules/ui/architecture.md](../../../../../../architecture.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# ReleaseControlGovernanceHubComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `archive`
|
||||||
|
- Preservation value: `low`
|
||||||
|
- Feature branch: `Release Control Legacy`
|
||||||
|
- Source: `features/release-control/governance/release-control-governance-hub.component.ts`
|
||||||
|
- Selector: `app-release-control-governance-hub`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Release Control Governance Hub appears to be a dedicated feature surface in the Release Control / Governance area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The canonical IA now redirects old `release-control/*` concepts into `/releases`, `/ops`, and `/setup`, so the original surfaces no longer anchor the product.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve only reusable copy, sequencing, or setup checklists that still improve the newer release and topology flows.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/releases, /ops/platform-setup, and /setup/topology
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/v2-rewire/S00_route_deprecation_map.md](../../../../../../v2-rewire/S00_route_deprecation_map.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
@@ -0,0 +1,47 @@
|
|||||||
|
# ReleaseControlGovernanceSectionComponent
|
||||||
|
|
||||||
|
## Status Snapshot
|
||||||
|
- Classification: `dead`
|
||||||
|
- Confidence: `high`
|
||||||
|
- Recommendation: `archive`
|
||||||
|
- Preservation value: `low`
|
||||||
|
- Feature branch: `Release Control Legacy`
|
||||||
|
- Source: `features/release-control/governance/release-control-governance-section.component.ts`
|
||||||
|
- Selector: `app-release-control-governance-section`
|
||||||
|
|
||||||
|
## What Is It?
|
||||||
|
Release Control Governance Section appears to be a dedicated feature surface in the Release Control / Governance area.
|
||||||
|
|
||||||
|
## Why It Likely Fell Out Of The Product
|
||||||
|
The canonical IA now redirects old `release-control/*` concepts into `/releases`, `/ops`, and `/setup`, so the original surfaces no longer anchor the product.
|
||||||
|
|
||||||
|
## What Is Worth Preserving
|
||||||
|
Preserve only reusable copy, sequencing, or setup checklists that still improve the newer release and topology flows.
|
||||||
|
|
||||||
|
## Likely Successor Or Merge Target
|
||||||
|
/releases, /ops/platform-setup, and /setup/topology
|
||||||
|
|
||||||
|
## Static Evidence
|
||||||
|
### Routed paths
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Route files
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Menu surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Absolute page-action surfaces
|
||||||
|
- none
|
||||||
|
|
||||||
|
### Runtime references outside routes/tests
|
||||||
|
- none
|
||||||
|
|
||||||
|
## Related Docs
|
||||||
|
- [docs/modules/ui/v2-rewire/S00_route_deprecation_map.md](../../../../../../v2-rewire/S00_route_deprecation_map.md)
|
||||||
|
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../../v2-rewire/source-of-truth.md)
|
||||||
|
|
||||||
|
## Next-Pass Questions
|
||||||
|
- Check whether newer routed pages already absorbed this workflow under a different name.
|
||||||
|
- Review component templates and services for reusable UX or domain language worth salvaging.
|
||||||
|
- Validate the preservation call against current Stella Ops product docs before archival.
|
||||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user