PLAN column in the board table, and plan= in --row. A filesystem
reading of the repo root: - = no file named exactly PLAN.md; Nd =
whole days the plan's mtime lies behind the last commit (0d when as new or
newer); ? = a plan with no commit to compare against. A symlinked PLAN.md is aged by its target. The content is never
read, and the column does not judge whether a criterion can be falsified -
the legend says so. The name is matched byte for byte, because APFS's
case-insensitivity makes [ -f PLAN.md ] true for plan.md. Display only:
not a sort key, not in --plan, not summed. board-selftest section 34
(written red before the column existed) pins all of it.
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 the field after the last column onward (field 18, since the PLAN
column below moved it again), and a selftest check pins the exact start of
the prose so the next inserted field turns it red.
--row and --dispatch for a repo with no STATE.md carried shifted
values. That record is written by its own printf, which lacked the VOY
field, so --row read voy=(ingen STATE.md) and an empty neste=. The
record is now complete; a fixture with no STATE.md pins it.
--inbox-plan cut NESTE at its first |. It read neste as one field
instead of "that field onward"; the whole prose now comes through, as it
already did in --row and --dispatch.
README said "macOS or Linux".board.sh uses BSD stat throughout and
renders no rows under GNU stat; the requirement now says macOS.
ktg released this