EnterpriseAI/ClosedCode
1
0
Fork 0
Code Issues Pull Requests Actions 30 Packages Projects Releases Wiki Activity

feat(core): replace instruction checkpoints with value-delta sync (#36254)

Browse Source
This commit is contained in:
Kit Langton
2026-07-10 13:26:25 -04:00
committed by GitHub
parent 768a69bbbd
commit 96a9731947
57 changed files with 2091 additions and 1316 deletions
Download Patch File Download Diff File Expand all files Collapse all files
specs/v2/schema-changelog.md
+14
View File
@@ -2,6 +2,20 @@
Status: **Historical pre-release compatibility ledger.** Older entries retain the names and behavior that were accurate when written; current contracts live in Protocol, Schema, Core, and the indexed specifications.
## 2026-07-10: Replace Instruction Checkpoints With Value Deltas
- Replace rendered `session.instructions.updated.1` prose with `session.instructions.updated.2 { delta }`, where values are SHA-256 hashes and the literal `"removed"` means removal.
- Add the global `instruction_blob` content-addressed value store and rebuildable per-Session `instruction_state` fold cache. Drop `instruction_checkpoint` and its stored baseline, snapshot, and baseline sequence.
- Add an authoritative parent event sequence to `session.forked.2` so forks derive instruction values from the selected parent prefix rather than copying the parent's latest state.
- Keep removed API entries as hidden source tombstones so the next safe boundary can admit and render a revocation. Reject API entry JSON larger than 8KB with a typed HTTP 413 error.
- Render initial instructions and chronological updates from stored values during request assembly. Instruction update prose is no longer a `session_message` row or compaction input; clients display changed keys from the durable delta.
Compatibility:
- Delete pre-beta `session.instructions.updated.1` events and their event-derived System rows instead of carrying a legacy event schema. The next safe boundary establishes one complete v2 delta.
- Existing forks are assigned the sequence reserved by their original projection and their durable event is rewritten to v2 with that cutoff.
- Blob GC is intentionally deferred. A future sync/export boundary must hydrate referenced blobs on the wire and re-hash them on ingestion.
## 2026-07-09: Make Session Input Storage Pending-Only And Rename It To Session Pending
- Rename the `SessionInput` schema namespace to `SessionPending` and the `session_input` table to `session_pending`.