The GM's Review, part two — events and corrections, who was there, highlights — and the old session page goes (SESS-4, lane 4) #818
Loading…
Reference in a new issue
No description provided.
Delete branch "build/lane4-page-review-b"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Lane 4's last page PR (#730). Review now draws all six of its sections, and
SessionDetail.jsxis deleted, after an audit of everything it still offered.The events it was built from (D31, D104)
PUT /pending-corrections/{beat_id}, in order. The pending banner counts them, and a reload keeps them.Who was there
GET /api/sessions/{id}/character-overrides.Highlights
The old page goes: the audit
Every feature
SessionDetailstill offered now has a home on the new pages. The PR's commit6f90cd7blists each one and where it went.SessionDetailand its test;PostSessionChecklist,SessionHighlights,ProcessingQueueNoteandSeriesUnderTitle;onlymode andLegacyLeaveGuard;restorePreviousSummary,fetchMyNotesandupsertMyNoteclients. Their server endpoints stay.ColdOpenPanel,ElapsedTimer,RecordingPanelandTitleSuggestions.ui/Segmented, whose group with nothing chosen couldn't be reached by keyboard.Departures (reasoned in the commits)
Checks
With this,
lane3.py's SESS-4 rows are all built, replaced or deferred. Lane 4's last PR, J5's journey, follows.🤖 Generated with Claude Code
`GET /sessions/{id}/character-overrides` (GM only) is the read the pin never had (IS-236 to IS-238): per member with a character, the character this session attributes to them (the pin, or their active character), whether it is a pin, and every character they could be pinned to. Additive; the PUT is unchanged. The bell's `transcript_failed` row links to `/sessions/{id}/review`, where Try again lives since 7a. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>Review draws its last three sections itself; the old page's `only` mode is no longer used by it (it goes in the next commit). - The events it was built from: "N events checked against the transcript · one did not check out", each row time · who · what with Strike, Reword and ⋯ More (the kind picker, Emphasise/Unemphasise). Every correction is saved at once through `PUT /pending-corrections/{beat_id}` with that event's whole set (D31), serialised so answers cannot land out of order; Undo is a PUT of what remains. Tags (Struck / Reworded / Now a table note / → story: kind / → emphasised / → not emphasised), "Corrected by you", "was: a story event, kind", the star, "Did not check out: reason" (IS-240, from the latest run), and a citation by transcript time ("at 1:09:12", D104) that opens the transcript fold at that line. Reword counts 500; Escape cancels it and the kind picker. A 422 is said beside the row. Table notes folded, each with Make it story. While a rewrite runs, or the saved set is stale, the events say why once and offer nothing. - Who was there: the recording's proposals (spoke / in channel, silent / not heard, and the voice matched to nobody with how long it talked), Use these and Leave it, "Filled in from the recording", the channel-read failure, There / Not there per player, and who played whom from the new pins read. - Highlights: drafts said, Edit and Delete each, Add one (A quote / A moment, Who said it, When · optional, the line — "Write the line itself."), and the drawing's delete question. - The three buttons a rewrite holds say why on one line; each keeps its reason as its accessible description. - Review makes its own attendance read (the lead counts it); Read's reads are no longer made for Review. Segmented keeps a tab stop with nothing chosen. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>