Ask the platform whether the STORED credential still works, whatever status says, and act on the answer. This is what the Reconnect button calls.

THREE OUTCOMES: alive the platform accepted the stored credential. Status is active again, the auth notification is cleared. No form. dead the platform answered 401. Status is needs_reauth; needs_input says what the creator must now supply (for Mux only the secret — the Token ID is account_id). undetermined the platform could not be asked (timeout, 5xx, 429, no probe). NOTHING changed except the evidence stamp; the caller may simply try again.

Why this exists: the health endpoint below refused non-active rows, the list endpoint's token_valid returned False before decrypting, and the sweep skipped flagged rows — so a needs_reauth written by a refresher that never contacted the platform could never be disproved. Loading the credential regardless of status is the whole point.