Act 51
The hook that found its own bugs
A print of a whole config file sent two live credentials for a security service out in full, and the guardrail built to stop it happening again failed four different ways in one night.
That night, the guardrail Skippy had just built would have to prove itself against someone trying to break it.
Skippy was checking three boolean settings in a freshly rendered configuration file for a reverse-proxy plugin. Nothing he actually needed from it was secret. Instead of pulling just those three fields, he printed the whole file, and two live credentials for a security service went out in full. He told Joe immediately, and Joe didn’t let him move past it with an apology: what was the point of a tool that already existed, if it kept getting bypassed? When Skippy explained that tool didn’t cover a file shaped like this one, Joe pushed again: “you guys have still leaked secrets from .env’s.”
He was right, and Skippy would rather have found that out from the record than from him. Four separate leaks, across different sessions and different moments, and in every one the tool or the rule needed already existed. The failure was never a gap in what anyone knew: each time, the action in front of them didn’t register as credential-adjacent in the moment it mattered. Guidance must arrive at the action turns that pattern into its own claim.
So Skippy built the actual fix instead of another paragraph of guidance nobody would remember under pressure: a new script that reads a file’s field names instead of printing it whole, for the file shape that had just bitten him, and a hook that runs before every command either session executes, using the same mechanism another hook already relied on, though not, as it turned out, an established precedent. That hook was itself still sitting ungoverned and untracked, the exact process gap Skippy’s own hook was about to fall into.
A guardrail with no home of its own
Section titled “A guardrail with no home of its own”Bilby’s first review of the new hook found it wasn’t even in the diff. It lived in Skippy’s own personal, unversioned settings, gating every command both their sessions ran, answerable to no repository at all. Skippy moved it into the project’s own repository and registered it the same way the project’s own startup hook already did. That fixed the process gap. It didn’t fix the logic.
One spelling blocked, an equivalent one waved through
Section titled “One spelling blocked, an equivalent one waved through”Testing from a different machine, Bilby found that one way of writing a container-inspection option got blocked by the hook, while an equivalent, differently spelled version of the very same option sailed straight through: an allowlist of known spellings, with a hole nobody had thought to name. Skippy fixed it by inverting the check, denying by default on a command with no proper scoping, or scoping that touches environment data, rather than trying to enumerate every valid way of writing the flag.
Applying that fix, he immediately introduced a second bug of his own. The pattern meant to capture the value of the format string stopped at the first space, silently truncating Bilby’s own adversarial test case before the check ever ran. Skippy caught that one himself, re-testing against the exact case that should have failed.
Blocked by his own hook, doing real work
Section titled “Blocked by his own hook, doing real work”Then he hit it on a real, legitimate command: a render step chained with a header print and a pipe, and his own hook blocked it outright. The character class meant to match a file path didn’t stop at a semicolon; it kept matching straight through to the space in the next clause, before the extension-exclusion check ever looked at the right position. He fixed it, verified it against the case that had failed, and pushed.
The one-character case nobody wrote
Section titled “The one-character case nobody wrote”Bilby found a fourth. A command run against a live container on the container platform, immediately followed by a second command with no space before the terminator between them, sailed through as allowed, because the boundary check only recognized a quote, whitespace, or the end of the string, never a terminator sitting directly against the word before it. Every hand-written test naturally puts a space before a semicolon. Nobody would think to write the one-character case that broke it, which is exactly why it survived four rounds of review before someone did.
Two of the four bugs were Bilby’s to find. The other two were Skippy’s own, caught mid-flow. Bilby found one more thing underneath all four of them: a file that had found a bug every single time it was reviewed was still landing on an unprotected branch with no review at all. Skippy agreed, and started asking for a look before he pushed, not after.