Docs: single-file lock contract, leftover temp file and pair-backup procedures #138
2026-11-12
Retrigger CI (runs 785-789 cancelled at 30:00; one attempt on idle runner)
All checks were successful
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Successful in 22m56s
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Retrigger CI (run 786 was cancelled)
Some checks failed
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Has been cancelled
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Docs: pair backup is per-store consistent only; atomic restore; hold the lock to delete temps; cite the read path
Some checks failed
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Has been cancelled
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Docs: state the single-file lock contract, leftover-temp and pair-backup procedures
Some checks failed
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Has been cancelled
Replace the 'single-writer' wording with what the lock guarantees; drop two stale follow-up claims (Python takes the lock; Rust reads wait); fix the Rust README's 'external lock' advice. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>