compoennts consolidation and avoid dropping of functionality work in progress

This commit is contained in:
master
2026-03-07 16:45:18 +02:00
parent 80aa16d5a1
commit 12d7eda923
403 changed files with 25343 additions and 4 deletions

View File

@@ -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

View File

@@ -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

View File

@@ -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

View File

@@ -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

View File

@@ -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

View File

@@ -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

View File

@@ -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

View File

@@ -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

View File

@@ -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

View File

@@ -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

View File

@@ -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

View File

@@ -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

View File

@@ -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

View File

@@ -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

View File

@@ -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

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -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.

View File

@@ -0,0 +1,47 @@
# RegionDetailComponent
## Status Snapshot
- Classification: `dead`
- Confidence: `high`
- Recommendation: `archive`
- Preservation value: `low`
- Feature branch: `Release Control Legacy`
- Source: `features/release-control/regions/region-detail.component.ts`
- Selector: `app-region-detail`
## What Is It?
Region Detail appears to be a detail panel or supporting drill-down surface in the Release Control / Regions 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.

View File

@@ -0,0 +1,47 @@
# RegionsOverviewComponent
## Status Snapshot
- Classification: `dead`
- Confidence: `high`
- Recommendation: `archive`
- Preservation value: `low`
- Feature branch: `Release Control Legacy`
- Source: `features/release-control/regions/regions-overview.component.ts`
- Selector: `app-regions-overview`
## What Is It?
Regions Overview appears to be a landing or overview surface in the Release Control / Regions 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.

View File

@@ -0,0 +1,47 @@
# ReleaseControlSetupHomeComponent
## Status Snapshot
- Classification: `dead`
- Confidence: `high`
- Recommendation: `archive`
- Preservation value: `low`
- Feature branch: `Release Control Legacy`
- Source: `features/release-control/setup/release-control-setup-home.component.ts`
- Selector: `app-release-control-setup-home`
## What Is It?
Release Control Setup Home appears to be a landing or overview surface in the Release Control / Setup 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.

View File

@@ -0,0 +1,47 @@
# SetupBundleTemplatesComponent
## Status Snapshot
- Classification: `dead`
- Confidence: `high`
- Recommendation: `archive`
- Preservation value: `low`
- Feature branch: `Release Control Legacy`
- Source: `features/release-control/setup/setup-bundle-templates.component.ts`
- Selector: `app-setup-bundle-templates`
## What Is It?
Setup Bundle Templates appears to be a setup or guided workflow surface in the Release Control / Setup 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.

View File

@@ -0,0 +1,47 @@
# SetupEnvironmentsPathsComponent
## Status Snapshot
- Classification: `dead`
- Confidence: `high`
- Recommendation: `archive`
- Preservation value: `low`
- Feature branch: `Release Control Legacy`
- Source: `features/release-control/setup/setup-environments-paths.component.ts`
- Selector: `app-setup-environments-paths`
## What Is It?
Setup Environments Paths appears to be a setup or guided workflow surface in the Release Control / Setup 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.

View File

@@ -0,0 +1,47 @@
# SetupTargetsAgentsComponent
## Status Snapshot
- Classification: `dead`
- Confidence: `high`
- Recommendation: `archive`
- Preservation value: `low`
- Feature branch: `Release Control Legacy`
- Source: `features/release-control/setup/setup-targets-agents.component.ts`
- Selector: `app-setup-targets-agents`
## What Is It?
Setup Targets Agents appears to be a setup or guided workflow surface in the Release Control / Setup 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.

View File

@@ -0,0 +1,47 @@
# SetupWorkflowsComponent
## Status Snapshot
- Classification: `dead`
- Confidence: `high`
- Recommendation: `archive`
- Preservation value: `low`
- Feature branch: `Release Control Legacy`
- Source: `features/release-control/setup/setup-workflows.component.ts`
- Selector: `app-setup-workflows`
## What Is It?
Setup Workflows appears to be a setup or guided workflow surface in the Release Control / Setup 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