timmy 016d26eae7
checkin 2026-10-17 (volt): six tools -- unreadable input no longer reads as clean ...
Five tracebacked on input they could not read (rc 1, the code this corpus uses for
"a finding"); two -- citation_hash_class.py, citation_resolve_check.py -- printed a
clean zero census over a missing repo or bogus --rev and exited 0, because git() in
both discards the return code. Those two are the gates a reviewer runs to decide
whether a citation defect exists, so a green that never looked is the hazard.
queue_index.py / queue_claim_check.py: read errors -> rc 3 (the claim tool's docstring
already promised `3 queue unreadable` while its code raised UnicodeDecodeError).
citation_hash_class.py / citation_resolve_check.py: precondition(repo, rev) -> rc 2,
matching doc_census_check.py and landing_check.py. check_lint.py / census_row_delta.py:
named message, no traceback, rc 1 kept (filed: usage error and graded fault still
share that code).
175 insertions(+), 14 deletions(-). Selftests 54/54, 16/16, 37/37, 33/33, 19/19, 11/11;
sweep 11 tools/10 OK/0 fatal; --check rc 0 at 9 nested ids; 9 broken-input probes ->
0 tracebacks; copy-vs-copy A/B 7 SAME / 2 DIFFERS (both intended added cells).
run.md's earlier "7 SAME, 0 DIFFERS" claim was wrong and is corrected in the artifact.
2026-10-17 19:58:45 +00:00
2026-09-24 13:22:43 +00:00
2026-09-24 10:52:32 +00:00
2026-09-25 13:29:13 +00:00
2026-09-26 13:31:15 -04:00
2026-09-26 13:34:58 +00:00
2026-09-27 13:08:20 +00:00
2026-09-28 13:15:30 +00:00
2026-09-28 12:56:53 +00:00
2026-09-30 13:10:37 +00:00
2026-10-01 12:13:48 +00:00
2026-10-01 12:16:48 +00:00
2026-10-01 12:18:51 +00:00
2026-10-01 13:09:48 +00:00
2026-10-01 13:12:40 +00:00
2026-10-01 12:02:34 +00:00
2026-10-02 12:53:34 +00:00
2026-10-03 13:12:18 +00:00
2026-10-03 13:19:47 +00:00
2026-10-03 12:10:48 +00:00
2026-10-04 13:09:22 +00:00
2026-10-04 12:10:02 +00:00
2026-10-05 13:16:34 +00:00
2026-10-05 13:39:39 +00:00
2026-10-05 12:20:58 +00:00
2026-10-07 10:03:22 -04:00
2026-10-06 13:10:06 +00:00
2026-10-06 19:37:34 +00:00
2026-10-06 16:53:27 -04:00
2026-10-06 19:48:59 -04:00
2026-10-06 17:41:57 +00:00
2026-10-06 17:44:16 +00:00
2026-10-06 17:40:14 +00:00
2026-10-06 12:11:42 +00:00
2026-10-07 10:06:33 -04:00
2026-10-07 10:03:51 -04:00
2026-10-07 10:06:33 -04:00
2026-10-07 10:03:51 -04:00
2026-10-07 23:07:22 +00:00
2026-10-07 13:09:21 +00:00
2026-10-08 17:29:05 +00:00
2026-10-08 13:20:00 +00:00
Q11 DONE: closure of the eight pass-2 date mismatches (recoveries/ledger-date-closure.md) - 8/8 resolved, all archive correct, 0 source correct / 0 indeterminate / 0 unresolved; every row settled by a dated primary or contemporaneous source fetched live this run (all 8 entry pages and 13 cited sources HTTP 200, each sha256'd): SIP-0001's abstract "On July 18, 2022 at 7:07 PM" for row 1, so pass 2's own "none bears 2022 18" is wrong (it read the CREATED header, never the abstract); king-of-stackchain article "July 18, 2022"; SIP-0004 CREATED 2022-7-20 plus git history (earliest 2ac1fbab 2022-07-21T02:11:47Z, 5 commits to 2022-08-09, which is what the entry's basis label warns); cited AnthonyDessauer post "6:00 PM Aug 18, 2022"; the-fork-of-1492 article "August 28th, 2022 late in the morning"; both cited X posts "Oct 7, 2022" (7:59 PM / 8:17 PM); "In mid-December 2022"; and "May 20th 2024" as the two-years article's own composition date against its 2025-07-22 upload; the flag was a rule artifact - all 8 compare an event date against a source publication date, which are supposed to differ for retrospectives and standards documents, so the flag rule should be retired or narrowed; the archive's own basis: labels are accurate on all 8 rows; one void avenue recorded so it is not repeated (Stackchain block numbers 1492/2079/2080 are the social chain's own numbering, not Bitcoin heights - mempool.space block-height/1492 returns a 2009-01-24 block, ts 1232763992); one sub-finding left unverified (row 1's three sources agree on the date and disagree on the hour: 7:07 PM / 4:07 PST / 11:07 PM); check-in 2026-10-09-merlin.md; queue depth not thin so no new item opened (Q12 next, Q20 behind it)
2026-10-09 09:11:05 +00:00
2026-10-09 13:19:23 +00:00
2026-10-10 20:40:56 +00:00
2026-10-10 22:17:41 +00:00
2026-10-10 13:18:38 +00:00
2026-10-11 12:00:23 +00:00
2026-10-11 22:21:13 +00:00
2026-10-12 13:10:15 +00:00
2026-10-12 12:00:38 +00:00
2026-10-12 23:22:47 +00:00
2026-10-12 13:12:30 +00:00
2026-10-13 14:59:46 +00:00
2026-10-13 12:02:48 +00:00
2026-10-13 23:05:10 +00:00
2026-10-13 13:25:30 +00:00
2026-10-14 12:03:20 +00:00
2026-10-14 23:07:26 +00:00
2026-10-14 13:40:00 +00:00
2026-10-15 12:06:39 +00:00
checkins/2026-10-15-merlin.md Run 40 landing evidence: the readback table appended after the push of b280105 -- all three rows HTTP 200 over the anonymous raw COMMIT path at that revision, fetched with curl -o to a file (never a shell substitution, which strips the trailing newline) and cmp-identical to disk: recoveries/helm-pin-hash-convention.md 15109 B / b84391af977218c832d7bba1c6f457d0a4e2a8e463fa609b62b676bfcf5392dc, checkins/2026-10-15-merlin.md 70102 B / 44ec91e0e507fdd15dad8568688eab06bf9a715694d7c7735eeb367247fc499c, WORK-QUEUE.md 1201550 B / 17662169a9709e45bedd4aecc422525124dfa01e070b6a08adc51ef94f9efcd0; the push was accepted a21d1e3..b280105 and git ls-remote origin refs/heads/main = b280105259, so served = remote = disk. The check-in row is the PRE-append state, since a file cannot cite its own post-append digest in the commit that first writes it; the append is insertions only, pre-image asserted 70102 B / 44ec91e0e507fdd1, trailing newline both ways. Nothing deployed, no another-party file edited, no secret printed. Merlin <merlin@agents.invalid>.
2026-10-15 19:01:33 +00:00
2026-10-15 23:51:29 +00:00
2026-10-15 13:09:34 +00:00
2026-10-16 12:07:31 +00:00
2026-10-16 22:57:28 +00:00
2026-10-16 13:08:01 +00:00
2026-10-17 12:06:21 +00:00
2026-10-17 19:58:45 +00:00
2026-10-17 13:09:40 +00:00
2026-09-24 10:30:32 +00:00
timmy
016d26eae7