feat: ship production local assurance viewer in core

docs/packaging/ADOPTION_GUIDE.md

@@ -20,6 +20,17 @@ The project defaults to Level 1/Core with runtime mode `managed`. Core remains
 under `$CASAN_HOME`; the repository receives `.casan` config/lock/bootstrap and
 the selected client hooks. The CLI output states the resolved runtime path.
 
+After any prompt, visual assurance is available from Core itself:
+
+```bash
+casan report latest
+casan view
+```
+
+The viewer is single-project, offline-capable and read-only. It starts lazily on
+`127.0.0.1`, so projects do not need Platform, Node/npm or an always-running
+service merely to inspect H1–H7 and H6.
+
 Use this for developer workstations and managed CI runners. CI must install the
 same release recorded by `.casan/version.lock` before running gates.
 
@@ -88,6 +99,8 @@ bin/casan pipeline --manifest apps/<project>/domain/project.manifest.json
 - **Project lock/config** → `.casan/config.json` and `.casan/version.lock`.
 - **Your domain data** → `apps/<project>/domain/` (via `CASAN_DOMAIN_ROOT`).
 - **Runtime state** → `.specify/` (logs, audit, governance — created on first run).
+- **Local viewer state** → `.specify/state/local-viewer.json` (`0600` on POSIX,
+  project ACL on Windows; ephemeral loopback port/session token; removed on stop).
 The bootstrap resolves the mode/path from the project lock and verifies the live
 Core hash before dispatch.