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.
All posts
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.
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.