[ChristopherPHolder]

What and why

Records the soundboard sounds and emoji reactions people send in the office voice channel, and lets banter see them.

Discord only sends these (VOICE_CHANNEL_EFFECT_SEND) to clients that are in the voice channel. Nothing in the REST API or the audit log has them, so the bot now sits in the office while anyone is there:

• It joins when the office opens and leaves when it empties, already self-muted and self-deafened. It only sends the gateway's voice-state message and never opens an audio connection, so it can't hear or send anything. At startup it joins if people are already in, and otherwise leaves, in case an earlier run left it behind.
• Each effect in the office goes to a new office.voice_effects table through the same buffered recorder: sound ID, name and volume, emoji and animation. Names come from the server's sounds (kept up to date with the non-privileged GuildExpressions intent) and Discord's default sounds (fetched once at startup). Bots are left out.
• A new office_activity view adds PlayedSound <name>, Reacted <emoji> and SentEffect events to voice_activity. Banter now reads that view, and the prompt explains the new events.
• The gateway drops every update and effect from the bot's own user ID, so it's never announced or recorded, even when Discord leaves out the member.
• A member's display name is no longer overwritten with their user ID when Discord sends something without the member (this also affected voice updates before).
• It logs a warning at startup if it lacks the Connect permission on the office channel.

Migration 0003_record_voice_effects only adds a table, indexes and a view.

Before merging: give the bot the Connect permission on the office channel. Without it, everything else keeps working, but nothing gets recorded and a warning is logged.

Known limits:

• Whenever the bot's Discord connection is ready or resumed, it goes back to where it should be. If someone kicks it from voice by hand, it rejoins the next time the office opens.
• I haven't checked against the real Discord yet whether effects still arrive while the bot is self-deafened. Watch for rows in voice_effects after the deploy.

How I tested it

• Program tests for when the bot moves: it leaves an empty office at startup, joins when the office opens, leaves when it empties, and joins straight away when people are already in. Also that effects are recorded only from the office and never from bots.
• PGlite tests for the new table and view: sounds, reactions and other effects show up next to voice activity in the banter history, and a repeated write is stored once.
• Recorder tests: effects are written in order with everything else.
• Ran scripts/try-banter.ts without --call-ai: the camera-party scenario now includes soundboard lines, and the prompt renders them.
• Not tried against a real Discord server.

Checklist

• pnpm typecheck, pnpm lint, pnpm test and pnpm build pass
• Tests cover the change
• README updated if what gets posted, the configuration or the deploy changed
• New environment variables are wired through (none added)
• Ready to ship: merging this deploys it to production (needs the Connect permission first)