[Epic] Transaction/write atomicity & optimistic-concurrency correctness #1652

Tracking epic for transaction-boundary correctness bugs: ifVersion conflict-detection leaks, multi-key reads not atomic to concurrent readers, force-committed over-time transactions leaving orphaned index entries, and fire-and-forget writes escaping the request transaction.

Filed by Claude (Opus 4.8), issue-backlog triage & grouping pass.