vh/ratatoskr
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

memory: bifrost 1.1.4 (hasattr backstop) supersedes 1.1.3 as the next bump target; folds into provider-maintenance batch

Browse Source
This commit is contained in:
vh
2026-07-16 16:53:47 -07:00
parent 722d6c76de
commit c0d00ccd18
2 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
persistent-memory.d/2026-07-16-bifrost-cursor-conformance.md
+4 -1
View File
@@ -28,7 +28,10 @@ it's only multi-page continuation that's non-conformant. Our contract INV-010 cu
marks the offset cursor **v1-provisional / KNOWN DEVIATION** (commit `8199774`).
TODO when sequenced:
1. Bump pin bifrost `1.1.1 → 1.1.3`.
1. Bump pin bifrost `1.1.1 → 1.1.4` (1.1.4 supersedes 1.1.3: adds the hasattr-gate backstop for the
maintenance verbs — mark_superseded/mark_invalid/patch_many/delete_many/upsert_edges/get_edges_for
degrade to `memory.unsupported_capability` 400 not AttributeError/500 — on top of 1.1.3's scan/cursor
conformance harness. One bump gets both).
2. Replace the offset cursor with the reference snapshot semantics (frozen id-list per
opaque token + `ScanCursorExpired` → 410).
3. Run `run_all(store_factory=..., include_optional=True)` against our SQLite store —