Review events: the GM can change who was involved when rewording an event #1190

New issue

Closed

opened 2026-10-14 04:20:36 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-10-14 04:20:36 +00:00

Collaborator

Owner request, 13 Oct 2026. Not urgent; a candidate for 4.5.2 or after.

On a session's Review tab (pages/session/ReviewEvents.jsx), each event offers Strike, Reword and ⋯ More (kind, Emphasise). Reword changes the sentence only. The event's actors (who was involved) come from extraction and cannot be corrected, so a wrongly attributed event stays wrongly attributed in the summary and anything built from it (#1189 makes events more specific, which makes a wrong actor more visible).

Wanted

The Reword box also shows the event's people, as removable chips, with a picker to add one: the campaign's player characters and members first, then NPC pages from the wiki, matching what extraction would name.
Saved with the rewording, through the same correction path, so the change is recorded on the run like a reword (who, when), survives a recompose, and feeds the next summary composed from these events.
An event left with nobody is allowed (scenery, weather, a narrated happening) but is said plainly in the row.
The read-only event log and the summary's anchors show the corrected people.

Notes

Find how a reword is stored (session_pending_corrections, the run's beats) and extend that rather than adding a second store.
Attribution matters to the accuracy evals (#349): a GM correction is ground truth for that session; check whether corrections should feed the eval fixtures or stay out.
Keyboard and phone: the chips and picker must work by keyboard (the keyboard journey) and fit at 390 px.

Owner request, 13 Oct 2026. Not urgent; a candidate for 4.5.2 or after. On a session's Review tab (`pages/session/ReviewEvents.jsx`), each event offers Strike, Reword and ⋯ More (kind, Emphasise). Reword changes the sentence only. The event's actors (who was involved) come from extraction and cannot be corrected, so a wrongly attributed event stays wrongly attributed in the summary and anything built from it (#1189 makes events more specific, which makes a wrong actor more visible). ## Wanted - The Reword box also shows the event's people, as removable chips, with a picker to add one: the campaign's player characters and members first, then NPC pages from the wiki, matching what extraction would name. - Saved with the rewording, through the same correction path, so the change is recorded on the run like a reword (who, when), survives a recompose, and feeds the next summary composed from these events. - An event left with nobody is allowed (scenery, weather, a narrated happening) but is said plainly in the row. - The read-only event log and the summary's anchors show the corrected people. ## Notes - Find how a reword is stored (`session_pending_corrections`, the run's beats) and extend that rather than adding a second store. - Attribution matters to the accuracy evals (#349): a GM correction is ground truth for that session; check whether corrections should feed the eval fixtures or stay out. - Keyboard and phone: the chips and picker must work by keyboard (the keyboard journey) and fit at 390 px.

claude-bot added this to the v4.6.0 - Calendar, Templates & Table Tools milestone

2026-10-17 04:21:24 +00:00