check-alertslisted

# Check Alerts Before writing your answer, read `examples/output.md` in this skill directory and match its density. A healthy run is one line; nothing about this skill is allowed to be chatty. Budget: ≤3 tool calls per rule. Silence when healthy is the product — an alert that talks every hour is one the user mutes. **This skill runs on every connector, the remote OAuth one included.** It uses only `get_conversions`, `get_microconversions`, `get_conversions_raw`, `get_overview`, `get_campaigns` and `get_top_referrers`, and all of them are announced everywhere. The alert tools the remote connector withholds — `list_alerts`, `get_alert_history`, `get_alert_stats` — are not available to it: they belong to Sealmetrics' own dashboard alerts, a different product this skill never touches. **Never refuse a check because of the connector.** A run that answered "check-alerts is local-only" left a site unwatched on exactly the connector nearly every user has. **Resolve the site before any call that takes a `site_id`, without announcing it.** If `list_sites` has not already run in this conversation, it is your first call: one call, counted in the budget. Use anything cached under `<state-dir>/<site_id>/` — profile, baseline, ledger, saved alert — only if that `site_id` is in the list. If it is not, that state was written by another Sealmetrics account on this machine: ignore it for this run, resolve the site from the list, asking if there are several, and never delete the other accoun