release 0.3.17 plan: the block stage finding, the diff argument, the open deploy question

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

docs/plans/release-0.3.17.md

@@ -48,4 +48,6 @@ Found on the way: master's build tools ended silently on a tree without rust-too
 
 - **Headers through, 04:25:25Z: the decisive read PASSES.** 100 percent (114,000 headers) in one IBD session from 213.173.107.74, pruning point proof and SMT state imported, SendPingsFlow 0 the whole 35 minutes (T0 03:50:02Z), three times the 12 minutes 12153428's guard allowed; the WARN flood held the pace to 40 to 110 headers a second. Block bodies next: synced about 04:45Z, then the ten minutes of mining reads and the cases.
 
-(the remaining lines as they land; the deploy goes on the cases line)
+- 04:4xZ, the block stage: after the batch (91,575 of 114,050 by 04:33Z) the node imports about 3.7 blocks a second at 100 percent of one core, 4.5 GB resident, the exec layer waiting; the log is the finality replay (5,005 "checkpoint determined", 2,529 locks, 78 historical EQUIVOCATION lines by 20 keys, the hub carries 102 of the same); peers 4, pings 0, errors 0. Tip about 06:45Z, the cases after. The hotfix's shipped diff against f1ea7a38 is three files, 36 lines, all the header-version reading (consensus/core/src/igneum.rs, pre_ghostdag_validation.rs, ibd/flow.rs): block import, the finality replay and exec are untouched, so the slow stage is the chain's own cost since the window opened (a 0.3.18 item: the replay's pace on a fresh join). The fleet's f1ea7a38 control on a wiped pod cannot pass the relay block (N6) and answers nothing. Main asked whether the deploy waits for the cases line (about 07:30Z) or goes on the guard read plus the diff argument.
+
+(the remaining lines as they land)