Shortening the transcript window is an ordinary confirmation (#1010) #1014

Merged
claude-bot merged 1 commit from fix/1010-transcript-window-ordinary-confirm into main 2026-10-01 22:19:30 +00:00
Collaborator

Closes #1010. The owner's answer to Q140, recorded as D268.

Before #680, shortening how long a campaign keeps transcripts destroyed the older ones that night, so the confirmation was D12's serious tier. Since #1005 they go to a bin, the GMs are warned, a GM can restore one, and putting the window back lets them all out. By D12's own rule a change that can be undone takes the ordinary tier.

What changes

CampaignSettingsRecording.jsx, ShortenAsk:

  • The confirm button is the primary one in every shape (it was red whenever transcripts were involved).
  • The "both" shape's lead paragraph is no longer red.
  • The words, the session names and the "Take a copy first? / Export the campaign" offer are unchanged.

Not changed

Admin → Recording & retention's "Cap retention now?" keeps its red button. It is a different question (one cap across every campaign), and the owner's answer was about a campaign's own window. Noted for the owner.

Checked

  • Full vitest: 3579 passed, 1 skipped; eslint 0 errors. No backend change.
  • Rendered in an e2e stack at 390×844 (touch) and 1440×900, light and dark, in both shapes (transcripts only; recordings and transcripts together), eight shots, looked at: the button is btn btn--primary and 44px high, nothing in the dialog carries modal__danger, the export offer is there, no sideways scroll, no console errors, no failed calls. Two sessions were aged in the throwaway stack's database so the question had something to name.

🤖 Generated with Claude Code

Closes #1010. The owner's answer to Q140, recorded as D268. Before #680, shortening how long a campaign keeps transcripts destroyed the older ones that night, so the confirmation was D12's serious tier. Since #1005 they go to a bin, the GMs are warned, a GM can restore one, and putting the window back lets them all out. By D12's own rule a change that can be undone takes the ordinary tier. ## What changes `CampaignSettingsRecording.jsx`, `ShortenAsk`: - The confirm button is the primary one in every shape (it was red whenever transcripts were involved). - The "both" shape's lead paragraph is no longer red. - The words, the session names and the "Take a copy first? / Export the campaign" offer are unchanged. ## Not changed Admin → Recording & retention's "Cap retention now?" keeps its red button. It is a different question (one cap across every campaign), and the owner's answer was about a campaign's own window. Noted for the owner. ## Checked - Full vitest: **3579 passed, 1 skipped**; eslint 0 errors. No backend change. - Rendered in an e2e stack at 390×844 (touch) and 1440×900, light and dark, in both shapes (transcripts only; recordings and transcripts together), eight shots, looked at: the button is `btn btn--primary` and 44px high, nothing in the dialog carries `modal__danger`, the export offer is there, no sideways scroll, no console errors, no failed calls. Two sessions were aged in the throwaway stack's database so the question had something to name. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Shortening the transcript window is an ordinary confirmation (#1010)
All checks were successful
CI / Does this change touch the recording path? (pull_request) Successful in 19s
CI / Synthetic session harness (no GPU, no LLM) (pull_request) Has been skipped
CI / Bot/backend version sync (pull_request) Successful in 1m12s
CI / Backend lint (ruff) (pull_request) Successful in 1m19s
CI / Docker image build (pull_request) Successful in 1m22s
CI / Feedback site tests (pull_request) Successful in 1m53s
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 2m30s
CI / Bot tests and audit (pull_request) Successful in 4m24s
CI / Frontend (shard 2/2) (pull_request) Successful in 7m27s
CI / Frontend (shard 1/2) (pull_request) Successful in 9m8s
CI / End-to-end journeys (keyboard) (pull_request) Successful in 10m2s
CI / End-to-end journeys (desktop) (pull_request) Successful in 10m3s
CI / End-to-end journeys (phone) (pull_request) Successful in 17m29s
CI / Backend migration, tests, and audit (pull_request) Successful in 20m25s
6ec85e4e23
D268, the owner's answer to Q140: with #680's bin behind a transcript the
change can be undone, so by D12's own rule it takes the ordinary tier. The
question keeps its words and the offer to export first; the red button and
the red lead paragraph go.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sign in to join this conversation.
No description provided.