diff --git a/docs/deployment/deployment-records/2026-08-20-wonder-app-vd03.md b/docs/deployment/deployment-records/2026-08-20-wonder-app-vd03.md
index efd45a0b..bf8d30f1 100644
--- a/docs/deployment/deployment-records/2026-08-20-wonder-app-vd03.md
+++ b/docs/deployment/deployment-records/2026-08-20-wonder-app-vd03.md
@@ -37,3 +37,24 @@ box has no psbridge, so everything ran from wonder-app-vq04 over **WinRM**
 ### Rollback
 Stop Site + Central, rename `app` → `app.failed`, `app.bak.20260820T163718` → `app` (same for
 `cli`), start Central then Site. Schema restore from the `.bak` only if needed (migrations are additive).
+
+## 2. Hotfix `da0bfe2b` — 17:03 (same day)
+
+Binary-only swap of `app\` to `main` @ **`da0bfe2b`** (MxGateway adapter: a graceful end of the
+event stream — dashboard "close session" / graceful gateway shutdown — is now a disconnect and
+triggers reconnect + re-subscribe; see the QA record §4 for the incident). No migrations, no
+config change; `cli\` untouched. Same WinRM-from-vq04 path: robocopy of vq04's unpacked release
+to `\\wonder-app-vd03\E$\psrem-stage\da0bfe2b` (1020 files), stop Site → Central, rename
+`app` → **`app.bak.20260820T170309`**, copy stage, copy back the three `appsettings*.json`,
+start Central → Site.
+
+Verification: `:8085` and `:8084` `/health/ready` 200 Healthy; `Host.dll` ProductVersion
+`1.0.0+da0bfe2b…`; site log 0 ERR/FTL after boot. The boot produced the same ~40 s of
+`Instance … subscribing to 270 tags` retries with `Worker command AdviseSupervisory timed out`
+that the 16:38 boot on `a24fa38e` did (3 instances × 270 tags advised against the local
+MxAccessGw), tailing off to the same ~1–2/min background `gRPC call deadline exceeded` by 17:07
+— not a regression. The new "event stream ended without a fault" warning has not fired (nothing
+closed the session).
+
+Rollback: stop Site + Central, rename `app` → `app.failed`, `app.bak.20260820T170309` → `app`,
+start Central then Site.