feat: add production assurance dashboard flow

docs/packaging/CASAN_PACKAGING_PLAN.md

@@ -5,17 +5,21 @@ holds (or scaffolds) all major CASAN components, and **releases are split by lev
 downstream project adopts only the level it needs. Single source of truth for bundle
 contents + maturity: [`packaging/levels.json`](../../packaging/levels.json).
 
-## The four levels
+## The four product editions
 
-| Lvl | Package names | Status | What it is |
+| Edition | Package names | Status | What it is |
 |---|---|:--:|---|
 | **1 — Core Harness** | `casan-core`, `casan-harness` | ✅ implemented | Minimal H1–H7 production runtime: security + action gates, evidence pack, audit, cost/telemetry, policy/config defaults, adapters, `bin/casan` CLI |
 | **2 — DevKit / Adoption Kit** | `casan-devkit`, `casan-project-kit` | ✅ implemented | Level 1 + project templates, domain-pack scaffold, Gitea workflow template, harness Dockerfile, install script, adoption/CI/domain-pack guides |
 | **3 — Platform Components** | `casan-platform`, `casan-control-panel` | 🟡 preview | Control Panel, Dashboard, Run History, governed chat MVP and **Evidence Pack Viewer**. Attack Battery Viewer, Gitea evidence publishing, and managed rollout are still pending. |
 | **4 — Enterprise / Governed Console** | `casan-enterprise`, `casan-governed-console` | 📋 future | Promotion layer requiring managed deployment, KMS/Object Lock operations, HA/DR/SLA, external review and compliance/support evidence. |
 
-Levels are cumulative: DevKit extends Core, Platform extends DevKit, Enterprise extends
-Platform.
+Editions are cumulative: DevKit extends Core, Platform extends DevKit, Enterprise extends
+Platform. Historical numeric packaging levels remain compatibility aliases only.
+
+Do not confuse editions with **CASAN Maturity L1–L5**. Maturity is an
+evidence-based operational assessment. Installing an edition never grants a
+maturity claim.
 
 ## Packaging principle
 The source hub may contain all levels, **but releases must be split**. Do NOT force a
@@ -61,7 +65,8 @@ minimal.
 ## Who adopts what
 - **Governance-harness-only / BJT initial / CI gate** → `casan-core`.
 - **New project adopting CASAN** → `casan-devkit` (install.sh scaffolds domain + CI).
-- **Want dashboards/visibility** → `casan-platform` (preview; dashboard today).
+- **Want dashboards/visibility** → `casan-platform` (preview; live H1–H7,
+  H6 coverage and on-demand run/H6 exports today).
 - **Enterprise governed console** → future; building blocks (RBAC/tenant/KMS/WORM/approval)
   already live in core.