calibrate-watchdoglisted

# Calibrate Watchdog Before writing your answer, read `examples/output.md` in this skill directory and match its density, structure and tone. It is the reference for what a good run of this skill looks like. Build the hour-of-week baseline that makes intraday monitoring meaningful, and store it so the hourly watchdog never has to rebuild it. Budget: ≤40 tool calls — high because it runs once and every later watchdog run costs ≤6. This is a **manual, explicit** skill. Never run it from a casual question and never run it on a schedule. **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 account's files. Rules in `skills/seal-copilot/references/state-schema.md`, "A cached site belongs to one connection". ## Why this is a separate skill The MCP has no hourly time series on the aggregated tools. Hourly counts come only from `get_microconversions_raw`, which is capped at a 31-day range and 100 rows per page. Rebuilding a 4-week baseline on every hourly check would cost hundreds of calls, so the baseline is bu