A write, a delete and a rename MUST check what they expect (no object, the object at a revision, or anything) against the file at the tip they read, and a branch that moved while the change was made MUST be read again and the change checked again, so that two writers of different files both succeed, two writers who expect the same revision of a file cannot both succeed, and the commit of another writer is never overwritten; a branch that keeps moving MUST end as a retryable unavailable after the tries.
Enforced (check): .github: cd commons/anyfs-git && bun run verify — suite/ref.test.ts
Proved by: anyfs-git/suite/ref.test.ts
Written in: anyfs-git/src/physical/ref/branch.ts, anyfs-git/src/physical/ref/mod.ts
Tests: passed: suite/ref.test.ts writers are decided by what they expect: two who expect the same revision cannot both win,