Purge and reprint bot status embed on restart and every few hours

[ebm5025]

Problem

Stale bot status embeds pile up in the bot status channel and have to be deleted by hand. The embed is tracked by message ID in the instructions table and edited in place; when those IDs drift — a redeploy, a manually deleted message, an embed-shape change — the old copies are orphaned and linger.

Fix

On restart and every 3 hours, the refresh now deletes all of the bot's own messages in the status channel and reprints from scratch.

• purgeBotMessages() paginates the channel and deletes each bot-authored message individually — bulkDelete can't remove messages older than 14 days, and the persistent status embeds are exactly that. Human messages (if any) are left untouched.
• It then drops the tracked instruction records (new public cancelTrackedInstructions() on InstructionsReadyAction) so the reprint posts fresh messages instead of trying to edit — and 404 on — the just-deleted ones.
• The purge is driven from inside the existing refresh loop, keyed on elapsed time (lastPurgeAt = 0 forces it on the first refresh after startup). The 30s live-data refresh continues to edit the current embed between purges, so nothing about the live behavior changes.
• refreshBotEmbed is now wrapped in a mutex so the periodic loop and bot data-change events (bot-prisma park/checkout) can't overlap and post duplicate embeds. This also hardens a pre-existing race in the edit path.

Notes

• Purge interval is a single constant (PURGE_INTERVAL = 3 * HOURS); easy to tune or move to an env var if you'd prefer.
• Only the bot's own messages are deleted, so no Manage Messages permission is required.

Testing

• yarn tsc — clean.
• yarn test:ci — 84 tests pass.

🤖 Generated with Claude Code

---

Generated by Claude Code