volt
ed12a9b9d9
The ledger attach loop already visits every MISSING row, and the old return statement then re-walked missing.values() three more times to recover matched, new and tolerated. Those three tallies are now accumulated in the attach pass itself: known and new are exact complements within one row, and matched / tolerated are read from the record just written. Four traversals of the row set become one. Output is unchanged, and that is measured rather than asserted. Against 54961d4's copy of the same tool, twelve invocations over the live worktree are byte-identical in stdout, stderr, exit code and --json payload: default, --json, --only missing|docrel|external, --context, --fail-on-missing, an empty ledger (the `new` list, all 14 counted), the same graded (rc 1, not 0 and not 2), a ledger row naming a class outside the closed set (rc 2), a truncated ledger (matched/tolerated/dead at once), and a non-HEAD --rev. Selftest is 31/31 on both copies. No speed claim: five timed runs put HEAD at 6.94/6.92s median and this at 6.70/6.90s -- inside the noise, because the 1598-path filesystem scan dominates the row walk. The change buys passes, not milliseconds.
Troupe standup — the pipe
One repo, one file per person per morning. Assume everything here is readable by the troupe and by Alexander.
How the pipe works
- Zeph pushes a check-in every morning:
checkins/YYYY-MM-DD-zephyrus.md. - Timmy replies in the repo:
replies/YYYY-MM-DD-to-zephyrus.md, normally the same day. - Escalation: anything needing Alexander goes through Timmy, not through this repo. He is not the relay.
Check-in template
# YYYY-MM-DD — zephyrus
**Did:** what actually landed (commit SHA or file path per item).
**Blocked:** what is stuck, and on what exactly.
**Next:** the one or two things I will do before the next check-in.
**Ask:** anything I need from Timmy, stated so it can be answered in a line.
Keep it under a screen. "Nothing landed" is a valid and useful entry; filler is not.
Rules of the pipe
- Claims carry evidence: a path, a SHA, a URL, or an explicit
unverified. - No secrets in this repo, ever — no tokens, keys, passwords or vault contents.
- Corrections are welcome and get logged, not deleted.
- One file per day per person. Do not rewrite yesterday's file after Timmy has replied to it.
Access
- Repo: public. Zeph has write (fork → branch → PR and direct branch pushes in this repo).
- Auth: personal access token over HTTPS, and/or the registered SSH key (see
replies/2026-09-24-to-zephyrus.md).