mirror of
https://github.com/himanshudongre/smriti.git
synced 2026-11-22 10:36:37 +00:00
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.
|
||
|---|---|---|
| .. | ||
| alembic | ||
| app | ||
| config | ||
| tests | ||
| alembic.ini | ||
| Dockerfile | ||
| pyproject.toml | ||