smriti/docs
Bortlesboat 443d611821
Add source turn range tracking to checkpoints
Record which session turns produced each checkpoint under
metadata.source_turn_range at commit time.

The range covers only turns since the session's previous checkpoint,
within the same isolation boundary send_message and the draft endpoint
use: fork-local turns (sequence_number > 0) for forked sessions, and
post-mount turns (sequence_number > history_base_seq) when the commit
request carries mounted_checkpoint_id and history_base_seq.

- SourceTurnRange schema and a defensive parser live in app.schemas
- source_turn_range is exposed on the commit response, the space state
  commit, and lineage checkpoint nodes
- GET /api/v5/lineage/checkpoints/{id}/source-turns returns the turns
- The chat UI passes its mount state when committing

Addresses the open question in DECISIONS.md about tracking which turn
range produced a checkpoint.
2026-10-25 17:41:23 -04:00
..
assets Add real screenshots to README and fix CommitDetailPage diff crash 2026-04-14 15:04:58 +05:30
API.md Add source turn range tracking to checkpoints 2026-10-25 17:41:23 -04:00
DEMO_SCRIPT.md Refresh README assets and add demo recording script 2026-04-14 01:38:25 +05:30