fix(board): --dispatch neste= carried three other record fields

d_neste took the record from field 14 onward - the index from when the
record had 14 fields. ORDRE, FLY and VOY were later inserted before
`neste` and the index never moved, so every dispatch block read
`neste=<claimed>|<claimedage>|<voy>|<prose>` (measured on the shipped
0.34.0: `neste=1|0d|0|NESTE: ...`). Now field 17 onward.

Found while adding a field before `neste`, which would have made the
prefix one field longer. board-selftest pins the exact start of the
fixture's NESTE prose, so the next inserted field turns it red.

board-selftest 427 -> 428; README and CLAUDE.md counts moved with it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

README.md

@@ -14,7 +14,7 @@ Session A in repo X leaves a message for repo Y; the next session in repo Y gets
 ![Hooks](https://img.shields.io/badge/hooks-1-green)
 ![Skills](https://img.shields.io/badge/skills-4-orange)
 ![CLI scripts](https://img.shields.io/badge/CLI_scripts-8-blue)
-![Selftest checks](https://img.shields.io/badge/selftest_checks-927-blue)
+![Selftest checks](https://img.shields.io/badge/selftest_checks-928-blue)
 
 ---
 
@@ -199,7 +199,7 @@ Note that raising the inbox's priority (Rule 7) deliberately does **not** widen
 ## Development
 
     bash scripts/coord-selftest.sh              # 257 checks against a throwaway mailbox
-    bash scripts/board-selftest.sh              # 427 checks against a throwaway repo tree
+    bash scripts/board-selftest.sh              # 428 checks against a throwaway repo tree
     bash scripts/route-selftest.sh              # 73 checks, incl. the route->board round trip
     bash scripts/orders-selftest.sh             # 116 checks, incl. the 20-way barriered claim race
     bash scripts/state-line-guard-selftest.sh   # 54 checks, incl. the Edit replace_all projection and the ratchet