samiandClaude Opus 5.5 a15d301b53 kv-sync: saturate seq increments instead of overflowing at u64::MAX ...

next_version() and the two merge paths in the engine computed max(seq) + 1 on seq
values read from decrypted plaintext. A version carrying seq = u64::MAX panicked in
debug builds and wrapped to 0 in release, so the next save looked like a replay to
every other device. Found while checking fuzz/item_replay; needs an authentic
plaintext, so low severity.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-17 00:52:50 +09:00

..

src

kv-sync: saturate seq increments instead of overflowing at u64::MAX

2026-10-17 00:52:50 +09:00

tests

kv-sync: authenticated tombstones (sealed {id, seq, deleted: true})

2026-10-16 11:34:08 +09:00

Cargo.toml

M1: persistent vault, local unlock key, sync client, test vectors

2026-10-15 21:52:14 +09:00