docs(AUDIT-WP-0008): coordinate V1 recovery exercise

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a025c2-407a-7a32-b40a-f37a52f03f62

workplans/AUDIT-WP-0008-tenancy-posture-alignment.md

@@ -8,7 +8,7 @@ status: active
 owner: claude
 topic_slug: railiance
 created: "2026-08-17"
-updated: "2026-08-21"
+updated: "2026-08-22"
 depends_on:
   - AUDIT-WP-0007
 state_hub_workstream_id: "84c01552-4c65-45fd-bf6c-7daab0ecc9b6"
@@ -444,6 +444,18 @@ five exercise scenarios with integrity as a pass condition, and the measurement
 rules. The exercise itself needs a live window on railiance01 and coordination
 with `user-engine`, since two scenarios are visible to the sender.
 
+Coordination is active as of 2026-08-22. `user-engine` was asked for the
+synthetic sender lane and sender-visible measurement constraints
+(`76cef7cb-bac2-43af-ae8d-e2716fedfe79`); `rapp-postgres` was asked for the
+single-primary restart window, rollback, and co-resident notification needs
+(`04a2aff2-5f82-4ff1-a0ab-d31d3d6f07b5`); and `railiance-platform` was asked
+for the value-safe OpenBao/ESO recovery path and railiance01 operator window
+(`a93fa88f-a9c5-4539-93ae-0c8f8490f53d`). Warden routes the dynamic database
+credential lane to `rapp-postgres` and the OpenBao broker to
+`railiance-platform`. These requests are readiness coordination only: no
+restart, lease revocation, secret read, or reboot is authorized until the
+owners return an approved window, rollback plan, and abort conditions.
+
 One thing the enumeration settled: **V2 is not reachable from P1 as built.**
 `platform-pg` runs `instances: 1`, and Decision 4.6.1 makes V the minimum across
 synchronous providers — so no amount of replication on our Deployment raises it.