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>
This commit is contained in:
parent
20fcd67f4a
commit
0008dbbc3a
5 changed files with 25 additions and 5 deletions
|
|
@ -7,6 +7,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|||
|
||||
## [Unreleased]
|
||||
|
||||
### Fixed
|
||||
|
||||
- **`board.sh --dispatch` put three other record fields in front of `neste=`.**
|
||||
The index that takes "the last field onward" was written when the record had
|
||||
14 fields and was never moved as ORDRE, FLY and VOY were inserted before
|
||||
`neste`, so a dispatch block read `neste=0|-|0|<the NESTE prose>`. It now
|
||||
takes field 17 onward, and a selftest check pins the exact start of the
|
||||
prose so the next inserted field turns it red.
|
||||
|
||||
## [0.34.0] - 2026-09-12
|
||||
|
||||
### Changed
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue