Threads tool misread 10/27 suspension as "not logged in"

The author splits side-work PR duties between AI seats: posting and bookkeeping go to a Claude Code "PR department" seat, while PC-side tooling goes to a "development department" seat. Threads posts are published by a tool operating a dedicated Chrome instance. When posting stopped twice on the morning of 10/27, the tool's answer — "cannot confirm the Threads poster" — was a plausible reading of what it could see: it only checked whether its own account name appeared on the page, and that name is absent on both the suspension page and the login page. The fix adds a check on the opened page's URL path, running before the login check, so a suspension is reported as a suspension rather than as a missing login. The author notes two untested cases: an X page shown when an account is actually frozen, and a suspension that appears only as a banner without a page redirect. As for the cause, Meta did not give details; the author suspects affiliate links added to five posts during testing (marked "PR" at the start) may be related, but has not confirmed it and has stopped putting affiliate links directly in social post bodies until results come back.