Print the list before you touch anything
A batch ceiling refuses work without telling you how much exists. Enumerating first turns an unknown amount of work into a finite list you can decide about.
All posts
The orchestrator that wrote the code itself
When the coordinator writes a layer instead of dispatching its generator, the conventions the generator carries are gone and the output still compiles.
Editing the generated thing is how the spec stops meaning anything
A change implemented directly in source skips the spec, so every report downstream is computed without it. The feature works and nothing can see it.
Every generated file should say what made it
A generated artifact carries no record of how it was made once the process ends. A provenance sidecar makes which-path-produced-this answerable by grep.
The post that went to the wrong account
A publication identifier is an optional field that silently defaults. The API reports success either way, so the only way to know is to verify the response.
A status column is wrong within a week
A hand-maintained status field said draft for a hundred posts while sixty-eight were live. State that is stored is a memory; state that is derived is a measurement.
Twenty-four of my tags file exactly one post
Across 219 posts I had 88 distinct tags and 24 appeared exactly once. A tag that gathers one item is a label, and labels do not help anybody find things.
The TextField overload you're using is probably the deprecated one
Compose has two TextField APIs. The String + onValueChange pair has real problems with cursor position and asynchronous updates; the TextFieldState overload solves them and is now the recommended one.
It returned an identifier and produced nothing
An exhausted quota returned a success with a session id and no artifact, and the message pointed at the prompt. The misdirection cost more than the outage.
One of the two links is always missing
A syndicated copy links home immediately; the original links out only after a rebuild. The asymmetry means one direction is reliably broken for a while.
Three hundred and three of three hundred and four
A mandatory generation step had produced its fallback on 303 of 304 artifacts, for weeks, because the flag that selected the real path crashed on any real file.
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.