The audit was green, specific, and about the wrong artifact
An audit passed on 113 pages while the source directory held 145, because it inspected a stale build. A correct check on the wrong artifact reports confidently.
tooling
36 posts
Never attempted, and the summary said complete
A missing trailing newline dropped the last entry from a loop. Nothing failed, the summary matched what ran, and one item was never attempted.
A warning is not a refusal, and the driver could not tell
A driver keyed on the word ok halted a batch of 49 at item 19, because the check reported a warning rather than a failure. Gate on the blocking count.
Name the fault, and rule out the wrong fix
An error that describes the request sends you to change the request. A good message names the real condition and closes off the plausible wrong repair.
The two fields that only exist in the interface
Two SEO fields have no API path on the platform I syndicate to. That single gap is the reason the pipeline stops at a draft instead of going live.
The export engine that exported nothing
A stub is not an empty function. It returns plausible values, satisfies its interface and does no work, which is why emptiness checks never find it.
A screen nothing navigates to still compiles
A route with no caller compiles, registers and never runs. Reachability is a graph property, so no per-file check can see it and nothing fails.
Your meta description is cut mid-sentence
A description clipped to a character limit is severed mid-clause. Writing to fit whole is the fix, and the field you edit may not be the one that ships.
The only screenshots worth committing
Golden references are test inputs and belong in version control; run captures are regenerable evidence and do not. Conflating them loses the reference.
A hundred posts is the easy half
Producing a hundred technical posts is a scheduling problem. Keeping the hundredth as good as the first needs a standard the work is checked against.
The module that compiled and was never installed
A dependency module nobody included compiles cleanly and fails at runtime. Declaration and installation are separate acts and only one of them is checked.
Stop hand-registering what a processor can see
A registry, a binding and a cleanup hook maintained by hand are three chances to forget. A processor already has what it needs to write all three.