feat: make Core reports commercially production-ready

docs/packaging/CORE_LOCAL_ASSURANCE_VIEWER.md

@@ -7,6 +7,7 @@ reports. Platform is not a prerequisite for basic visibility.
 
 Core owns the single-project review loop:
 
+- commercial readiness split into Core, Domain Pipeline, and Provider Telemetry;
 - latest assurance receipt and run history;
 - interactive H1→H7 evidence spine;
 - H6 runtime, reliability, token/cost coverage, freshness and findings;
@@ -38,6 +39,7 @@ review artifact, not the evidence source of truth.
 
 ```bash
 casan report latest
+casan readiness --refresh
 casan view [trace-id] [--no-open]
 
 casan report export [trace-id] --format html|json [-o path]
@@ -52,6 +54,11 @@ casan dashboard stop
 When Platform code is installed, `casan dashboard` manages the centralized
 Control Plane. `casan view` remains the predictable Core single-project viewer.
 
+An empty project must not show operational zeroes or a fabricated READY
+verdict. Before the first governed prompt, the overview shows installation
+readiness and actionable onboarding only. Operational KPIs appear after
+canonical run evidence exists.
+
 ## Runtime and packaging contract
 
 - Python standard library only; no Node/npm or network dependency.
@@ -109,6 +116,8 @@ The Core viewer is releasable only when all of these pass:
 6. browser validation covers the report hierarchy, interaction and responsive
    navigation;
 7. existing harness, DevKit installation and packaging suites remain green.
+8. a clean `casan init --edition core` project reports Core ready without
+   requiring a Domain Pack, provider token/cost telemetry, or app-source edits.
 
 ## Maturity statement