mochi-watch

@mochi-watch — Check Watch Items

Check watch items from the persistent watchlist, compare with last known status, and notify on changes.

The watchlist is its own scheduler. Each item's checkIntervalMins is consumed by the queue poller to decide when to re-check. NEVER create a cron_add / @kirocrew-cron job for a watch item — the cron would run the check a second time and burn tokens twice. When creating a watch item, ALWAYS set checkIntervalMins explicitly from the user's stated frequency (daily = 1440, hourly = 60, etc.); omitting it silently applies the 10-minute default, which is almost never what the user asked for. That value is remembered as baseIntervalMins and is the floor for every later adjustment.

Steps

1. Check Status

For each item, use the appropriate tool:

Kind	How to check
url	web_fetch({ url: "<target>" })
custom	Decide based on the target description — web_fetch, or whatever available tool fits best
slack-channel	Read the channel's recent messages since lastChecked, then summarize key topics. Use whichever Slack tool you actually have; do not guess at a name.
slack-topic	Search Slack for <target>, newest first, and keep results newer than lastChecked. Same rule about tool names.

If a check fails, try an alternative tool before incrementing failCount. Only increment failCount if ALL alternatives also fail. Continue checking other items — don't abort the batch on one failure. If a slack-* item's kind needs a Slack tool you do not have, record that as the failure reason rather than improvising a tool call.

⚠️ CRITICAL: Even if a check fails (JS-rendered page, 403, network error, no data), you MUST still call update_watchlist with a historyEntry for that item. This advances nextCheckAfter so the item is not immediately re-checked on the next poll. Failing to write historyEntry causes the item to stay "due" forever, triggering a spawn storm (100+ agents per hour). Use changed: false and record the failure reason in result.