STATE-CURRENT + docs: record P2 identity overlay, P3 control forwarding and P5 wave-1 shadow execution

1 files changed, 15 insertions, 5 deletions

diff --git a/docs/03-architecture/11-physical-backend-guest-wiring.md b/docs/03-architecture/11-physical-backend-guest-wiring.md
index 55700b5..8c38680 100644
--- a/docs/03-architecture/11-physical-backend-guest-wiring.md
+++ b/docs/03-architecture/11-physical-backend-guest-wiring.md
@@ -1,11 +1,13 @@
 # Physical Backend Guest Wiring: Driving the Guest-Facing Emulation from the Live GSP-RM Session
 
-> **Status: P0-P3 implemented (2026-10-02).** The backend API skeleton (P0),
-> the mdev-owned lifecycle (P1, fail-open; the async FWSEC boot on that path
-> is an open defect off the critical path), the static-config identity
-> overlay (P2, verified live in an A/B run) and the read-only control
+> **Status: P0-P5(w1) implemented (2026-10-02).** The backend API skeleton
+> (P0), the mdev-owned lifecycle (P1, fail-open; the async FWSEC boot on that
+> path is an open defect off the critical path), the static-config identity
+> overlay (P2, verified live in an A/B run), the read-only control
 > forwarding whitelist (P3, default off, verified live: ok=22/fallback=2,
-> smoke `ALL OK` 64/64) are in the tree. The physical
+> smoke `ALL OK` 64/64) and the P5 wave-1 guest-submission shadow execution
+> (default off, verified live: 514 real CE copies during a green guest smoke
+> `ALL OK` 64/64) are in the tree. The physical
 > backend itself is live: the module-owned
 > GSP-RM completes initialization on the real TU104, serves the full
 > static-config reply, and shuts down gracefully. The host resource-manager
@@ -473,6 +475,14 @@ go-ahead, recovery plan, pstore, never unattended
 * **Rollback:** parameter off (guest returns to echo path).
 
 ### P5 - Work forwarding + completion relay (interim, host buffers)
+* **Status (2026-10-02): wave 1 implemented and verified live (default off).**
+  With `gsp_phys_work_forward=1` the sema pump shadow-executes eligible CE
+  pushes on the physical engine through one ordered work item running the
+  module-owned ladder copy; the software release path stays authoritative and
+  no guest memory/VA is touched. Live: guest smoke GREEN `ALL OK` 64/64 with
+  514 real CE copies (194 requests coalesced/dropped while one was in flight,
+  0 refusals, 0 timeouts). Wave 2 (hardware-primary release relay) and P6
+  remain.
 * **Scope:** the debugfs ladder's real-submission half is **done** (cycle 25:
   channel allocates, page directory commits, `REAL COPY OK` on the physical
   CE in VA mode). The remaining work: bind each guest CE/GR channel to a real