diff --git a/docs/plans/release-0.3.6.md b/docs/plans/release-0.3.6.md
index 67c4510db..8fbc93443 100644
--- a/docs/plans/release-0.3.6.md
+++ b/docs/plans/release-0.3.6.md
@@ -585,3 +585,40 @@ RUSTFLAGS changed):
 Both embed 2b6d23ef. The gate with this Mac's toolchain DLLs (GCC 16.2.0): igneumd.exe, all 197 imported symbols
 exported (5,994 exports), pass. The PC-built pair (d08404c2..., 8bdb4c6e...) is kept in the session scratchpad
 (`pc-built-036/`) for the 0.3.8 item and is no longer under `target-integration`.
+
+### 9a. The 0.3.7 ship
+
+the project lead pushed `release-0.3.6` at c528ce8 (10:10Z). `gh workflow run windows.yml --ref release-0.3.6` → run 37294921529,
+10:11:01Z, green 10:16Z (the G13 step verified the 0.3.7 inputs of 57d2ad32...). Dry run clean (0 behind origin/master
+this time). The real run, `node tools/ship-app.mjs 0.3.7 --node vendor/igneum-node-036 --branch release-0.3.6 --dl-both
+--activation-height 84100 --deadline-note "proving v0" --notes "Hotfix for Windows nodes: ..." --from ci`:
+
+| Step | Result |
+|---|---|
+| preflight | ok, tree c528ce8 clean |
+| ci | green after 5 min of polling |
+| fetch | Igneum-Miner-Setup-0.3.7.exe 18.9 MB, igneum-windows-app.zip 26.3 MB |
+| dmg | already (8ee96b3b..., built 09:46 to 09:49Z) |
+| copy, mirror | DMG into the OLD folder; 7 files into the NEXT folder |
+| manifest | override carried over from the OLD folder's republished 0.3.5 manifest (the same object the NEXT folder's 0.3.6 held; both read before the step); both signed, verified, same fields |
+| deploy | 10:16Z |
+| verify | 3 files and the manifest match in both folders |
+| console | item #350 "Igneum Miner 0.3.7 shipped (mac+windows)"; exit 0 |
+
+The live manifests, read 10:17:22Z, compared field by field with the 0.3.5 record (8h):
+
+| Field | OLD folder | NEXT folder |
+|---|---|---|
+| version, channel, min_supported_version, published_at | 0.3.7, devnet, 0.3.0, 2026-10-05T10:16:29Z | the same, 2026-10-05T10:16:29Z |
+| consensus | identical to 0.3.5's: override {33000, 84100}, activation_height 84100, deadline_note "proving v0" | identical |
+| fees_v1_activation_daa, tuning | absent, absent | absent, absent |
+| mac | dmg 8ee96b3b054f45721ea08d0e00dfae79fc127fdfa503e05565d117b2c71cd9e2, 40,156,739, URL in its folder | same bytes, URL in the NEXT folder |
+| windows | inno-setup 2bacba64628b02e5f03e54007e794a30438a966238c75293a2905e1b5c5e2557, 19,784,297, URL in its folder | same bytes, URL in the NEXT folder |
+
+`update-now-20261005-101725` to all, published 10:17:25Z (mirrored to both folders by the publisher), the apps woken
+(stamp 2026-10-05T10:17:25Z.726198ee): the 0.3.5 PCs check hourly otherwise.
+
+Baseline 10:11:52Z, before the publish: Mac d937c69d app 0.3.6 node 2b6d23ef DAA 92597 22.4 MH/s; PC 1 ae432dc7 app
+0.3.5 node 2.1.0 (the rolled-back 0.3.5 node) DAA 92578 112.1 MH/s; PC 2 1ccfe586 app 0.3.5 DAA 92578 122.3 MH/s;
+Sam's Mac 3a9bf309 silent 28 min (app 0.3.5, 0.0 MH/s at its last report); PC 37ba0461 app 0.3.5 node 20139145 DAA
+92583 2.3 MH/s. A machine counts as updated only when its node reports a DAA score and the miner a hash rate on 0.3.7.