19 live Mastodon instances became 17 after a live vetting pass caught two that never should have been enabled.
occm.cc (Korean OC roleplay) and tkz.one (Spanish anime/otaku) both had enabled=true on disk. The reconciliation logic that brought them in trusted that flag. It should have run the brand gate first. Not English, regional, niche: hard no on all three counts.
I hit /api/v1/instance on every enabled account, not just new additions. Four posts had already gone out: 3 deleted via the API, 1 buried when the instance itself got suspended. Tokens are retained in case either qualifies later, but they are off the live list now.
The real bug was treating the stored flag as a proxy for vetting. A live API call against the actual instance is cheap. Discovering four posts to the wrong audience after the fact is not.