2 Commits

Author	SHA1	Message	Date
Mike Swanson	95daa70551	feat(alerts): route RMM/Dev alerts to private #dev-alerts, Syncro stays in #bot-alerts ... post-bot-alert.sh now auto-routes by message prefix: [RMM]/[DEPLOY]/[DEV]/[BUILD]/ [GURURMM]/[SMARTBADGE-WATCH] -> #dev-alerts (1509998508198068484, private; Howard+Mike); everything else incl. [SYNCRO] -> #bot-alerts (unchanged). Optional 2nd arg (dev|bot| <channel_id>) overrides. Existing call sites (scheduled SmartBadge task, /rmm) route correctly with no change. /rmm skill docs updated to reference #dev-alerts. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-05-29 12:18:49 -07:00
Mike Swanson	34a0d73d00	syncro: post a summary + link to #bot-alerts after every write ... Add .claude/scripts/post-bot-alert.sh — reusable, soft-failing Discord poster that reads the bot token from the SOPS vault (bot-token.sops.yaml, credentials.bot_token) with a .env fallback, so it works from any machine. Wire it into the /syncro skill: a Hard Rules pointer, a billing-workflow step (17), and a "Post to #bot-alerts" reference section with the message format and ticket/invoice/customer link mapping (computerguru.syncromsp.com). Scoped to write ops (create/update/close/comment/bill/customer); reads post nothing. Best-effort — never fails the Syncro write it follows. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-20 16:43:23 -07:00