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,47 @@
# AiRunViewerComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Ai Runs`
- Source: `features/ai-runs/ai-run-viewer.component.ts`
- Selector: `stellaops-ai-run-viewer`
## What Is It?
Ai Run Viewer appears to be a dedicated feature surface in the Ai Runs area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/ai-runs/:runId`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/operations.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# AiRunsListComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Ai Runs`
- Source: `features/ai-runs/ai-runs-list.component.ts`
- Selector: `stellaops-ai-runs-list`
## What Is It?
Ai Runs List appears to be a dedicated feature surface in the Ai Runs area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/ai-runs`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/operations.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# AocComplianceDashboardComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Aoc Compliance`
- Source: `features/aoc-compliance/aoc-compliance-dashboard.component.ts`
- Selector: `app-aoc-compliance-dashboard`
## What Is It?
Aoc Compliance Dashboard appears to be a landing or overview surface in the Aoc Compliance area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/aoc`
### Route files
- `src/Web/StellaOps.Web/src/app/features/aoc-compliance/aoc-compliance.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ComplianceReportComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Aoc Compliance`
- Source: `features/aoc-compliance/compliance-report.component.ts`
- Selector: `app-compliance-report`
## What Is It?
Compliance Report appears to be a dedicated feature surface in the Aoc Compliance area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/aoc/report`
### Route files
- `src/Web/StellaOps.Web/src/app/features/aoc-compliance/aoc-compliance.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# GuardViolationsListComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Aoc Compliance`
- Source: `features/aoc-compliance/guard-violations-list.component.ts`
- Selector: `app-guard-violations-list`
## What Is It?
Guard Violations List appears to be a dedicated feature surface in the Aoc Compliance area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/aoc/violations`
### Route files
- `src/Web/StellaOps.Web/src/app/features/aoc-compliance/aoc-compliance.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# IngestionFlowComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Aoc Compliance`
- Source: `features/aoc-compliance/ingestion-flow.component.ts`
- Selector: `app-ingestion-flow`
## What Is It?
Ingestion Flow appears to be a dedicated feature surface in the Aoc Compliance area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/aoc/ingestion`
### Route files
- `src/Web/StellaOps.Web/src/app/features/aoc-compliance/aoc-compliance.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ProvenanceValidatorComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Aoc Compliance`
- Source: `features/aoc-compliance/provenance-validator.component.ts`
- Selector: `app-provenance-validator`
## What Is It?
Provenance Validator appears to be a dedicated feature surface in the Aoc Compliance area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/aoc/provenance`
### Route files
- `src/Web/StellaOps.Web/src/app/features/aoc-compliance/aoc-compliance.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# AuditAnomaliesComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Audit Log`
- Source: `features/audit-log/audit-anomalies.component.ts`
- Selector: `app-audit-anomalies`
## What Is It?
Audit Anomalies appears to be a audit and evidence surface in the Audit Log area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/evidence/audit-log/anomalies`
### Route files
- `src/Web/StellaOps.Web/src/app/features/audit-log/audit-log.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# AuditAuthorityComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Audit Log`
- Source: `features/audit-log/audit-authority.component.ts`
- Selector: `app-audit-authority`
## What Is It?
Audit Authority appears to be a audit and evidence surface in the Audit Log area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/evidence/audit-log/authority`
### Route files
- `src/Web/StellaOps.Web/src/app/features/audit-log/audit-log.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# AuditCorrelationsComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Audit Log`
- Source: `features/audit-log/audit-correlations.component.ts`
- Selector: `app-audit-correlations`
## What Is It?
Audit Correlations appears to be a audit and evidence surface in the Audit Log area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/evidence/audit-log/correlations`
### Route files
- `src/Web/StellaOps.Web/src/app/features/audit-log/audit-log.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# AuditEventDetailComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Audit Log`
- Source: `features/audit-log/audit-event-detail.component.ts`
- Selector: `app-audit-event-detail`
## What Is It?
Audit Event Detail appears to be a audit and evidence surface in the Audit Log area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/evidence/audit-log/events/:eventId`
### Route files
- `src/Web/StellaOps.Web/src/app/features/audit-log/audit-log.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# AuditExportComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Audit Log`
- Source: `features/audit-log/audit-export.component.ts`
- Selector: `app-audit-export`
## What Is It?
Audit Export appears to be a audit and evidence surface in the Audit Log area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/evidence/audit-log/export`
### Route files
- `src/Web/StellaOps.Web/src/app/features/audit-log/audit-log.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# AuditIntegrationsComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Audit Log`
- Source: `features/audit-log/audit-integrations.component.ts`
- Selector: `app-audit-integrations`
## What Is It?
Audit Integrations appears to be a audit and evidence surface in the Audit Log area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/evidence/audit-log/integrations`
### Route files
- `src/Web/StellaOps.Web/src/app/features/audit-log/audit-log.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# AuditLogTableComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Audit Log`
- Source: `features/audit-log/audit-log-table.component.ts`
- Selector: `app-audit-log-table`
## What Is It?
Audit Log Table appears to be a audit and evidence surface in the Audit Log area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/evidence/audit-log/events`
### Route files
- `src/Web/StellaOps.Web/src/app/features/audit-log/audit-log.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# AuditPolicyComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Audit Log`
- Source: `features/audit-log/audit-policy.component.ts`
- Selector: `app-audit-policy`
## What Is It?
Audit Policy appears to be a audit and evidence surface in the Audit Log area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/evidence/audit-log/policy`
### Route files
- `src/Web/StellaOps.Web/src/app/features/audit-log/audit-log.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# AuditTimelineSearchComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Audit Log`
- Source: `features/audit-log/audit-timeline-search.component.ts`
- Selector: `app-audit-timeline-search`
## What Is It?
Audit Timeline Search appears to be a audit and evidence surface in the Audit Log area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/evidence/audit-log/timeline`
### Route files
- `src/Web/StellaOps.Web/src/app/features/audit-log/audit-log.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# AuditVexComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Audit Log`
- Source: `features/audit-log/audit-vex.component.ts`
- Selector: `app-audit-vex`
## What Is It?
Audit Vex appears to be a audit and evidence surface in the Audit Log area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/evidence/audit-log/vex`
### Route files
- `src/Web/StellaOps.Web/src/app/features/audit-log/audit-log.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# BundleDetailComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Bundles`
- Source: `features/bundles/bundle-detail.component.ts`
- Selector: `app-bundle-detail`
## What Is It?
Bundle Detail appears to be a detail panel or supporting drill-down surface in the Bundles area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/releases/bundles/:bundleId`
### Route files
- `src/Web/StellaOps.Web/src/app/features/bundles/bundles.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# BundleVersionDetailComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Bundles`
- Source: `features/bundles/bundle-version-detail.component.ts`
- Selector: `app-bundle-version-detail`
## What Is It?
Bundle Version Detail appears to be a detail panel or supporting drill-down surface in the Bundles area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/releases/bundles/:bundleId/versions/:versionId`
### Route files
- `src/Web/StellaOps.Web/src/app/features/bundles/bundles.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ConsoleAdminLayoutComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Console Admin`
- Source: `features/console-admin/console-admin-layout.component.ts`
- Selector: `app-console-admin-layout`
## What Is It?
Console Admin Layout appears to be a dedicated feature surface in the Console Admin area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/console-admin`
### Route files
- `src/Web/StellaOps.Web/src/app/features/console-admin/console-admin.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ClientsListComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Console Admin`
- Source: `features/console-admin/clients/clients-list.component.ts`
- Selector: `app-clients-list`
## What Is It?
Clients List appears to be a dedicated feature surface in the Console Admin / Clients area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/console-admin/clients`
### Route files
- `src/Web/StellaOps.Web/src/app/features/console-admin/console-admin.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# RolesListComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Console Admin`
- Source: `features/console-admin/roles/roles-list.component.ts`
- Selector: `app-roles-list`
## What Is It?
Roles List appears to be a dedicated feature surface in the Console Admin / Roles area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/console-admin/roles`
### Route files
- `src/Web/StellaOps.Web/src/app/features/console-admin/console-admin.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,48 @@
# TenantsListComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Console Admin`
- Source: `features/console-admin/tenants/tenants-list.component.ts`
- Selector: `app-tenants-list`
## What Is It?
Tenants List appears to be a dedicated feature surface in the Console Admin / Tenants area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/console-admin`
- `/console-admin/tenants`
### Route files
- `src/Web/StellaOps.Web/src/app/features/console-admin/console-admin.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# TokensListComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Console Admin`
- Source: `features/console-admin/tokens/tokens-list.component.ts`
- Selector: `app-tokens-list`
## What Is It?
Tokens List appears to be a dedicated feature surface in the Console Admin / Tokens area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/console-admin/tokens`
### Route files
- `src/Web/StellaOps.Web/src/app/features/console-admin/console-admin.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# UsersListComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Console Admin`
- Source: `features/console-admin/users/users-list.component.ts`
- Selector: `app-users-list`
## What Is It?
Users List appears to be a dedicated feature surface in the Console Admin / Users area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/console-admin/users`
### Route files
- `src/Web/StellaOps.Web/src/app/features/console-admin/console-admin.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ConsoleProfileComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Console`
- Source: `features/console/console-profile.component.ts`
- Selector: `app-console-profile`
## What Is It?
Console Profile appears to be a dedicated feature surface in the Console area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/administration/profile`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/administration.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# DeadLetterDashboardComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Deadletter`
- Source: `features/deadletter/deadletter-dashboard.component.ts`
- Selector: `app-deadletter-dashboard`
## What Is It?
Dead Letter Dashboard appears to be a landing or overview surface in the Deadletter area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/dead-letter`
### Route files
- `src/Web/StellaOps.Web/src/app/features/deadletter/deadletter.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# DeadLetterEntryDetailComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Deadletter`
- Source: `features/deadletter/deadletter-entry-detail.component.ts`
- Selector: `app-deadletter-entry-detail`
## What Is It?
Dead Letter Entry Detail appears to be a detail panel or supporting drill-down surface in the Deadletter area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/dead-letter/entry/:entryId`
### Route files
- `src/Web/StellaOps.Web/src/app/features/deadletter/deadletter.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# DeadLetterQueueComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Deadletter`
- Source: `features/deadletter/deadletter-queue.component.ts`
- Selector: `app-deadletter-queue`
## What Is It?
Dead Letter Queue appears to be a dedicated feature surface in the Deadletter area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/dead-letter/queue`
### Route files
- `src/Web/StellaOps.Web/src/app/features/deadletter/deadletter.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# EvidenceBundlesComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Evidence Export`
- Source: `features/evidence-export/evidence-bundles.component.ts`
- Selector: `app-evidence-bundles`
## What Is It?
Evidence Bundles appears to be a dedicated feature surface in the Evidence Export area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/evidence/exports/bundles`
### Route files
- `src/Web/StellaOps.Web/src/app/features/evidence-export/evidence-export.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ProvenanceVisualizationComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Evidence Export`
- Source: `features/evidence-export/provenance-visualization.component.ts`
- Selector: `app-provenance-visualization`
## What Is It?
Provenance Visualization appears to be a visualization or exploration surface in the Evidence Export area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/evidence/exports/provenance`
### Route files
- `src/Web/StellaOps.Web/src/app/features/evidence-export/evidence-export.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# EvidencePackViewerComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Evidence Pack`
- Source: `features/evidence-pack/evidence-pack-viewer.component.ts`
- Selector: `stellaops-evidence-pack-viewer`
## What Is It?
Evidence Pack Viewer appears to be a dedicated feature surface in the Evidence Pack area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/evidence/capsules/:capsuleId`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/evidence.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ExceptionApprovalQueueComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Exceptions`
- Source: `features/exceptions/exception-approval-queue.component.ts`
- Selector: `app-exception-approval-queue`
## What Is It?
Exception Approval Queue appears to be a approval and review surface in the Exceptions area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/security/exceptions/approvals`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/security-risk.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# GraphExplorerComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Graph`
- Source: `features/graph/graph-explorer.component.ts`
- Selector: `app-graph-explorer`
## What Is It?
Graph Explorer appears to be a visualization or exploration surface in the Graph area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/security/sbom/graph`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/security-risk.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,48 @@
# IntegrationActivityComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Integration Hub`
- Source: `features/integration-hub/integration-activity.component.ts`
- Selector: `app-integration-activity`
## What Is It?
Integration Activity appears to be a dedicated feature surface in the Integration Hub area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/integrations/activity`
- `/setup/integrations/activity`
### Route files
- `src/Web/StellaOps.Web/src/app/features/integration-hub/integration-hub.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# IssuerDetailComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Issuer Trust`
- Source: `features/issuer-trust/components/issuer-detail.component.ts`
- Selector: `app-issuer-detail`
## What Is It?
Issuer Detail appears to be a detail panel or supporting drill-down surface in the Issuer Trust / Components area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/administration/trust/issuers/:issuerId`
### Route files
- `src/Web/StellaOps.Web/src/app/features/issuer-trust/issuer-trust.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# IssuerEditorComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Issuer Trust`
- Source: `features/issuer-trust/components/issuer-editor.component.ts`
- Selector: `app-issuer-editor`
## What Is It?
Issuer Editor appears to be a authoring or editing surface in the Issuer Trust / Components area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/administration/trust/issuers/new`
### Route files
- `src/Web/StellaOps.Web/src/app/features/issuer-trust/issuer-trust.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,48 @@
# IssuerListComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Issuer Trust`
- Source: `features/issuer-trust/components/issuer-list.component.ts`
- Selector: `app-issuer-list`
## What Is It?
Issuer List appears to be a dedicated feature surface in the Issuer Trust / Components area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/administration/trust/issuers`
- `/administration/trust/issuers/list`
### Route files
- `src/Web/StellaOps.Web/src/app/features/issuer-trust/issuer-trust.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# JobEngineDashboardComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Jobengine`
- Source: `features/jobengine/jobengine-dashboard.component.ts`
- Selector: `app-jobengine-dashboard`
## What Is It?
Job Engine Dashboard appears to be a landing or overview surface in the Jobengine area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/jobengine`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/operations.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# JobEngineJobDetailComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Jobengine`
- Source: `features/jobengine/jobengine-job-detail.component.ts`
- Selector: `app-jobengine-job-detail`
## What Is It?
Job Engine Job Detail appears to be a detail panel or supporting drill-down surface in the Jobengine area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/orchestrator/jobs/:jobId`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/operations.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# JobEngineJobsComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Jobengine`
- Source: `features/jobengine/jobengine-jobs.component.ts`
- Selector: `app-jobengine-jobs`
## What Is It?
Job Engine Jobs appears to be a dedicated feature surface in the Jobengine area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/jobengine/jobs`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/operations.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# JobEngineQuotasComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Jobengine`
- Source: `features/jobengine/jobengine-quotas.component.ts`
- Selector: `app-jobengine-quotas`
## What Is It?
Job Engine Quotas appears to be a dedicated feature surface in the Jobengine area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/jobengine/quotas`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/operations.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,48 @@
# MissionActivityPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Mission Control`
- Source: `features/mission-control/mission-activity-page.component.ts`
- Selector: `app-mission-activity-page`
## What Is It?
Mission Activity Page appears to be a dedicated feature surface in the Mission Control area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/**/activity`
- `/mission-control/activity`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/mission-control.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,48 @@
# MissionAlertsPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Mission Control`
- Source: `features/mission-control/mission-alerts-page.component.ts`
- Selector: `app-mission-alerts-page`
## What Is It?
Mission Alerts Page appears to be a monitoring and alerting surface in the Mission Control area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/**/alerts`
- `/mission-control/alerts`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/mission-control.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# NotifyPanelComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Notify`
- Source: `features/notify/notify-panel.component.ts`
- Selector: `app-notify-panel`
## What Is It?
Notify Panel appears to be a detail panel or supporting drill-down surface in the Notify area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/notifications`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/operations.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# BundleManagementComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Offline Kit`
- Source: `features/offline-kit/components/bundle-management.component.ts`
- Selector: `app-bundle-management`
## What Is It?
Bundle Management appears to be a dedicated feature surface in the Offline Kit / Components area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/offline-kit/bundles`
### Route files
- `src/Web/StellaOps.Web/src/app/features/offline-kit/offline-kit.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# JwksManagementComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Offline Kit`
- Source: `features/offline-kit/components/jwks-management.component.ts`
- Selector: `app-jwks-management`
## What Is It?
Jwks Management appears to be a dedicated feature surface in the Offline Kit / Components area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/offline-kit/jwks`
### Route files
- `src/Web/StellaOps.Web/src/app/features/offline-kit/offline-kit.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,52 @@
# OfflineDashboardComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Offline Kit`
- Source: `features/offline-kit/components/offline-dashboard.component.ts`
- Selector: `app-offline-dashboard`
## What Is It?
Offline Dashboard appears to be a landing or overview surface in the Offline Kit / Components area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/administration/offline`
- `/ops/operations/offline-kit`
- `/ops/operations/offline-kit/dashboard`
- `/settings/offline`
### Route files
- `src/Web/StellaOps.Web/src/app/features/offline-kit/offline-kit.routes.ts`
- `src/Web/StellaOps.Web/src/app/features/settings/settings.routes.ts`
- `src/Web/StellaOps.Web/src/app/routes/administration.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# VerificationCenterComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Offline Kit`
- Source: `features/offline-kit/components/verification-center.component.ts`
- Selector: `app-verification-center`
## What Is It?
Verification Center appears to be a dedicated feature surface in the Offline Kit / Components area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/offline-kit/verify`
### Route files
- `src/Web/StellaOps.Web/src/app/features/offline-kit/offline-kit.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# PackRegistryBrowserComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Pack Registry`
- Source: `features/pack-registry/pack-registry-browser.component.ts`
- Selector: `app-pack-registry-browser`
## What Is It?
Pack Registry Browser appears to be a dedicated feature surface in the Pack Registry area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/packs`
### Route files
- `src/Web/StellaOps.Web/src/app/features/pack-registry/pack-registry.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# IncidentTimelineComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Platform Health`
- Source: `features/platform-health/incident-timeline.component.ts`
- Selector: `app-incident-timeline`
## What Is It?
Incident Timeline appears to be a visualization or exploration surface in the Platform Health area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/health-slo/incidents`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform-health/platform-health.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# PlatformHealthDashboardComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Platform Health`
- Source: `features/platform-health/platform-health-dashboard.component.ts`
- Selector: `app-platform-health-dashboard`
## What Is It?
Platform Health Dashboard appears to be a landing or overview surface in the Platform Health area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/health-slo`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform-health/platform-health.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ServiceDetailComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Platform Health`
- Source: `features/platform-health/service-detail.component.ts`
- Selector: `app-service-detail`
## What Is It?
Service Detail appears to be a detail panel or supporting drill-down surface in the Platform Health area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/health-slo/services/:serviceName`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform-health/platform-health.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# DataIntegrityJobRunDetailPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `merge`
- Preservation value: `medium`
- Feature branch: `Platform Ops Legacy`
- Source: `features/platform-ops/data-integrity/job-run-detail-page.component.ts`
- Selector: `app-data-integrity-job-run-detail-page`
## What Is It?
Data Integrity Job Run Detail Page appears to be a detail panel or supporting drill-down surface in the Platform Ops / Data Integrity 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
- `/ops/operations/data-integrity/nightly-ops/:runId`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform-ops/data-integrity/data-integrity.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# DataQualitySlosPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `merge`
- Preservation value: `medium`
- Feature branch: `Platform Ops Legacy`
- Source: `features/platform-ops/data-integrity/data-quality-slos-page.component.ts`
- Selector: `app-data-quality-slos-page`
## What Is It?
Data Quality Slos Page appears to be a dedicated feature surface in the Platform Ops / Data Integrity 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
- `/ops/operations/data-integrity/slos`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform-ops/data-integrity/data-integrity.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# DlqReplaysPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `merge`
- Preservation value: `medium`
- Feature branch: `Platform Ops Legacy`
- Source: `features/platform-ops/data-integrity/dlq-replays-page.component.ts`
- Selector: `app-dlq-replays-page`
## What Is It?
Dlq Replays Page appears to be a dedicated feature surface in the Platform Ops / Data Integrity 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
- `/ops/operations/data-integrity/dlq`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform-ops/data-integrity/data-integrity.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# FeedsFreshnessPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `merge`
- Preservation value: `medium`
- Feature branch: `Platform Ops Legacy`
- Source: `features/platform-ops/data-integrity/feeds-freshness-page.component.ts`
- Selector: `app-feeds-freshness-page`
## What Is It?
Feeds Freshness Page appears to be a dedicated feature surface in the Platform Ops / Data Integrity 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
- `/ops/operations/data-integrity/feeds-freshness`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform-ops/data-integrity/data-integrity.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# IntegrationConnectivityPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `merge`
- Preservation value: `medium`
- Feature branch: `Platform Ops Legacy`
- Source: `features/platform-ops/data-integrity/integration-connectivity-page.component.ts`
- Selector: `app-integration-connectivity-page`
## What Is It?
Integration Connectivity Page appears to be a dedicated feature surface in the Platform Ops / Data Integrity 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
- `/ops/operations/data-integrity/integration-connectivity`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform-ops/data-integrity/data-integrity.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# NightlyOpsReportPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `merge`
- Preservation value: `medium`
- Feature branch: `Platform Ops Legacy`
- Source: `features/platform-ops/data-integrity/nightly-ops-report-page.component.ts`
- Selector: `app-nightly-ops-report-page`
## What Is It?
Nightly Ops Report Page appears to be a dedicated feature surface in the Platform Ops / Data Integrity 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
- `/ops/operations/data-integrity/nightly-ops`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform-ops/data-integrity/data-integrity.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ReachabilityIngestHealthPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `merge`
- Preservation value: `medium`
- Feature branch: `Platform Ops Legacy`
- Source: `features/platform-ops/data-integrity/reachability-ingest-health-page.component.ts`
- Selector: `app-reachability-ingest-health-page`
## What Is It?
Reachability Ingest Health Page appears to be a dedicated feature surface in the Platform Ops / Data Integrity 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
- `/ops/operations/data-integrity/reachability-ingest`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform-ops/data-integrity/data-integrity.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ScanPipelineHealthPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `merge`
- Preservation value: `medium`
- Feature branch: `Platform Ops Legacy`
- Source: `features/platform-ops/data-integrity/scan-pipeline-health-page.component.ts`
- Selector: `app-scan-pipeline-health-page`
## What Is It?
Scan Pipeline Health Page appears to be a dedicated feature surface in the Platform Ops / Data Integrity 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
- `/ops/operations/data-integrity/scan-pipeline`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform-ops/data-integrity/data-integrity.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# PlatformSetupDefaultsGuardrailsPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Platform`
- Source: `features/platform/setup/platform-setup-defaults-guardrails-page.component.ts`
- Selector: `app-platform-setup-defaults-guardrails-page`
## What Is It?
Platform Setup Defaults Guardrails Page appears to be a setup or guided workflow surface in the Platform / Setup area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/platform-setup/defaults-guardrails`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform/setup/platform-setup.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# PlatformSetupFeedPolicyPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Platform`
- Source: `features/platform/setup/platform-setup-feed-policy-page.component.ts`
- Selector: `app-platform-setup-feed-policy-page`
## What Is It?
Platform Setup Feed Policy Page appears to be a setup or guided workflow surface in the Platform / Setup area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/platform-setup/policy-bindings`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform/setup/platform-setup.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# PlatformSetupGateProfilesPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Platform`
- Source: `features/platform/setup/platform-setup-gate-profiles-page.component.ts`
- Selector: `app-platform-setup-gate-profiles-page`
## What Is It?
Platform Setup Gate Profiles Page appears to be a setup or guided workflow surface in the Platform / Setup area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/platform-setup/gate-profiles`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform/setup/platform-setup.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# PlatformSetupPromotionPathsPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Platform`
- Source: `features/platform/setup/platform-setup-promotion-paths-page.component.ts`
- Selector: `app-platform-setup-promotion-paths-page`
## What Is It?
Platform Setup Promotion Paths Page appears to be a setup or guided workflow surface in the Platform / Setup area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/platform-setup/promotion-paths`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform/setup/platform-setup.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# PlatformSetupRegionsEnvironmentsPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Platform`
- Source: `features/platform/setup/platform-setup-regions-environments-page.component.ts`
- Selector: `app-platform-setup-regions-environments-page`
## What Is It?
Platform Setup Regions Environments Page appears to be a setup or guided workflow surface in the Platform / Setup area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/platform-setup/regions-environments`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform/setup/platform-setup.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# PlatformSetupReleaseTemplatesPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Platform`
- Source: `features/platform/setup/platform-setup-release-templates-page.component.ts`
- Selector: `app-platform-setup-release-templates-page`
## What Is It?
Platform Setup Release Templates Page appears to be a setup or guided workflow surface in the Platform / Setup area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/platform-setup/release-templates`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform/setup/platform-setup.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# PlatformSetupWorkflowsGatesPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Platform`
- Source: `features/platform/setup/platform-setup-workflows-gates-page.component.ts`
- Selector: `app-platform-setup-workflows-gates-page`
## What Is It?
Platform Setup Workflows Gates Page appears to be a setup or guided workflow surface in the Platform / Setup area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/platform-setup/workflows-gates`
### Route files
- `src/Web/StellaOps.Web/src/app/features/platform/setup/platform-setup.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,49 @@
# ConflictResolutionWizardComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/conflict-resolution-wizard.component.ts`
- Selector: `app-conflict-resolution-wizard`
## What Is It?
Conflict Resolution Wizard appears to be a setup or guided workflow surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/conflicts/:conflictId/resolve`
- `/administration/policy/governance/conflicts/:conflictId/resolve`
- `/ops/policy/conflicts/:conflictId/resolve`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,49 @@
# GovernanceAuditComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/governance-audit.component.ts`
- Selector: `app-governance-audit`
## What Is It?
Governance Audit appears to be a audit and evidence surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/audit`
- `/administration/policy/governance/audit`
- `/ops/policy/audit`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,49 @@
# ImpactPreviewComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/impact-preview.component.ts`
- Selector: `app-impact-preview`
## What Is It?
Impact Preview appears to be a approval and review surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/impact-preview`
- `/administration/policy/governance/impact-preview`
- `/ops/policy/impact-preview`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,49 @@
# PolicyConflictDashboardComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/policy-conflict-dashboard.component.ts`
- Selector: `app-policy-conflict-dashboard`
## What Is It?
Policy Conflict Dashboard appears to be a landing or overview surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/conflicts`
- `/administration/policy/governance/conflicts`
- `/ops/policy/conflicts`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,49 @@
# PolicyValidatorComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/policy-validator.component.ts`
- Selector: `app-policy-validator`
## What Is It?
Policy Validator appears to be a dedicated feature surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/validator`
- `/administration/policy/governance/validator`
- `/ops/policy/validator`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,52 @@
# RiskBudgetConfigComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/risk-budget-config.component.ts`
- Selector: `app-risk-budget-config`
## What Is It?
Risk Budget Config appears to be a dedicated feature surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/budget/config`
- `/administration/policy-governance/risk-budget/config`
- `/administration/policy/governance/budget/config`
- `/administration/policy/governance/risk-budget/config`
- `/ops/policy/budget/config`
- `/ops/policy/risk-budget/config`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,52 @@
# RiskProfileEditorComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/risk-profile-editor.component.ts`
- Selector: `app-risk-profile-editor`
## What Is It?
Risk Profile Editor appears to be a authoring or editing surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/profiles/:profileId`
- `/administration/policy-governance/profiles/new`
- `/administration/policy/governance/profiles/:profileId`
- `/administration/policy/governance/profiles/new`
- `/ops/policy/profiles/:profileId`
- `/ops/policy/profiles/new`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,49 @@
# RiskProfileListComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/risk-profile-list.component.ts`
- Selector: `app-risk-profile-list`
## What Is It?
Risk Profile List appears to be a dedicated feature surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/profiles`
- `/administration/policy/governance/profiles`
- `/ops/policy/profiles`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,49 @@
# SchemaDocsComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/schema-docs.component.ts`
- Selector: `app-schema-docs`
## What Is It?
Schema Docs appears to be a dedicated feature surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/schema-docs`
- `/administration/policy/governance/schema-docs`
- `/ops/policy/schema-docs`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,49 @@
# SchemaPlaygroundComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/schema-playground.component.ts`
- Selector: `app-schema-playground`
## What Is It?
Schema Playground appears to be a dedicated feature surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/schema-playground`
- `/administration/policy/governance/schema-playground`
- `/ops/policy/schema-playground`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,49 @@
# SealedModeControlComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/sealed-mode-control.component.ts`
- Selector: `app-sealed-mode-control`
## What Is It?
Sealed Mode Control appears to be a dedicated feature surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/sealed-mode`
- `/administration/policy/governance/sealed-mode`
- `/ops/policy/sealed-mode`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,49 @@
# SealedModeOverridesComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/sealed-mode-overrides.component.ts`
- Selector: `app-sealed-mode-overrides`
## What Is It?
Sealed Mode Overrides appears to be a dedicated feature surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/sealed-mode/overrides`
- `/administration/policy/governance/sealed-mode/overrides`
- `/ops/policy/sealed-mode/overrides`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,49 @@
# StalenessConfigComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/staleness-config.component.ts`
- Selector: `app-staleness-config`
## What Is It?
Staleness Config appears to be a dedicated feature surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/staleness`
- `/administration/policy/governance/staleness`
- `/ops/policy/staleness`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,49 @@
# TrustWeightingComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Policy Governance`
- Source: `features/policy-governance/trust-weighting.component.ts`
- Selector: `app-trust-weighting`
## What Is It?
Trust Weighting appears to be a dedicated feature surface in the Policy Governance area.
## Why It Likely Fell Out Of The Product
These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing.
## What Is Worth Preserving
Preserve the full governance branch; the main question is wiring quality, not product value.
## Likely Successor Or Merge Target
/admin/policy/governance
## Static Evidence
### Routed paths
- `/administration/policy-governance/trust-weights`
- `/administration/policy/governance/trust-weights`
- `/ops/policy/trust-weights`
### Route files
- `src/Web/StellaOps.Web/src/app/features/policy-governance/policy-governance.routes.ts`
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/v2-rewire/source-of-truth.md](../../../../../v2-rewire/source-of-truth.md)
- [docs/contracts/policy-studio.md](../../../../../../../contracts/policy-studio.md)
## Next-Pass Questions
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,49 @@
# PolicyWorkspaceComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `merge`
- Preservation value: `high`
- Feature branch: `Policy Studio Legacy`
- Source: `features/policy-studio/workspace/policy-workspace.component.ts`
- Selector: `app-policy-workspace`
## What Is It?
Policy Workspace appears to be a dedicated feature surface in the Policy Studio / Workspace 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
- `/administration/policy/packs`
- `/administration/policy/packs/:packId`
- `/administration/policy/packs/:packId/:page`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/administration.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# QuotaAlertConfigComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Quota Dashboard`
- Source: `features/quota-dashboard/quota-alert-config.component.ts`
- Selector: `app-quota-alert-config`
## What Is It?
Quota Alert Config appears to be a monitoring and alerting surface in the Quota Dashboard area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/quotas/alerts`
### Route files
- `src/Web/StellaOps.Web/src/app/features/quota-dashboard/quota.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# QuotaForecastComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Quota Dashboard`
- Source: `features/quota-dashboard/quota-forecast.component.ts`
- Selector: `app-quota-forecast`
## What Is It?
Quota Forecast appears to be a dedicated feature surface in the Quota Dashboard area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/quotas/forecast`
### Route files
- `src/Web/StellaOps.Web/src/app/features/quota-dashboard/quota.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# QuotaReportExportComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Quota Dashboard`
- Source: `features/quota-dashboard/quota-report-export.component.ts`
- Selector: `app-quota-report-export`
## What Is It?
Quota Report Export appears to be a dedicated feature surface in the Quota Dashboard area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/quotas/reports`
### Route files
- `src/Web/StellaOps.Web/src/app/features/quota-dashboard/quota.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# TenantQuotaDetailComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Quota Dashboard`
- Source: `features/quota-dashboard/tenant-quota-detail.component.ts`
- Selector: `app-tenant-quota-detail`
## What Is It?
Tenant Quota Detail appears to be a detail panel or supporting drill-down surface in the Quota Dashboard area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/quotas/tenants/:tenantId`
### Route files
- `src/Web/StellaOps.Web/src/app/features/quota-dashboard/quota.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# TenantQuotaTableComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Quota Dashboard`
- Source: `features/quota-dashboard/tenant-quota-table.component.ts`
- Selector: `app-tenant-quota-table`
## What Is It?
Tenant Quota Table appears to be a dedicated feature surface in the Quota Dashboard area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/quotas/tenants`
### Route files
- `src/Web/StellaOps.Web/src/app/features/quota-dashboard/quota.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ThrottleContextComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Quota Dashboard`
- Source: `features/quota-dashboard/throttle-context.component.ts`
- Selector: `app-throttle-context`
## What Is It?
Throttle Context appears to be a dedicated feature surface in the Quota Dashboard area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/quotas/throttle`
### Route files
- `src/Web/StellaOps.Web/src/app/features/quota-dashboard/quota.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# WorkflowEditorComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Release Orchestrator`
- Source: `features/release-orchestrator/workflows/workflow-editor/workflow-editor.component.ts`
- Selector: `app-workflow-editor`
## What Is It?
Workflow Editor appears to be a authoring or editing surface in the Release Orchestrator / Workflows / Workflow Editor area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/administration/workflows/:id`
### Route files
- `src/Web/StellaOps.Web/src/app/features/release-orchestrator/workflows/workflows.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# HotfixDetailPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Releases`
- Source: `features/releases/hotfix-detail-page.component.ts`
- Selector: `app-hotfix-detail-page`
## What Is It?
Hotfix Detail Page appears to be a detail panel or supporting drill-down surface in the Releases area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/releases/hotfixes/:hotfixId`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/releases.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ReleaseOpsOverviewPageComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Releases`
- Source: `features/releases/release-ops-overview-page.component.ts`
- Selector: `app-release-ops-overview-page`
## What Is It?
Release Ops Overview Page appears to be a landing or overview surface in the Releases area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/releases/overview`
### Route files
- `src/Web/StellaOps.Web/src/app/routes/releases.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,50 @@
# SourceWizardComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Sbom Sources`
- Source: `features/sbom-sources/components/source-wizard/source-wizard.component.ts`
- Selector: `app-source-wizard`
## What Is It?
Source Wizard appears to be a setup or guided workflow surface in the Sbom Sources / Components / Source Wizard area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/integrations/sbom-sources/:id/edit`
- `/ops/integrations/sbom-sources/new`
- `/setup/integrations/sbom-sources/:id/edit`
- `/setup/integrations/sbom-sources/new`
### Route files
- `src/Web/StellaOps.Web/src/app/features/sbom-sources/sbom-sources.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ScannerOpsComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Scanner Ops`
- Source: `features/scanner-ops/scanner-ops.component.ts`
- Selector: `app-scanner-ops`
## What Is It?
Scanner Ops appears to be a dedicated feature surface in the Scanner Ops area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/scanner-ops`
### Route files
- `src/Web/StellaOps.Web/src/app/features/scanner-ops/scanner-ops.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# AnalyzerHealthComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Scanner Ops`
- Source: `features/scanner-ops/components/analyzer-health.component.ts`
- Selector: `app-analyzer-health`
## What Is It?
Analyzer Health appears to be a dedicated feature surface in the Scanner Ops / Components area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/scanner-ops/analyzers`
### Route files
- `src/Web/StellaOps.Web/src/app/features/scanner-ops/scanner-ops.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# BaselineListComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Scanner Ops`
- Source: `features/scanner-ops/components/baseline-list.component.ts`
- Selector: `app-baseline-list`
## What Is It?
Baseline List appears to be a dedicated feature surface in the Scanner Ops / Components area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/scanner-ops/baselines`
### Route files
- `src/Web/StellaOps.Web/src/app/features/scanner-ops/scanner-ops.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# DeterminismSettingsComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Scanner Ops`
- Source: `features/scanner-ops/components/determinism-settings.component.ts`
- Selector: `app-determinism-settings`
## What Is It?
Determinism Settings appears to be a dedicated feature surface in the Scanner Ops / Components area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/scanner-ops/settings`
### Route files
- `src/Web/StellaOps.Web/src/app/features/scanner-ops/scanner-ops.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,48 @@
# OfflineKitListComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Scanner Ops`
- Source: `features/scanner-ops/components/offline-kit-list.component.ts`
- Selector: `app-offline-kit-list`
## What Is It?
Offline Kit List appears to be a dedicated feature surface in the Scanner Ops / Components area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/scanner-ops`
- `/ops/scanner-ops/offline-kits`
### Route files
- `src/Web/StellaOps.Web/src/app/features/scanner-ops/scanner-ops.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# PerformanceBaselineComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Scanner Ops`
- Source: `features/scanner-ops/components/performance-baseline.component.ts`
- Selector: `app-performance-baseline`
## What Is It?
Performance Baseline appears to be a dedicated feature surface in the Scanner Ops / Components area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/scanner-ops/performance`
### Route files
- `src/Web/StellaOps.Web/src/app/features/scanner-ops/scanner-ops.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

View File

@@ -0,0 +1,47 @@
# ScheduleManagementComponent
## Status Snapshot
- Classification: `weak-route`
- Confidence: `medium`
- Recommendation: `preserve`
- Preservation value: `high`
- Feature branch: `Scheduler Ops`
- Source: `features/scheduler-ops/schedule-management.component.ts`
- Selector: `app-schedule-management`
## What Is It?
Schedule Management appears to be a dedicated feature surface in the Scheduler Ops area.
## Why It Likely Fell Out Of The Product
The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it.
## 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
- `/ops/operations/scheduler/schedules`
### Route files
- `src/Web/StellaOps.Web/src/app/features/scheduler-ops/scheduler-ops.routes.ts`
### 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
- Confirm whether the route is reachable only through relative child-tab navigation.
- Check the corresponding product/docs promise before treating the page as dropped.
- Verify whether the route should be linked from the current shell or intentionally remain deep-linked only.

Some files were not shown because too many files have changed in this diff Show More