volt
d693f682ff
- suite:0735102converts the seven uncalled functions into one unittest.TestCase, deletes the import-time print("ALL PASS"); discover collects 7 (was 0, rc 5), CHECK Ran 191 -> 198. - mutant battery (scratch/q82/battery.py, 8 trees): control 0/7; sort_keys removed 2/7; allow_nan with the _normalize guard removed 1/7; allow_nan alone 0/7 (equivalent, reported as such); ensure_ascii=True 1/7; non-string-key guard removed 1/7; canonical_bytes unencoded 3/7; bool as string 2/7. 7 of 7 cells have a named killer. - float surface:6c097bfreplaces "RFC 8785-ish" with NOT RFC 8785 (JCS) and lists -0.0 / 1e-06 / 2**53+1 against RFC 8785 Table 1, each measured at that commit. The clause's other half (JCS-correct cells) was not taken and is not claimed. - gate: python3 tools/verify.py -> rc 0, 8 of 8 legs pass, 0 fault, 0 ungradable. CHECK: bash wizard-work/beam/CHECK && python3 tools/queue_index.py --check docs/queue-index.md
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).