volt
36ce415842
Seventeen unittest.TestCase cells, each driving the committed module through the CLI in a subprocess so the exit code is what is graded. MOD resolves from this file's own directory, not a host path. Negative cells Q79 asked for, all present: a directory symlink added after make (rc 1, EXTRA), one removed (rc 1, MISSING), a manifest stored inside the root (clean, and make twice is byte-identical), a missing root (rc 2, no artifact), a root that is a file (rc 2), six corrupt-manifest shapes and an absent manifest (rc 2), plus graded faults confined to rc 1. Bite measured, not asserted: the same suite against edac5cf's manifest.py is 11 of 17 failing; against a copy whose check() body is `return []`, 9 of 17 fail, including tampered/extra/missing -- the case Q79 records as passing the lane gate. `bash wizard-work/beam/CHECK` -> Ran 191 tests, OK, rc 0. CHECK: python3 wizard-work/beam/test_manifest.py
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).