Pause and resume warmup on an account

Warmup only runs against accounts with status = active or aging. Pausing an account stops it from being scheduled as a sender or recipient in future warmup jobs.

POST /accounts/{id}/pause
POST /accounts/{id}/resume

Both take no request body and return 404 if the account doesn't exist. pause is refused with 409 (sandbox_warmup_locked) for the free sandbox mailbox.

curl -X POST https://app.warmerly.com/api/v1/accounts/1c2d3e4f-.../pause \
  -H "X-Api-Key: wmv_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

{ "ok": true }

resume sets the account back to active, clears needsReconnect and disconnectReason, resets consecutiveFailures to 0 and clears any campaign-sending pause. If the account is flagged as needing a reconnect, it first tests the stored login and answers 409 with code reconnect_required when that fails. Resuming a dead or flagged account can return 402 plan_capacity when the workspace is at its mailbox limit:

curl -X POST https://app.warmerly.com/api/v1/accounts/1c2d3e4f-.../resume \
  -H "X-Api-Key: wmv_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

{ "ok": true }