feat: add display kiosk host

docs/development/testing.md

@@ -275,6 +275,24 @@ enablement. During realtime development, run the focused live Node suite repeate
 `pnpm verify` and `pnpm test:migrations:integration`; consecutive runs are specifically intended to
 catch retained timers, listeners, subscribers, or loopback servers.
 
+Phase 7A pass 6 adds display evidence across the same boundaries
+([ADR 0033](../architecture/decisions/0033-display-kiosk-host-contract.md)). Contract tests prove the
+manifest v6 hard cutover, optional role combinations, module-owned non-public display permission,
+and collision rejection. Discovery tests prove inert compiled-artifact validation, containment,
+symlink collision detection, deterministic diagnostics, and that modules without a display remain
+valid. Builder tests prove the exact `src/ui/index.tsx` / `src/display/index.tsx` sources,
+deterministic role order, preflight/compile atomicity, no runtime-entrypoint overwrite, and identical
+browser/CSS boundaries.
+
+Core/API tests prove independently frozen primary and display publication records, exact anonymous
+artifact routing, permission-gated stable page and descriptor routes, eligible/running lifecycle
+filtering, sanitized failures, and startup-time frozen host assets. Surface tests prove principal-
+first descriptor bootstrap, the role-neutral host context, full-viewport mounting without Dashboard
+chrome or static module imports, late-import cleanup, manual retry, realtime reuse, and unmount.
+The canonical template builds and mounts both artifacts through `parseModuleUiExport`; contract
+fixtures also retain no-display and backend-only cases. These are code-only tests: display hosting
+adds no PostgreSQL, object-store, or Docker requirement beyond the existing suites.
+
 ### Which kind of timing proof lives where
 
 Pass 4 introduced several deadlines, and their tests deliberately differ in kind: