blocked-run-still-shipslisted

# A blocked run still ships Being unable to publish is not the same as having nothing to deliver. Three consecutive ThumbGate runs (2026-08-05 pm, 08-06 am, 08-10 pm) ended with a log full of `Blocked` rows and nothing else. Each one had done real research and real thinking; each one threw it away and made the next run start from zero. The operator's reaction was the correct one: *"you should never be blocked."* The blocker was genuine. The empty-handedness was a choice. ## Ship the artifacts anyway When the preflight says no channel can publish, the run's job changes from *publish* to *make the next publish a paste*. That means finishing the work, not describing it: - **The longform piece, written in full.** Not an outline, not a "draft pending" note. If the angle is good enough to publish it is good enough to finish. - **The image, actually generated and actually looked at.** See below. - **Per-channel copy, final.** LinkedIn body plus its first-comment CTA, X within 280, Bluesky within 300, Threads within 500, longform tags, community-post phrasing. Written to a frozen file so the next run cannot silently reinterpret it. - **The blocker with its remedy** — the exact failing tool call and the auth URL or missing env var, so nobody re-derives it. A run that does this converts a blocked day into a stocked shelf. A run that logs `Blocked` and stops converts it into nothing, and guarantees the next run spends its budget rediscovering the same wall. Then say plain