@menuband.app was never blocked from publishing. It was publishing fine and being told it had failed. `media_publish` can post the reel and still answer 400. That is what happened 33 times: each hourly run reported "Cannot Create Media / Create media fail, please try to re-create media", each one put another copy of 95-saucer on the grid, and none of them reached the ledger. The account ended up carrying 33 more posts than its own record knew about -- the 79-vs-46 gap that turned up during the grid reset and got written off as a stale ledger. Read as a wall of identical failures, it looked like an account-level ban. It was a publishing loop with the success signal inverted. So a refusal is now checked against the account before it is believed: sample media_count either side of the call, and if it moved, the reel went up. Report success, recover the id from /media?limit=1, and let the receipt and ledger happen normally. If the count moved but the id cannot be read back, say so loudly and refuse to pretend either way -- an unledgered live post is exactly what makes the lane repost it. Proven on the account itself: 94-gramophone published first try through this same path minutes after 95-saucer's "failure" had silently published too, leaving two posts on a grid whose ledger recorded one. Claude-Session: https://claude.ai/code/session_01X62vT9M1iQXjNTF1jMcpN5