feat(runtime): enforce governed mutation boundaries

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06ba0-10aa-7ea0-b20a-4f3fac39efe9

deploy/README.md

@@ -3,6 +3,21 @@
 Single shared harness instance on **railiance01**. Secrets stay on the host
 (Lanes 2–3); the container image is the portable runtime package.
 
+## Supported runtime topology
+
+The authoritative production runtime is the railiance01 user service
+`rein-aharness-claim-loop.service`. It owns the configured repository
+checkouts, private runtime state, worker credential, lease heartbeats, and
+signal-driven shutdown behavior.
+
+The Kubernetes Deployment is explicitly labeled `packaging-smoke` and runs
+`sleep infinity`. It proves that the image can be scheduled with its hardened
+container settings; it is not ready to claim work and is not a failover worker.
+Do not give it an Activity Core worker credential or scale it as execution
+capacity. Promoting Kubernetes requires a separate reviewed cutover with real
+workspace, credential, repository-lock, Glas/sandbox, shutdown, and recovery
+semantics.
+
 > **Renamed from agent-harness (HARNESS-WP-0002-T02) — cutover done
 > 2026-07-26.** Railiance now runs `rein-aharness` end to end: image tag,
 > k8s namespace, CLI command, Python package, host secrets dir, and
@@ -48,6 +63,9 @@ Single shared harness instance on **railiance01**. Secrets stay on the host
 - Lane 3 AppRole under `~/.local/rein-aharness/approle-binky-mail`
 - `source ~/.local/rein-aharness/env`
 - Hub: `http://127.0.0.1:18000` (ops-bridge) or in-cluster `state-hub.state-hub.svc`
+- While profile-absent tenant definitions remain, set a reviewed ISO expiry in
+  `AGENT_HARNESS_LEGACY_APPROACHES_UNTIL`. The checked-in example expires
+  2026-12-31; missing or expired values refuse compatibility dispatch.
 
 ## Build & load image (workstation → railiance01)