git.stella-ops.org/docs/modules/ui/component-preservation-map/SUMMARY_TREE.md

Summary Tree

Generated on 2026-03-07. This is the branch-level view of candidate unused or weakly surfaced UI families.

Dead

• Admin Notifications what: Admin Notifications components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Advisory Ai what: Advisory Ai components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 5 components
• Aoc what: Aoc components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Approvals what: Approvals components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 3 components
• Binary Index what: Binary Index components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Change Trace what: Change Trace components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Compare what: Compare components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 2 components
• Components what: Components components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 10 components
• Cvss what: Cvss components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Dashboard what: Dashboard components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 2 components
• Deployments what: Deployments components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Doctor what: Doctor components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Environments what: Environments components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Evidence what: Evidence components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 3 components
• Evidence Thread what: Evidence Thread components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 2 components
• Findings what: Findings components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Graph what: Graph components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 3 components
• Home what: Home components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Lineage what: Lineage components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 14 components
• Operations what: Operations components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Overlays what: Overlays components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 2 components
• Platform what: Platform components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Platform Ops Legacy what: Older operations console pages from before the current /ops shell consolidation. keep: Keep distinctive observability widgets, platform state views, and telemetry interactions that are still missing from the current ops pages. action: merge why: Ops views were consolidated under the newer platform and operations route families, leaving the older platform-ops pages behind. count: 5 components
• Policy what: Policy components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 3 components
• Policy Studio Legacy what: Legacy all-in-one policy authoring, approvals, dashboard, and simulation surfaces from the older IA. keep: Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces. action: merge why: The current route tree moved policy work into newer governance and simulation surfaces, leaving the old /policy-studio family unmounted. count: 11 components
• Promotions what: Promotions components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 2 components
• Proof Chain what: Proof Chain components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Proof Studio what: Proof Studio components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Qa what: Qa components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Reachability Witnessing what: Reachability proof, witness, and proof-of-exploit supporting surfaces. keep: Keep witness capture, proof overlays, and explainability flows that can reinforce policy and evidence decisions. action: merge why: The supporting pages and drawers are not mounted even though reachability remains a core Stella Ops differentiator. count: 2 components
• Registry Admin what: Registry Admin components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 4 components
• Release Control Legacy what: Pre-rewire release-control setup, governance, and landing pages retained after the route migration. keep: Preserve only reusable copy, sequencing, or setup checklists that still improve the newer release and topology flows. action: archive why: The canonical IA now redirects old release-control/* concepts into /releases, /ops, and /setup, so the original surfaces no longer anchor the product. count: 9 components
• Release Orchestrator what: Release Orchestrator components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 12 components
• Releases what: Releases components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 2 components
• Scores what: Scores components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Security what: Security components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 13 components
• Security Risk what: Security Risk components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Settings what: Settings components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 2 components
• Slo Monitoring what: Slo Monitoring components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 4 components
• Snapshot what: Snapshot components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Timeline what: Timeline components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Triage Workbench what: Triage experiments, workbenches, and audit-bundle side surfaces around artifact analysis. keep: Keep any explainability, quiet-lane, or audit-bundle interactions that meaningfully shorten operator triage loops. action: merge why: Several triage surfaces read as design experiments that were never folded cleanly into the main artifact workspace. count: 8 components
• Triage Inbox what: Triage Inbox components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• Ui what: Ui components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 8 components
• Unknowns what: Unknowns components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components
• VEX Studio what: Conflict-resolution and authoring surfaces around VEX decisions. keep: Keep conflict resolution workflows, rationale capture, and consensus tooling that could strengthen VEX Hub. action: merge why: The standalone studio is not mounted, but related VEX concepts and data structures still appear to matter elsewhere. count: 1 components
• Vuln Explorer what: Vuln Explorer components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 7 components
• Vulnerabilities what: Vulnerabilities components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 2 components
• Watchlist what: Operator watchlist and monitoring surfaces backed by a real client/provider but not wired into navigation. keep: Keep the operational watchlist concept, status views, and monitoring workflows; this looks closer to productizable than many other dead branches. action: wire-in why: The feature appears partially implemented but never surfaced in the current route tree or menu. count: 1 components
• Workflow Visualization Prototype what: A prototype workflow explorer with time-travel and step drill-down concepts. keep: Keep the timeline, step-diff, and replay ideas if they can strengthen evidence or release run introspection. action: investigate why: The route file exists, but nothing mounts the workflow visualization branch in the active shell. count: 3 components
• Workspaces what: Workspaces components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: investigate why: No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced. count: 1 components

Weak Route

• Ai Runs what: Ai Runs components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 2 components
• Aoc Compliance what: Aoc Compliance components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 5 components
• Audit Log what: Audit Log components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 10 components
• Bundles what: Bundles components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 2 components
• Console what: Console components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 1 components
• Console Admin what: Console Admin components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 6 components
• Deadletter what: Deadletter components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 3 components
• Evidence Export what: Evidence Export components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 2 components
• Evidence Pack what: Evidence Pack components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 1 components
• Exceptions what: Exceptions components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 1 components
• Graph what: Graph components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 1 components
• Integration Hub what: Integration Hub components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 1 components
• Issuer Trust what: Issuer Trust components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 3 components
• Jobengine what: Jobengine components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 4 components
• Mission Control what: Mission Control components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 2 components
• Notify what: Notify components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 1 components
• Offline Kit what: Offline Kit components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 4 components
• Pack Registry what: Pack Registry components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 1 components
• Platform what: Platform components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 7 components
• Platform Health what: Platform Health components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 3 components
• Platform Ops Legacy what: Older operations console pages from before the current /ops shell consolidation. keep: Keep distinctive observability widgets, platform state views, and telemetry interactions that are still missing from the current ops pages. action: merge why: Ops views were consolidated under the newer platform and operations route families, leaving the older platform-ops pages behind. count: 8 components
• Policy Governance what: Current policy governance admin subtree that looks real but still needs surface verification. keep: Preserve the full governance branch; the main question is wiring quality, not product value. action: preserve why: These pages are routed but some leaves are weakly surfaced in static analysis because their navigation appears to rely on local tabs or relative routing. count: 14 components
• Policy Studio Legacy what: Legacy all-in-one policy authoring, approvals, dashboard, and simulation surfaces from the older IA. keep: Keep the authoring concepts, simulation affordances, approvals flow, and any editor UX that is stronger than the current split surfaces. action: merge why: The current route tree moved policy work into newer governance and simulation surfaces, leaving the old /policy-studio family unmounted. count: 1 components
• Quota Dashboard what: Quota Dashboard components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 6 components
• Release Orchestrator what: Release Orchestrator components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 1 components
• Releases what: Releases components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 2 components
• Sbom Sources what: Sbom Sources components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 1 components
• Scanner Ops what: Scanner Ops components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 6 components
• Scheduler Ops what: Scheduler Ops components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 2 components
• Security what: Security components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 1 components
• Security Risk what: Security Risk components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 5 components
• Settings what: Settings components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 8 components
• Signals what: Signals components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 1 components
• Topology what: Topology components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 8 components
• Triage Workbench what: Triage experiments, workbenches, and audit-bundle side surfaces around artifact analysis. keep: Keep any explainability, quiet-lane, or audit-bundle interactions that meaningfully shorten operator triage loops. action: merge why: Several triage surfaces read as design experiments that were never folded cleanly into the main artifact workspace. count: 1 components
• Trivy Db Settings what: Trivy Db Settings components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 1 components
• Trust Admin what: Trust Admin components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 6 components
• Unknowns Tracking what: Unknowns Tracking components grouped from the static unused-component scan. keep: Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts. action: preserve why: The component is still routed, but the current scan did not find an obvious menu or absolute page-action path to it. count: 4 components