fix(webapp): the session page says calmly when a summary was read in parts (#1187) #1188
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/1187-summary-limits-note"
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?
Closes #1187. Not to merge until the owner's wording is in (Wording Review page, part "Session page: the AI note"); the three strings are provisional constants in
pages/session/ReadView.jsx(PARTS_TITLE,PARTS_BODY,TRUNCATED_WARNING).The session page showed "Summarised with a limited setup" with a lock icon and every capability gap on the run, joined, to every member, including risks that did not happen. Now it shows only what applied to this summary:
Backend. Migration
f1187a1b2c3d(aftere1158a1b2c3d) addssummarisation_runs.windows_read(int) andprompt_truncated(bool), both nullable; existing runs read NULL. Set where the run is written: the window count from the beats and chunked prose paths;prompt_truncatedfrom the prompt-token check, which was log-only (the existingtruncatedcolumn is the output cap, a different thing). A recompose copies both from its source run. The session read fieldsummary_limits(list of titles) becomessummary_note({truncated, parts}or null). An old run with no window count shows the parts note only if its stored gaps include chunking.Verified
On
docker-test: 379 backend tests over session read fields, chunking, runs, usage, capability gaps, LLM transport, beats, recompose and sessions (12 new); alembic upgrade, downgrade -1, upgrade with one head; ruff; version and changelog checks; frontend lint; vitest oversrc/pages/session(481, 4 new). No journey pins the old text.Not done: a render check of the two notes; the prototype page and a coverage file still carry the old wording (design records, not the app).
🤖 Generated with Claude Code