Mario Zechner 6c2fd73b0c feat(durable): deferred storage of throttled commits ... A commit may be marked deferrable ({ persistence: { kind: "deferred", withinMs? } }) on Session, Conversation, TaskRuntime and a tool's api.commit. When every write changes an existing conversation document with history "latest" and fork "initial", it is adopted in memory and shown to watches at once, and stored with the next commit that reads or writes the document, before the document leaves memory, at close, or within withinMs (default settings.progress.persistWithinMs, 1000 ms). The generation partial throttle and the tool output throttle use it. subscribeCommits() gets these commits only once stored, with exactly what was stored; internal observers get memory-only publications. Spec §1/§13 changed, new §4.1. 32 streams over SQLite: storage transactions 562/s -> 99/s, disk 14.3 -> 4.9 MB/s, CPU 29% -> 22% of one core. A crash loses up to about 1 s of streamed content.		2026-10-24 17:49:30 +00:00
..
spec.md	feat(durable): deferred storage of throttled commits	2026-10-24 17:49:30 +00:00