release 0.3.17 plan: PC 1 read-back, the workers-after-relaunch fault, the restart job

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs/plans/release-0.3.17.md

@@ -68,4 +68,6 @@ Found on the way: master's build tools ended silently on a tree without rust-too
 - **Canary full form PASS, 05:04Z** (c17-1, wiped datadir, d712b498 / 5899f603): fresh join through the headers proof in one session (03:49:51Z to 04:25:25Z, zero guard lines), synced 04:54:02Z, ten minutes mining with the live miner 3976c1b2 at 51 to 55 MH/s: 52 blocks via submit block, accepted 51, rejected 0, mismatched 0, got-reject 0, wrong-version 0, SendPingsFlow 0, digest eada4bda, pow link 6 (Mac grep) and 5 (box grep); the hub holds 19 blocks by c17-1's key 1f5bce70 in its last 700 with 0 rejects naming the pod. The relay and poison cases started 05:04:25Z as the confirmation.
 - Fleet rollout under the lock rule (folded-table gate): p1-3080 04:56:13Z, sha d712b498, commit 5899f603, digest eada4bda, pow 5, synced 118,862 with 4 peers, miner back, lock after at checkpoint 8070 (81.3 percent), 59 s; p2-4070-1 05:03:10Z, same read-back, 118,980 blocks, lock at 8073 (81.1), 93 s; p1-4070 next; the 14 done by about 05:30Z with pool-1 and hub-1 last.
 
+- **PC 1 (ae432dc7), read back 05:00Z by job:** app 0.3.17, node pid 3840 started 04:51:43Z, synced at DAA 251,095 with 4 peers, consensus_digest eada4bda, the installed igneumd.exe carries 5899f603 (3 marks) and the igneum-pow link (9 paths). Its sha 949a30a1 (52,256,768 bytes) differs from the cross exe b6b3f417 (51,894,272) by the CI payload step (windows.yml line 243): on the day's check list. **Fault: the workers did not come back after the relaunch.** The 05:15Z dump: mining state "waiting", paused false, every enabled card (RTX 5090, RTX 4070, RX 9070 XT) "faulted: no status line from the miner for 90 s (restarted once already)", pid 0, 0.0 MH/s since 04:51Z (142.5 MH/s on 0.3.16 at 04:51Z); the node was still syncing when the workers were first started (program: "next program not known yet", boundary 255,600); proving unaffected (segments proven and paid through). Main's word: one `restart --what miners` job (05:1xZ), read back at the 0.3.16 rates; if that does not bring them back, PC 1 waits for the project lead. A 0.3.18 app row for the UI lane: workers must start after an OTA relaunch (main sends the known-failed case).
+
 (per-box table as the lines land)