Plan 0.3.17: the kill-by-name row (my pkill of build-remote.sh killed another lane's run)

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

docs/plans/release-0.3.17.md

@@ -37,6 +37,10 @@ HiveOS images are Ubuntu 20.04 (glibc 2.31); the canary pods on 22.04 (2.35) ref
 
 `cargo check -p kaspa-testing-integration --tests` runs in the box suite of every cut and in the fork's CI (the crate had not compiled since the finality fields landed; no integration test ran on any cut until this one). The 0.3.17 box chain carries it as its last step (rebuild-on-fix.sh step_box / the node chain's "integration check"). 0.3.18 node notes: relay pipelining bb397f99 and the sync-request fuzz gate 6cf33d36 on ca3-v4-0318; aa0182aa and 812c3ac2 from ca3-v4-0316.
 
+## 2c. A kill matches a pid, never a name (main's row, 7 October 2026, 01:xx UK)
+
+My `pkill -f build-remote.sh` at 00:17 UK (to stop my own chained box builds before a rerun) killed the decimals lane's box run on the same Mac: the pattern matched every build-remote.sh, not mine. Rule: every kill in the ship tooling matches a pid file or the exact command line (the run's log path, the worktree path), never a tool's name; the ship scripts run through tools/ci/pre-push.sh's kill-by-name check before the next cut. Tonight's scratch runbooks hold no pkill by tool name any more (the chains are started with their log path in the command and stopped by that path).
+
 ## 3. Owed
 
 - exec-sync-0313's consensus verification behind a feature off for Windows (the proving lane), then its two commits.