v4.3.0 build order: Product Surface in eight phases

claude-bot commented

2026-09-06 00:33:37 +00:00

Collaborator

Tracking issue for the v4.3.0 milestone (34 issues from the #319 audit plus #302–#305 and #479). Proposed order, with the reasoning, so the milestone is built as a sequence rather than a pile. Each phase is one or more PRs; phases marked ∥ can run in parallel with the previous one because they touch different files.

Principles

Fix the lies first. Anything that tells a user something false (a failed summary announced as ready, a lost vote that looks recorded, a network blip shown as "not recording") goes before anything that is merely hard to find. These are small, independent, and the highest impact per line.
Build the spine before hanging things on it. The nav bar and the single vocabulary come before the clusters that need links and names, or every later PR renames something twice.
Respect the stated dependencies. #305 depends on #302 and #303; #374 explicitly stays broken until #302–#305 land; #368's RSVP row needs #370; #375 and #379 share the "Bot Proposals" rename.
One delegate per file cluster. The workbench, the bot cogs, and the wiki pages each get a sequential lane so parallel work does not collide in the same files.

Phase 1 — Stop lying (all small, all independent, run in parallel) → ship early as v4.2.3

issue	what	size
#372	failed transcription announced as "Session Summary Ready"	S
#394	drop the unused privileged intent; no more crash-loop	S
#391	deep link in every Discord embed (`session_url` exists, thread it through)	S
#384	delete the orphaned CampaignNotes page	S
#383	players can set their own character name (one guard)	S
#376	WikiArticle usable at phone width (one class)	S
#479	archived campaigns stop materialising sessions and sending reminders (backend, with the "must stay live" tests)	M

Worth a patch release on its own: three of these are CRITICAL/HIGH bot lies on prod today, and none touches the frontend structure.

Phase 2 — The spine

#378 persistent nav bar (dashboard link, campaign switcher, Sessions / Prep / Wiki / Quotes inside a campaign; wiki no longer opens a new tab)
#379 one vocabulary (Prep, Wiki, Quests, Highlights, Recording; "Bot Proposals" → "Suggested wiki updates"; human labels in GenerationHistory; duplicate timeline removed)

Sequential in one lane: the nav links need the final names.

Phase 3 — The workbench lane (sequential, one lane)

#302 session picker default → #303 beat-notes round trip (read path, real append, no clobber) → #304 re-open restores output → #305 prep prompt gets GM intent (notes box in the prep panel, one-shot steer, rebalanced prompt) → #374 the navigational fixes (Prep-this-session button, query params, date labels, one save action, history refetch, palette 13 → 5–6) → #381 elapsed timers (GeneratorPanel is already open).

Decision recorded here, override if wrong: the palette cut folds series_titles, npc_voice and random_table into the tools they support, as the audit proposes.

Phase 4 ∥ — The attention surface (parallel with phase 3; different files)

#370 web RSVP (writes to the same attendance data as Discord reactions; party roster) → #380 status fields for the four invisible post-session tasks (migration) and the "Post-session processing" checklist → #368 the "Needs you" aggregate endpoint and dashboard block (open votes, missing RSVPs, transcripts awaiting approval, pending suggestions, in-progress sessions; countdown becomes a link).

Phase 5 ∥ — Bot self-diagnosis (parallel with phases 3–4; two lanes inside `bot/`)

Lane A (notifications/voting): #369 misconfigured channel fails loudly (no silent XACK, status back to the web app, per-field test message) → #371 acknowledge Discord votes and RSVPs, fix the web/Discord asymmetry, reject reactions on closed polls, log the Redis fallback, add-a-timeslot control
Lane B (sessions/recording/linking): #373 /help, guild-join welcome, real error strings, "no campaign bound" vs "nothing scheduled" → #393 /record start session identity, validated UUID, fulfilled stop, restart-safe active state (#399's recovery already covers the audio; this is the state and the messages) → #392 linking dead ends (real pages instead of raw JSON, correct DM on conflict, /link named in Profile)

Phase 6 — The wiki lane (sequential, one lane; after phase 2 so names are settled)

#375 proposal discovery (one-line link fix, entry link out of the hidden aside, inline queue replaced by an always-visible summary row) → #385 one review vocabulary and flow (Approve vs Review merge, busy states, no alert(), consistent append/replace copy) → #395 robustness (poll timeout, inline errors instead of page-level, confirm on Full regenerate) → #396 search box and paginated sidebar → #377 the silent-error sweep last, because it touches twelve files across every cluster and is cheapest once the others have settled.

Phase 7 — Onboarding and self-service

#387 /join/<code> link and first-run checklist → #388 players get the "Previously on" recap → #389 un-reveal, delete XP, .ics export → #382 explain gated states instead of hiding → #390 end-user docs and the Login page copy (last, so it documents what shipped).

Phase 8 — One live-session screen

#386 fold the Recording Dashboard into SessionDetail. Last because it is the largest restructuring and v4.4.0 redesigns this surface anyway. Decision recorded here, override if wrong: SessionDetail becomes the canonical screen (it is the hub every other link lands on); the standalone dashboard's live panel moves into it, the "Dashboard →" link goes, and recording controls become reachable from a proposed session.

Release shape

Phase 1 as v4.2.3 within a day; phases 2–8 as v4.3.0, deployed to dev after each phase for a look, prod once at the end. If the milestone runs long, phases 2–5 are a coherent v4.3.0 on their own and 6–8 can be v4.3.1.

Out of scope, noted

Nothing here is visual redesign; that is v4.4.0. #386 is the one place the two milestones touch, which is why it is last.

Tracking issue for the v4.3.0 milestone (34 issues from the #319 audit plus #302–#305 and #479). Proposed order, with the reasoning, so the milestone is built as a sequence rather than a pile. Each phase is one or more PRs; phases marked ∥ can run in parallel with the previous one because they touch different files. ## Principles 1. **Fix the lies first.** Anything that tells a user something false (a failed summary announced as ready, a lost vote that looks recorded, a network blip shown as "not recording") goes before anything that is merely hard to find. These are small, independent, and the highest impact per line. 2. **Build the spine before hanging things on it.** The nav bar and the single vocabulary come before the clusters that need links and names, or every later PR renames something twice. 3. **Respect the stated dependencies.** #305 depends on #302 and #303; #374 explicitly stays broken until #302–#305 land; #368's RSVP row needs #370; #375 and #379 share the "Bot Proposals" rename. 4. **One delegate per file cluster.** The workbench, the bot cogs, and the wiki pages each get a sequential lane so parallel work does not collide in the same files. ## Phase 1 — Stop lying (all small, all independent, run in parallel) → ship early as **v4.2.3** | issue | what | size | |---|---|---| | #372 | failed transcription announced as "Session Summary Ready" | S | | #394 | drop the unused privileged intent; no more crash-loop | S | | #391 | deep link in every Discord embed (`session_url` exists, thread it through) | S | | #384 | delete the orphaned CampaignNotes page | S | | #383 | players can set their own character name (one guard) | S | | #376 | WikiArticle usable at phone width (one class) | S | | #479 | archived campaigns stop materialising sessions and sending reminders (backend, with the "must stay live" tests) | M | Worth a patch release on its own: three of these are CRITICAL/HIGH bot lies on prod today, and none touches the frontend structure. ## Phase 2 — The spine - #378 persistent nav bar (dashboard link, campaign switcher, Sessions / Prep / Wiki / Quotes inside a campaign; wiki no longer opens a new tab) - #379 one vocabulary (Prep, Wiki, Quests, Highlights, Recording; "Bot Proposals" → "Suggested wiki updates"; human labels in GenerationHistory; duplicate timeline removed) Sequential in one lane: the nav links need the final names. ## Phase 3 — The workbench lane (sequential, one lane) #302 session picker default → #303 beat-notes round trip (read path, real append, no clobber) → #304 re-open restores output → #305 prep prompt gets GM intent (notes box in the prep panel, one-shot steer, rebalanced prompt) → #374 the navigational fixes (Prep-this-session button, query params, date labels, one save action, history refetch, palette 13 → 5–6) → #381 elapsed timers (GeneratorPanel is already open). **Decision recorded here, override if wrong:** the palette cut folds `series_titles`, `npc_voice` and `random_table` into the tools they support, as the audit proposes. ## Phase 4 ∥ — The attention surface (parallel with phase 3; different files) #370 web RSVP (writes to the same attendance data as Discord reactions; party roster) → #380 status fields for the four invisible post-session tasks (migration) and the "Post-session processing" checklist → #368 the "Needs you" aggregate endpoint and dashboard block (open votes, missing RSVPs, transcripts awaiting approval, pending suggestions, in-progress sessions; countdown becomes a link). ## Phase 5 ∥ — Bot self-diagnosis (parallel with phases 3–4; two lanes inside `bot/`) - Lane A (notifications/voting): #369 misconfigured channel fails loudly (no silent XACK, status back to the web app, per-field test message) → #371 acknowledge Discord votes and RSVPs, fix the web/Discord asymmetry, reject reactions on closed polls, log the Redis fallback, add-a-timeslot control - Lane B (sessions/recording/linking): #373 `/help`, guild-join welcome, real error strings, "no campaign bound" vs "nothing scheduled" → #393 `/record start` session identity, validated UUID, fulfilled stop, restart-safe active state (#399's recovery already covers the audio; this is the state and the messages) → #392 linking dead ends (real pages instead of raw JSON, correct DM on conflict, `/link` named in Profile) ## Phase 6 — The wiki lane (sequential, one lane; after phase 2 so names are settled) #375 proposal discovery (one-line link fix, entry link out of the hidden aside, inline queue replaced by an always-visible summary row) → #385 one review vocabulary and flow (Approve vs Review merge, busy states, no `alert()`, consistent append/replace copy) → #395 robustness (poll timeout, inline errors instead of page-level, confirm on Full regenerate) → #396 search box and paginated sidebar → **#377 the silent-error sweep last**, because it touches twelve files across every cluster and is cheapest once the others have settled. ## Phase 7 — Onboarding and self-service #387 `/join/<code>` link and first-run checklist → #388 players get the "Previously on" recap → #389 un-reveal, delete XP, `.ics` export → #382 explain gated states instead of hiding → #390 end-user docs and the Login page copy (last, so it documents what shipped). ## Phase 8 — One live-session screen #386 fold the Recording Dashboard into SessionDetail. Last because it is the largest restructuring and v4.4.0 redesigns this surface anyway. **Decision recorded here, override if wrong:** SessionDetail becomes the canonical screen (it is the hub every other link lands on); the standalone dashboard's live panel moves into it, the "Dashboard →" link goes, and recording controls become reachable from a `proposed` session. ## Release shape Phase 1 as v4.2.3 within a day; phases 2–8 as v4.3.0, deployed to dev after each phase for a look, prod once at the end. If the milestone runs long, phases 2–5 are a coherent v4.3.0 on their own and 6–8 can be v4.3.1. ## Out of scope, noted Nothing here is visual redesign; that is v4.4.0. #386 is the one place the two milestones touch, which is why it is last.

claude-bot changed title from v4.3.0 build order: Product Surface in eight phases</title> <parameter name="body">Tracking issue for the v4.3.0 milestone (34 issues from the #319 audit plus #302–#305 and #479). Proposed order, with the reasoning, so the milestone is built as a seq… to v4.3.0 build order: Product Surface in eight phases

2026-09-06 00:34:01 +00:00

claude-bot added this to the v4.3.0 - Product Surface: Navigation, Attention & Feedback milestone

Rows
Columns

v4.3.0 build order: Product Surface in eight phases #514