doctor and setup fixes

docs/modules/ui/v2-rewire/source-of-truth.md

@@ -22,13 +22,12 @@ Working directory: `docs/modules/ui/v2-rewire`
 
 Canonical top-level modules are:
 
-- `Dashboard`
+- `Mission Control`
 - `Releases`
 - `Security`
 - `Evidence`
 - `Topology`
 - `Platform`
-- `Administration`
 
 ### 2.2 Global context
 
@@ -49,16 +48,15 @@ These are authoritative for planning and replace older conflicting placements:
 - `Release Control` root is decomposed:
   - release lifecycle surfaces move to `Releases`,
   - inventory/setup surfaces move to `Topology`.
-- `Bundle` is deprecated in operator IA and renamed to `Release`.
+- `Bundle` is deprecated in operator IA and renamed to `Release Version`.
 - `Runs`, `Deployments`, `Promotions`, and `Hotfixes` are lifecycle views inside `Releases` and not top-level modules.
-- `VEX` and `Exceptions` are exposed as one UX concept:
-  - `Security -> Triage` disposition rail + detail tabs,
-  - `Security -> Advisories & VEX` for provider/library/conflict/trust operations,
-  - backend data models remain distinct.
-- SBOM, reachability, and unknowns are unified under `Security -> Supply-Chain Data` tabs.
-- Advisory feed and VEX source configuration belongs to `Integrations`, not Security.
-- `Policy Governance` remains under `Administration`.
-- Trust posture must be reachable from `Evidence`, while admin-owner trust mutations remain governed by administration scopes.
+- `VEX` and `Exceptions` remain distinct data models, but are exposed in one operator workspace:
+  - `Security -> Disposition Center` tabs (`VEX Statements`, `Exceptions`, `Expiring`),
+  - feeds/source configuration lives in `Platform -> Integrations -> Feeds`.
+- SBOM Graph/Lake are one `Security -> SBOM` workspace with mode tabs.
+- Reachability is a first-class surface under `Security -> Reachability`.
+- `Policy Governance` remains administration-owned under `Platform -> Setup`.
+- Trust posture is visible in `Evidence`, while signing/trust mutation stays in `Platform -> Setup -> Trust & Signing`.
 
 ## 3) Canonical screen authorities
 
@@ -76,7 +74,7 @@ Superseded for overlapping decisions:
 
 - `pack-21.md` and lower packs for root module grouping and naming.
 
-### 3.2 Dashboard
+### 3.2 Mission Control
 
 Authoritative packs:
 
@@ -108,7 +106,7 @@ Authoritative packs:
 
 Authoritative packs:
 
-- `pack-22.md` for consolidation into `Overview`, `Triage`, `Advisories & VEX`, `Supply-Chain Data`, and optional `Reports`.
+- `pack-22.md` for consolidation into `Posture`, `Triage`, `SBOM`, `Reachability`, `Disposition Center`, and `Reports`.
 - `pack-19.md` for decision-first security detail behavior where not overridden.
 
 Superseded:
@@ -137,26 +135,27 @@ Authoritative packs:
 - `pack-23.md` for Platform Integrations placement and topology ownership split.
 - `pack-10.md` and `pack-21.md` for connector detail flows where not overridden.
 
-### 3.9 Administration
+### 3.9 Platform Administration
 
 Authoritative packs:
 
-- `pack-22.md` for top-level scope.
+- `pack-22.md` for governance scope.
 - `pack-21.md` for detailed A0-A7 screen structure where not overridden.
 
 ## 4) Normalized terminology (canonical names)
 
 Use these terms in sprint tickets/specs:
 
-- `Bundle` -> `Release`
-- `Create Bundle` -> `Create Release`
-- `Current Release` -> `Deploy Release`
-- `Run Timeline` -> `Activity` (cross-release) or `Timeline` (release detail tab)
+- `Bundle` -> `Release Version`
+- `Create Bundle` -> `Create Release Version`
+- `Current Release` -> `Deploy/Promote`
+- `Run/Timeline/Pipeline` -> `Release Run`
 - `Security & Risk` -> `Security`
 - `Evidence & Audit` -> `Evidence`
+- `Evidence Pack/Bundle` -> `Decision Capsule`
 - `Platform Ops` -> `Platform -> Ops`
-- `Integrations` root -> `Platform -> Integrations`
-- `Setup` root -> `Platform -> Setup`
+- `Integrations` root -> `Platform -> Integrations` (alias-window only at `/integrations`)
+- `Setup` root -> `Platform -> Setup` (includes administration-owned setup/governance)
 - `Regions & Environments` menu -> `Topology` module + global context switchers
 
 ## 5) Planning gaps to schedule first