diff --git a/docs/plans/release-0.3.6.md b/docs/plans/release-0.3.6.md
index bf3a1896..5f8192ba 100644
--- a/docs/plans/release-0.3.6.md
+++ b/docs/plans/release-0.3.6.md
@@ -553,3 +553,15 @@ three 0.3.6 machines within four minutes; Sam's Mac had not fetched it by 09:50Z
 | PC 1 ae432dc7 | `2026-10-05T10:35:10 apply : engine 24000 installer '...\updates\Igneum-Miner-Setup-0.3.6.exe' version 0.3.6 (the engine keeps mining until the installer runs)`, `installer sha256 verified` (BST; 09:35:10Z, 64 s after the manifest went live) | the installer ran, the 0.3.6 engine's first line at 09:35:17Z: the whole Windows path, check to restart, took 71 s and the helper launched with CREATE_NO_WINDOW alone did run (the 0.3.0 to 0.3.4 stall is gone) |
 | PC 2 1ccfe586 | `2026-10-05T10:38:34 apply : engine 14028 installer '...Igneum-Miner-Setup-0.3.6.exe' version 0.3.6`, `installer sha256 verified` (09:38:34Z; its log also holds the 0.3.4 attempt of 4 October: `sha256 mismatch`, the stall of that day) | engine restart 09:38:40Z |
 | Mac d937c69d | `2026-10-05T09:37:30Z apply: engine 63267 host 63263 ... version 0.3.6`, `staged bundle digest verified`, `swapped; opening /Applications/Igneum Miner.app`, `0.3.6 is running` | engine restart 09:37:35Z |
+
+Correction from the PCs (coordinator, 09:5x BST): with the matching GCC 13 DLLs swapped in, the PC-built igneumd.exe
+(1dcac192...) prints `--version` and satisfies all 182 libstdc++ imports, yet exits within 2 s of "Logs to console
+only" on PC 1 on the real database and on a scratch appdir (job probe-node-pc1-036), no stderr, empty exit code: a
+loader or abort, not a Rust panic. So the PC-built Windows node is unusable at runtime, not only mislinked, and does
+not ship. 0.3.7's igneumd.exe and igneum-miner.exe are the Mac cross-build (2b6d23ef, this Mac's mingw GCC 16.2.0)
+with that toolchain's DLLs, packaged exactly as 0.3.5 was. Both PCs are being rolled back to 0.3.5 with the silent
+installer (job rollback-035-pcs) and will read the OLD folder, so 0.3.7 goes to both folders.
+
+Open item for 0.3.8: why the PC-built node dies at start. Reproduce under WSL with wine or on PC 2 with a scratch run;
+compare Ubuntu's mingw (GCC 13, posix threads) with the Mac's (GCC 16); check `-static` against rocksdb's thread
+model. Until then the PC build job builds Linux binaries and tests; the Windows node comes from the Mac cross-build.