Add EQNotify feature under /eqnotify command

[ebm5025]

Summary

Merges the standalone EQNotify batphone-notification bot into castle as a native feature under a new /eqnotify slash command. Subscribers register a delivery channel and a set of keyword tags; batphones posted in the batphone channel are matched against each subscriber's tags (buff / last-hour RTE calls filtered out) and an alert is pushed to their phone.

Ported from a v11-era standalone discord.js bot to castle's conventions: TypeScript, discord.js v14, Command/Subcommand classes, and Prisma/Postgres persistence (replacing the original users.json).

Commands

All commands moved to subcommands under /eqnotify:

• Self-service: register, unregister, add-tag, remove-tag, list-tags, clear-tags, test
• Officer/Mod/Knight-gated: add-user, remove-user

The original prefix commands map as: !add → add-tag, !remove → remove-tag, !list → list-tags, !cleartags → clear-tags, !adduser → add-user, !testmsg → test.

Delivery backends

Two backends are selected per-subscriber and dispatched through a pluggable notifier that switches on type:

• WirePusher (Android only) — carried over from the original.
• Telegram (iOS/Android/desktop) — closes the WirePusher Android-only gap. Sending is a single authenticated POST to the Bot API; no new dependencies. Requires TELEGRAM_BOT_TOKEN; when unset, Telegram is offered nowhere and WirePusher works standalone.

Notable implementation detail

The original was a separate bot, so it saw castle's batphones as another bot's messages. Integrated, batphones are authored by castle itself (via /bp send), and messageCreateListener early-returns on bot authors — so the EQNotify dispatch runs before that guard, filtered to the watched channel. The buff/RTE content filter, substring tag-matching, and the all tag are all preserved. The watched channel defaults to the batphone channel and is overridable via eqnotifyChannelId.

Changes

• New eqnotify_subscriber Prisma model + migration (20260724000000_add_eqnotify_subscribers).
• New feature under src/features/eqnotify/: command + subcommands, service, notifiers (WirePusher/Telegram/dispatcher), and a channel message-action.
• Pure matching/filtering logic extracted to matcher.ts with unit tests.
• New config: TELEGRAM_BOT_TOKEN (optional), eqnotifyChannelId (optional).
• README updated (feature list, env vars, EQNotify usage section).

Deployment notes

• Run the new migration (prisma migrate deploy — already wired as the postdeploy step).
• To enable Telegram: create a bot via @Botfather and set TELEGRAM_BOT_TOKEN. Users get their numeric chat ID (e.g. from @userinfobot) and paste it into /eqnotify register.

Testing

• yarn test:ci — 71 tests pass (11 new for the matcher).
• yarn tsc — clean.

🤖 Generated with Claude Code

---

Generated by Claude Code