Finalize UI truthfulness and bootstrap hardening

This commit is contained in:
master
2026-04-16 16:23:54 +03:00
parent 4799aa2402
commit bc6b1c5959
145 changed files with 10503 additions and 9837 deletions

View File

@@ -199,7 +199,7 @@ Each feature folder builds as a **standalone route** (lazy loaded). All HTTP sha
* **Implicit route weighting**: global search always prefers current-page evidence first and renders cross-scope overflow as a quiet secondary section only when it materially improves the answer.
* **Answer-first search**: every non-empty search renders a visible answer panel before raw cards; the panel resolves to `grounded`, `clarify`, or `insufficient` and never leaves the operator with a blank result area.
* **Page-owned self-serve questions**: priority pages define common questions and clarifying prompts in the shared search context registry; empty-state search uses those as starter questions and answer states reuse them as follow-up or clarification buttons.
* **Priority route rollout**: mocked end-to-end journeys explicitly cover findings, policy, doctor, timeline, and release-control routes; live ingestion-backed route verification remains required where corpus parity already exists.
* **Priority route rollout**: integration activity, export center, offline-kit bundle management, setup topology, configuration pane, policy governance conflicts, and image security now require live route rechecks against mounted flows. Mock-only journey coverage is no longer sufficient for those routes.
* **Suggestion executability gate**: contextual/page starters preflight through backend viability signals before render so dead suggestions are suppressed instead of being taught to the user.
* **Ambient payload activation**: each global search request sends ambient context (`currentRoute`, `visibleEntityKeys`, `recentSearches`, `sessionId`, optional `lastAction`) so AdvisoryAI can apply contextual ranking and answer shaping.
* **Contract governance**: contextual chips follow `docs/modules/ui/search-chip-context-contract.md`, while self-serve questions, rollout ownership, and fallback states follow `docs/modules/ui/search-self-serve-contract.md`; both are implemented in `search-context.registry.ts`.

View File

@@ -1,47 +0,0 @@
# NodeDiffTableComponent
## Status Snapshot
- Classification: `dead`
- Confidence: `high`
- Recommendation: `investigate`
- Preservation value: `medium`
- Feature branch: `Lineage`
- Source: `features/lineage/components/node-diff-table/diff-table.component.ts`
- Selector: `app-node-diff-table`
## What Is It?
Node Diff Table appears to be a dedicated feature surface in the Lineage / Components / Node Diff Table area.
## Why It Likely Fell Out Of The Product
No route or runtime references remain in the current Angular shell, which suggests the surface was dropped or replaced.
## What Is Worth Preserving
Preserve the underlying workflow only if current product docs still claim the capability or if the component contains unique UI concepts.
## Likely Successor Or Merge Target
Needs branch-level review against current IA
## Static Evidence
### Routed paths
- none
### Route files
- none
### Menu surfaces
- none
### Absolute page-action surfaces
- none
### Runtime references outside routes/tests
- none
## Related Docs
- [docs/modules/ui/README.md](../../../../../../../README.md)
- [docs/modules/ui/architecture.md](../../../../../../../architecture.md)
## Next-Pass Questions
- Check whether newer routed pages already absorbed this workflow under a different name.
- Review component templates and services for reusable UX or domain language worth salvaging.
- Validate the preservation call against current Stella Ops product docs before archival.

View File

@@ -2,7 +2,7 @@
## Branch Summary
- Classification bucket: `dead`
- Components in branch: 14
- Components in branch: 13
- Default recommendation: `investigate`
- Preservation value: `medium`
@@ -27,5 +27,4 @@ Needs branch-level review against current IA
- [LineageProvenanceCompareComponent](../features/lineage/components/lineage-provenance-compare/LineageProvenanceCompareComponent.md) - `investigate`, features/lineage/components/lineage-provenance-compare/lineage-provenance-compare.component.ts
- [LineageSbomDiffComponent](../features/lineage/components/lineage-sbom-diff/LineageSbomDiffComponent.md) - `investigate`, features/lineage/components/lineage-sbom-diff/lineage-sbom-diff.component.ts
- [LineageVexDiffComponent](../features/lineage/components/lineage-vex-diff/LineageVexDiffComponent.md) - `investigate`, features/lineage/components/lineage-vex-diff/lineage-vex-diff.component.ts
- [NodeDiffTableComponent](../features/lineage/components/node-diff-table/NodeDiffTableComponent.md) - `investigate`, features/lineage/components/node-diff-table/diff-table.component.ts
- [PinnedPanelComponent](../features/lineage/components/pinned-explanation/pinned-panel/PinnedPanelComponent.md) - `investigate`, features/lineage/components/pinned-explanation/pinned-panel/pinned-panel.component.ts

View File

@@ -1150,28 +1150,6 @@
],
"likelyDestination": "Needs branch-level review against current IA"
},
{
"className": "NodeDiffTableComponent",
"selector": "app-node-diff-table",
"classification": "dead",
"confidence": "high",
"recommendation": "investigate",
"preservationValue": "medium",
"family": "lineage",
"branchKey": "lineage",
"branchTitle": "Lineage",
"source": "features/lineage/components/node-diff-table/diff-table.component.ts",
"routePaths": [],
"routeFiles": [],
"menuSurfaceFiles": [],
"actionSurfaceFiles": [],
"runtimeRefs": [],
"relatedDocs": [
"docs/modules/ui/README.md",
"docs/modules/ui/architecture.md"
],
"likelyDestination": "Needs branch-level review against current IA"
},
{
"className": "PinnedPanelComponent",
"selector": "app-pinned-panel",