docs(deploy): #793 vd03 post-deploy deploy Applied (e4b4824a)

Claude-Session: https://claude.ai/code/session_01GT67AD99zQQqpLCVm3p7xk

docs/deploy/vd03-upgrade-b8b4c18f-to-master.md

@@ -352,6 +352,8 @@ Run over WinRM (owner-authorised for this upgrade) with staged scripts; the buil
   (`BadServiceUnsupported`, backing off); this is visible now because #874 routes SDK warnings to Serilog. The
   mesh-PSK refresh warns that `ot-mesh-psk-dev` is absent; the box runs the default DPS mesh transport, so the
   PSK is not used.
-- **Not done.** The post-deploy "Deploy once" check. `/deployments` shows "Configuration drift", but `ConfigEdit`
-  has no rows after the last seal (2026-08-05), so the drift is master's composer re-serialising the same
-  configuration; the deploy itself was left to the owner.
+- **Post-deploy deploy (owner-authorised, 11:02 UTC).** `/deployments` "Deploy current configuration" →
+  deployment `e4b4824a` (rev `475db34b…`) Sealed; chip back to "In sync"; `/fleet` 1 node **Applied** (not
+  degraded), no failure reason; no 3952. The drift had been master's composer re-serialising the 2026-08-05
+  configuration (0 `ConfigEdit` rows since that seal). Afterwards: ServiceLevel 255, `parts-count` and
+  `Program/Name` Good, `/health/ready` 200.