Rust cache: one record per key, foreign carry, key-identity vector walked #123
Loading…
Reference in a new issue
No description provided.
Delete branch "hands/variants-leaf-key-identity-rs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rust leaf of
variants:follow_up:leaf-key-identity-parity: the cache holds one record per key (a second type at a held key, or at a key a store carries foreign, is refused withSchemaConflictError, memory-only included), a store's unregistered records load as foreign and are carried byte for byte through writes, a key in two stores refuses the pull; walks the key-identity vector merged as6d1684e1(12 rows).Breaking for leaf consumers (not the managed API:
src/is untouched, so apicompat has nothing to check); theCHANGELOGUnreleased "Breaking" entry states it, and per docs/semver-policy.md the next release is a major bump (Rust is consumed by pinned revision).Known open, stated in the CHANGELOG and
docs/write-ownership-map.md: at a key only the store holds, ownership still follows the envelope's claimed id for ids the cache does not register (Soulcut-leaf-key-identity-rs.s3, deferred tovariants:follow_up:lki-rs-declared-ids; it predates this change). redb still keys by (type, key).Soul passes s1 to s4; s4 held (docs delta over s3 code held with the deferred blocker).
🤖 Generated with Claude Code
293ce32a6b8b8d6c15e0