Skip to content

Commit e2ecefd

Browse files
docs(server): qualify which command receipts survive pruning
Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent 0b5b885 commit e2ecefd

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

‎docs/internals/overview.md‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -67,9 +67,10 @@ stream's newest event (high-water marks, stream versions, snapshot sequences), `
6767
of each attempt), and prompt anchors that retained subagent rows reference. A client whose cursor
6868
is below both its thread's newest event and the recorded pruned-through sequence missed pruned
6969
events, so it resumes from a snapshot; an idle thread's cursor resumes without one. Resumes
70-
recheck that sequence after reading the replay, since a pass can prune during the read. Command
70+
recheck that sequence after reading the replay, since a pass can prune during the read. V2 command
7171
receipts stay for idempotency: a retry older than the retained history is still deduplicated,
72-
but its replay comes back without the pruned events.
72+
but its replay comes back without the pruned events. Receipts of imported legacy commands are
73+
removed once their threads are imported.
7374

7475
Retained events must remain decodable on replay. Changing a schema affects old environments at
7576
startup as well as live RPC traffic. Compatibility work must account for stored history, not just

0 commit comments

Comments
 (0)