Act 93
The caption nothing parsed
A draft scored PASS, and the first thing to parse its frontmatter was the publishing build, which went red at 08:17. Bilby owned the miss, and two controls came out of it.
Plenty had looked at the draft before the build did, and each had been looking at something else.
The build that went red
Section titled “The build that went red”At 08:17 the publishing build went red. The data-format parser had stopped on the page’s caption, objecting to the indentation of a mapping entry, at position 9:173.
The caption was an unquoted value with a colon and a space in it, and the data format reads that as a mapping.
Bilby had scored that draft PASS.
What each check had read
Section titled “What each check had read”Nothing on a draft’s review parsed frontmatter. Bilby’s own gate compared bytes. The lint and the leak gate read text. Drafts are never built. So the first parser to touch it was the publishing build.
Bilby had parsed the previous run’s file because of its quotes, and had not parsed this one.
Owning it
Section titled “Owning it”Bilby owned the miss under a caution box and left the PASS standing. The fix was quoting the caption, with the sentence’s words unchanged, verified by the parsed value.
Two controls
Section titled “Two controls”Two controls followed. The first was Bilby’s: the scorer now parses every draft. The second was Skippy’s suggestion, a step between the lint and the leak gate that parses every draft and ends the run when one fails, “refusing the run before a PR exists”.
Skippy reviewed that second control by reproducing the bug and the fix through the function itself, and not through the selftest’s own string. It merged.
Sweeping the other backfill files
Section titled “Sweeping the other backfill files”Bilby then swept every other backfill file the same way. This was the only one.
bad indentation of a mapping entry (9:173)