# Feature Roadmap A living document describing what's planned, why, and the concrete steps to ship it. Each feature also has a card on the [Bot Development project board](https://github.com/users/jason-tucker/projects/3) with a matching breakdown — bring those into "In Progress" when you start, and use the implementation steps below as the punch list. --- ## Status legend - ✅ **Shipped** — running in production, documented, and wired into `/help` - 🟡 **Infrastructure ready** — schema and/or `/sudo → Settings` toggle exists, but the user-facing behavior hasn't been built - 🔵 **Designed** — concept agreed, scope written, no infrastructure yet - 💭 **Idea** — bullet on a napkin; needs more thought before estimating --- ## ✅ Recently shipped The 0.7.x and 0.8.x lines covered most of the original Phase 5/6 backlog: - ✅ **Auto voice channels with persistent control panel** — hubs rename in place, replacement hub spawns, attached private text channel, sticky 📋 Open Panel button, reconciler on startup - ✅ **Voice control panel buttons** — Rename, Lock/Unlock, Hosts (single panel listing all members with rank emojis), Templates (Auto / Counter / Comp 5-stack / Tryhard / Chill), Claim, Delete - ✅ **Random tech default channel names** — `Sloppy Ethernet` style fallback when no rich-presence game is active - ✅ **`/report` flow** — modal → owner DM with Approve/Reject (notify or silent) → GitHub issue - ✅ **`/sudo → Settings` panel** — runtime config for sudo users, channels, voice cleanup delay, and the auto-thread channel list. Backed by `bot_settings` (key/value overrides), `sudo_users` (members granted sudo at runtime), and `auto_thread_channels` (the dynamic auto-thread list). See [Slash Commands](Slash-Commands#sudo) for the full sub-panel reference. - ✅ **Auto Threads** — channels added under `/sudo → Settings → Auto Threads` get a public thread on every non-bot message. Default thread name `{author} — {first line}` (100-char cap). Backed by `auto_thread_channels`. Requires the `MessageContent` privileged intent. **Shipped as a single dynamic list rather than the per-channel feature flags originally drafted** (clips/food were collapsed into one panel during implementation). - ✅ **Hub Channels (dynamic)** — `/sudo → Settings → Hub Channels` adds/removes hubs at runtime. `HUB_CHANNEL_IDS` env is now a one-time legacy seed list; the DB is authoritative. Reconciler-driven hub recreation, replacement-hub flow, and `isHubChannel()` are all cache-backed. - ✅ **`channel.auto_voice_category` override** — the `AUTO_VOICE_CATEGORY_ID` env value is now overridable from `/sudo → Settings → Voice`. Auto-channel creation, hub registration, and the reconciler all read via `getSetting() ?? env.AUTO_VOICE_CATEGORY_ID`. - ✅ **User profile editor** — sudo-side editor under `/sudo → Settings → User Profiles` and via right-click → Manage User → Edit Profile. Self-service via `/profile`. Sudo edits all fields; self mode covers display name, birthday, and opt-out toggles. Every edit logs a `profile-edit` line. - ✅ **Birthday pings** — daily scheduler that fires at the configured target hour (default 9). Members opt out via `/profile`. Idempotency via `bot_settings.birthday.last_run_date`. Feb 29 birthdays handled in non-leap years. - ✅ **Game roles + game prefs + `/play` LFG** — `/sudo → Settings → Games` is a full catalog editor (name / aliases / sort / view role / ping role / channel / visibility / archive / delete). `/games` is the self-service prefs editor; **Manage User → Game Prefs** is the sudo-on-behalf path. Toggling auto-syncs the corresponding Discord role on the target member. `/play ` posts an LFG message in the game's channel pinging its `ping_role_id`, with a 30-minute per-(user,game) cooldown (sudo-bypass via `force:true`) and `allowedMentions` hardening so `@everyone`/`@here` are never resolved. - ✅ **Social feeds** — `/sudo → Settings → Social Feeds` adds RSS-backed sources (e.g. an rss.app Instagram feed) reposted into a channel. Poller dedupes by `last_seen_id` and posts new items oldest-first every ~30 min; per-feed items-per-poll cap (sudo 3, bot owner unlimited). Gated by `feature.social_poller`. Backed by `social_feeds`. - ✅ **Reaction roles (#37)** — `/sudo → Settings → Reaction Roles` builds a message with emoji=role mappings; reacting toggles the role. Optional expiry creates temporary game-night roles that auto-clean. Backed by `reaction_role_messages` / `reaction_role_mappings`. - ✅ **Welcome / goodbye messages** — `/sudo → Settings → Welcome / Goodbye` sets a channel + template (tokens `{user} {server} {member_count} {account_age}`) for join/leave posts. Both default OFF. - ✅ **Auto-join roles (#36)** — `/sudo → Settings → Auto Roles` applies roles to every new member. Gated by `feature.auto_role_on_join` (default OFF). Backed by `auto_join_roles`. - ✅ **Color roles (#38)** — `/color` self-service color picker (one color at a time). Gated by `feature.color_roles` (default OFF). Backed by `color_roles`. - ✅ **Channel archive** — `/sudo → Settings → Archive` archives/unarchives channels in opt-in categories (stores original name + parent for restore). Backed by `archive_eligible_categories` / `archived_channels`. - ✅ **botpanel integration (Redis command/event bus)** — most flows are also RPC verbs on `cmd.squishy.*` (HMAC-signed) so the web dashboard drives the same actions; cache-invalidate + event fan-out on `bot.squishy.*`. All optional — the bot runs without Redis or `BOTPANEL_RPC_SECRET`. See [Architecture](Architecture). --- ## 🔵 In progress / next up The current active backlog is tracked on the [Bot Development project board](https://github.com/users/jason-tucker/projects/3). The backlog issues #11–#38 (filed 2026-05-11) are the carved-up `/sudo` brainstorm; #39 is the umbrella for designing the future `/mod` command. ### Recently shipped from this brainstorm - ✅ **#11** — Dynamic `isBotOwner()` from the Discord Application Team. Bot-owner permission checks now resolve at runtime; see [Bot Owner](Bot-Owner.md) for setup. /report approval gates via this. - ✅ **#12** — Per-hub auto-channel defaults (template, manual name, user limit). See [Auto Voice Channels → Hub defaults](Auto-Voice-Channels#hub-defaults---pinned-template--name--user-limit). - ✅ **#13** — Hub lockdown — per-hub (sudo) and server-wide (bot-owner). See [Auto Voice Channels → Hub lockdown](Auto-Voice-Channels#hub-lockdown--temporary-kill-switch). - ✅ **Owner grace** — original owner can reclaim within 5 min, configurable in `/sudo → Settings → Voice → Owner grace (ms)`. See [Auto Voice Channels → Ownership transfer](Auto-Voice-Channels#ownership-transfer). - ✅ **Auto-thread media gate** — auto-thread channels only thread messages with attachments or resolved link embeds. ### Operational - [ ] Verify `AUTO_VOICE_CATEGORY_ID` and `HUB_CHANNEL_IDS` in `.env` are correct for the ITSRI guild — see [issue #3](https://github.com/jason-tucker/squishybot/issues/3) - [x] Enable Presence Intent in Discord Developer Portal — [issue #4](https://github.com/jason-tucker/squishybot/issues/4) (resolved) - [x] GitHub Actions auto-deploy on push to main — done end-to-end --- ## 💭 Ideas backlog Light sketches — bring one to "Designed" status before it goes on the project board. - **Voice channel "party" / LFG mode** — members in an auto-channel can mark themselves LFG; the channel name appends `(LFG x/y)` and a button lets others join. - **Auto-name cycling** — if the rich-presence game changes mid-session, the auto-channel name updates to match (with rate-limit guards — Discord limits channel renames to 2/10min). - **OC-style stock widget for other businesses** — port otterbot's `oc_stock` pattern if a non-MKE business in the server wants the same kind of board. - **External webhook intake** — `POST /webhook/` endpoint that posts to a configured channel (e.g. for GitHub Actions completion notices, Grafana alerts). Would require a small HTTP server alongside the Discord client. --- ## How to use this roadmap 1. When you start working on a feature, move its project board card to **In Progress**. 2. Add a dated, real-semver section at the top of `CHANGELOG.md` (Keep a Changelog format, with a `v · ` footer) and bump `package.json` to match. 3. Treat the implementation steps above as a checklist — tick them off in commit messages or PR description. 4. When the feature ships, move the card to **Done**, mark the row above ✅ Shipped, and prune steps from this page (keep the headline + 1-line summary so the history is readable).