Quest Board — outside the app

Everything Quest Board says where it does not own the screen: the campaign’s Discord channel, its slash commands, reactions and direct messages; email; calendars; and the installed app. Seventy-one placements across eight surfaces, none of them drawn before; reviewed 20 September.

New on 26 September: what the build of this lane added (#736) — Test the bot, the two pages an email opens, Discord DMs on the notification grid, choosing the Discord server and channels, and the voice channel, and a recording announcement nobody could post — drawn first, below. The older stills are brought into line with the decisions since (D96, D97, D123, D151–D163); the questions the drawing raised were answered the same day as D221 to D232, and the pickers redrawn for D226.

The chat, mail and calendar frames here are plain stand-ins for somebody else’s client. What is Quest Board’s to choose is what the message says and how it is laid out, and that is what these draw.

Reviewed, settled, and still open

Settled before drawing

D13: a quiet “updated — reload” notice, and installing stays the browser’s.
D17: one time, the reader’s own. Discord timestamps do this by themselves; email uses the reader’s profile.
D48 (lane 1b): Discord is one of the three places a notification can go, once an account is linked.
D61 (lane 6d): showing a handout posts it, switchably. D2: a concern reaches the GM alone.
The consent model: recording announces itself in the channel. That announcement is drawn here.

Proposed while drawing, accepted on review (20 September: “no changes”)

One shape for every post: a coloured edge for its kind, the kind first in the title, the facts as fields, and one link back. Today’s posts each have their own emoji and shape.
A post meant for the GM goes to the GM. At risk, a failed summary and audio about to be deleted are GM-facing but posted publicly today; they would arrive by direct message where the GM has linked Discord, and in the channel only where they have not.
“Maybe” gets a reaction (❔) on a confirmed session, which Discord has no way to say today — and every post says in its own footer what its reactions mean, since taking a reaction off a time means “no”, not “undo”.
Every email can be stopped in one click, rather than by a sentence naming a setting.
A link the server cannot make is left out, not drawn broken — already true of the code, and kept.

Decided since, from the build (24–26 September)

D96: a summary reaches Discord only once the GM approves it, so “The summary is ready” and its accuracy reactions are retired, and the approved post carries the summary. D97: a player’s note is for them and the GM. D123: the /record start picker lists only what can record. D67: Admin’s Discord check posts nowhere.
D124, D146, D149, D150: Test the bot, in Settings → Recording, retention & AI and on the session page while the window is shut; 30 seconds; the audio always deleted once transcribed; the results kept or deleted; not in Admin.
D151: the GM’s warnings go to her bell, and by DM on her settings. D152: a DM says the bell’s line, the time and a link. D153: a campaign with no Discord emails its sessions. D154, D155: the two pages an email opens. D156: a command means the campaign whose channel it’s typed in. D157: Take it back deletes the post. D158: “Recording · /help”. D159: a voice channel setting, and Where. D160: /concern is anonymous. D161: the star and wish is the player’s choice. D162: the recap email waits for approval. D163: /ask lists the sessions it drew on. D171: a recording starts even when its announcement can’t be posted, and the GM is told.

Settled 26 September: the questions lane 10’s drawings and build raised

D221 (O18): Stop early ends a test’s recording, and what was heard is still transcribed and summarised.
D222 (O19): Test the bot on the session page opens the section in Settings.
D223 (O20): an administrator reads “you run this server” with a way into Admin; everyone else reads the administrators’ names.
D224 (O21): “Stop these emails” stops that kind from every campaign.
D225 (O22): the star and wish’s In Quest Board cell reads “On Home”.
D226 (O23, the owner’s choice over the recommendation): pickers now for the server, the channel and the voice channel, listing only the GM’s own Discord servers and the channels the bot can see; a GM who hasn’t linked Discord types the IDs. Redrawn in the voice channel section.
D227 (O24): a test’s AI use counts in the campaign’s usage and credits, marked as a test.
D228 (O25): no recording bar during a test.
D229 (O26): nothing in Discord when a test dies with the bot.
D230 (O27): a campaign with its own webhook counts as having Discord, so no default email.
D231 (O28): a summary that couldn’t be written never reaches the channel.
D232 (O29): the star and wish is its own sub-row under Sessions on the grid.

Nothing is open on this page.

The coverage check: none missing. Of 71 placements at the first review: 55 drawn, 3 replaced by a proposal here, 7 belonging to another surface, 1 behaviour with nothing to see, and 5 deferred: the speculative Matrix and Element ideas, said so rather than drawn. EXT-8 has no rows. Since lane 10’s drawings: 80 on these surfaces (61 drawn, 6 replaced, 7 elsewhere, 1 behaviour, 5 deferred), and 11 more drawn here but placed on Settings, the session page, the recording panel and Notifications (IS-443 to IS-456). The check is coverage/lane8.py beside the catalogue.