Test the bot: a full-pipeline check (record → transcribe → summarise) outside any session (D124) #824

New issue

Closed

opened 2026-09-26 03:32:29 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-09-26 03:32:29 +00:00

Collaborator

The owner's decision, 2026-09-26 (D124). A GM needs a way to check the recording setup before a session that doesn't attach anything to a real session.

Why now. D116 made starting a recording start the session, and D123 limits recording to a window before the confirmed start: 30 minutes by default, settable per campaign. Before those, the only way to test the bot was to record on a real session. That attached the test audio to it, and a transcript and draft summary followed for a game that hadn't been played.

What it does:

Recording: the bot joins the campaign's voice channel and records a short sample, per speaker. It says who it can and can't hear.
Transcription: the sample goes through the configured Whisper endpoint, speaker by speaker.
Summarisation: the merged transcript is summarised with the configured LLM, so a broken AI configuration shows up here and not after a real session.
Results: shown to the GM, with each stage's result, timing and any failure in plain words.
Keep or delete: chosen when the test is launched.
- Keep: the test run, its transcript and its summary stay in the campaign as a test run, attached to no session, until the GM deletes them.
- Delete when done: the audio and results are removed once they've been shown.

Constraints:

The channel announcement still happens when recording begins (the consent model). The announcement says it's a test.
Nothing a test produces reaches players. No notifications, no Discord summary post, no wiki suggestions, no highlights.
Audio handling follows the existing audio_temp rules. Test audio is never committed anywhere.
A test isn't a session: no number, and it isn't in the Sessions list or analytics.

Where it lives (proposed):

a "Test the bot" entry in Settings → Recording, retention & AI;
the same action on Table mode's recording panel when no session is live.

It must be mocked up in the prototype and given catalogue rows before it's built (#659), and its home lane decided: lane 10, "Outside the app" (#736), is the natural fit.

The bot contract: this needs new /api/bot/* routes, or a mode on the recording start. Decide in the design whether that's an additive change (no bump) or not.

Refs #731, #736, #366.

**The owner's decision, 2026-09-26 (D124).** A GM needs a way to check the recording setup before a session that doesn't attach anything to a real session. **Why now.** D116 made starting a recording start the session, and D123 limits recording to a window before the confirmed start: 30 minutes by default, settable per campaign. Before those, the only way to test the bot was to record on a real session. That attached the test audio to it, and a transcript and draft summary followed for a game that hadn't been played. **What it does:** - **Recording:** the bot joins the campaign's voice channel and records a short sample, per speaker. It says who it can and can't hear. - **Transcription:** the sample goes through the configured Whisper endpoint, speaker by speaker. - **Summarisation:** the merged transcript is summarised with the configured LLM, so a broken AI configuration shows up here and not after a real session. - **Results:** shown to the GM, with each stage's result, timing and any failure in plain words. - **Keep or delete:** chosen when the test is launched. - **Keep:** the test run, its transcript and its summary stay in the campaign as a test run, attached to no session, until the GM deletes them. - **Delete when done:** the audio and results are removed once they've been shown. **Constraints:** - The channel announcement still happens when recording begins (the consent model). The announcement says it's a test. - **Nothing a test produces reaches players.** No notifications, no Discord summary post, no wiki suggestions, no highlights. - Audio handling follows the existing `audio_temp` rules. Test audio is never committed anywhere. - A test isn't a session: no number, and it isn't in the Sessions list or analytics. **Where it lives (proposed):** - a "Test the bot" entry in Settings → Recording, retention & AI; - the same action on Table mode's recording panel when no session is live. It must be mocked up in the prototype and given catalogue rows before it's built (#659), and its home lane decided: lane 10, "Outside the app" (#736), is the natural fit. **The bot contract:** this needs new `/api/bot/*` routes, or a mode on the recording start. Decide in the design whether that's an additive change (no bump) or not. Refs #731, #736, #366.