fix: render registry workspaces for harness

README.md

@@ -141,12 +141,16 @@ Each public smoke has its own 30-minute process-group supervisor with TERM/KILL
 an independent 32-minute outer timeout and does not retry a failed command.
 
 Current release status (2026-08-05): clean-root render/setup and the production runtime-binding
-resolver contracts are green. The single corrected server-profile run proved image build,
-clean-root startup, and core/frontend health, then stopped at a fixture-authenticated frontend
-request; its trusted-hop headers are corrected deterministically but were not rerun. The single
-corrected rollback run reached runtime/Pi/registry/persistence checks and the stopped-candidate
-preflight, then stopped at active-session inventory before mutation. Full server behavior and
-bad-Pi compensation with unchanged state therefore remain release gates. Native Windows Docker
+resolver contracts are green. The server fixture supplies all four private trusted claims,
+including exact non-admin value `0`, and a focused test proves nginx normalization produces the
+accepted non-admin backend principal. Canonical schema-v2 registry descriptors now pass through
+one backend-owned, secret-safe runtime handoff for inventory and session execution; canonical
+identity and durable session/artifact/index roots are retained. The fresh update-only smoke passed
+bad-candidate mutation, automatic `rolled_back` compensation, exact prior-image restoration,
+unchanged registry/mount identity, all four sentinels, post-rollback doctor/workspace checks, and
+exact cleanup. The one authorized server-smoke invocation was denied access to the Docker socket
+by its execution sandbox before startup, so the complete authenticated workspace and fail-closed
+session assertions still require a fresh authorized release run. Native Windows Docker
 Desktop/WSL2 remains a separate manual/self-hosted gate.
 
 The deterministic native Windows contract is: