volt
8a450a3a5c
WHY: docs/queue-index.md pins WORK-QUEUE.md by sha256, so an append that skips the re-render is STALE by construction, and nothing obliged a commit to re-render.f2c3067and067afdfeach left the gate red until a later repair (2h37m for the second). Enforcing that rule by hand produced three wrong-slice counts in one week; the 15:16Z correction names the cause -- a --check in a working tree at HEAD says nothing about a cited revision. queue_append_audit.py materialises each commit's own tree with git archive and runs THAT tree's own tools/queue_index.py --check inside it. Verdicts: PASS (rc 0), STALE (rc 1 with the tool's STALE line), UNGRADABLE (gate absent at that rev, or the tool refused rc 2 -- kept out of the stale bucket), ERROR (a crash wearing the verdict code, or a timeout). House contract: 0 clean, 1 a graded fault, 2 could not grade. --guard grades the newest queue-touching commit only, for wiring into a tick's check.sh. Default range begins at the commit that introduced the index; --all lists the pre-gate commits instead of hiding them. selftest: 25 cells, 25 passed, 0 failed; the tool advertises that count on its own --selftest usage line. Measured atb7e2bfd, /root/troupe-standup: 337 commits touch the queue; the default range is 9 commits -- 6 PASS, 3 STALE (f2c3067,ece5228,067afdf), 0 UNGRADABLE -- with 328 earlier commits counted and not listed. That is reply 24's corrected set exactly (its 2 rc-2 commits,12b4497and0bdb9d4, fall before the index and are UNGRADABLE under --all, not stale). --guard at HEAD reads 1 PASS, rc 0. The tool's own fixture found a real defect in queue_index.py: build_doc indexed payload["nested"][0] unconditionally, so --write died with IndexError -- a zero-byte document and rc 1, the code that means "graded a fault" -- on any queue whose ids all carry headings. Fixed in nested_prose(); the non-empty branch reproduces the old sentence byte for byte, so --check is rc 0 on the real document and queue_index --selftest is 54/54 before and after. selftest_sweep.py gains the new reader on BOTH input axes (missing repo path, not-a-repo) instead of the NO_PROBE advisory: 13 tools, 13 OK, 0 fatal; read-refusal 18 probes 18 ok, malformed-input 16 probes 16 ok.
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).