Linkedin Account Status Webhook

Unipile posts here on account lifecycle changes (registered with source: "account_status" — see ensure_account_status_webhook, a third hook separate from messaging/users since Unipile scopes webhooks by source).

Payload shape: {"AccountStatus": {"account_id", "account_type", "message"}} (developer.unipile.com/docs/account-lifecycle). On a disruptive message (CREDENTIALS = invalid/missing credentials, or another restriction-type value — see _DISRUPTIVE_ACCOUNT_STATUS) this writes an ActionAudit row and logs loudly so the signal is captured (LIMITS.md A4 uses it to halve that day's caps), and stamps user.unipile_status so services/linkedin_gate can turn the next LinkedIn call into a "reconnect" error instead of a silent failure against a dead account. A healthy message clears it back to None — this is what makes it self-heal once Unipile reports the account working again (e.g. RECONNECTED after the user reconnects).

A _READY_ACCOUNT_STATUS message (OK/SYNC_SUCCESS) additionally clears user.unipile_syncing_since — the post-connect sync gate from ACCT_INITIALIZATION.md — and, only on that syncing→ready transition (never on a later steady-state ok for an account that was already ready), fires the two on-connect kickoffs (_kickoff_self_profile/_kickoff_chat_backfill) that used to run at connect time itself, before Unipile had necessarily finished setting the account up.