agent-synclisted

# agent-sync — one project, many agents, no collisions Two planes, and one rule between them: > **Git is the record plane. The cloud is the coordination plane.** > A fact that must survive is written to git first and referenced from the cloud. > A fact about *who is doing what right now* lives in the cloud and expires. No cloud object is ever the only home of a durable fact. Everything below exists to keep that true while several agents write at once. ## Four traps — read these before anything else **1. No backend offers compare-and-swap.** Outline's `documents.update` has `editMode: append|replace|prepend|patch` and **no `lastRevision`**. So a mutable table of claims is a race: two agents read it, both write, the second wins and the first believes it holds a lease it lost. Never model coordination state as a document you rewrite. Append, then read back, and let document order decide. **2. `atomicAppend: false` means you are NOT the lease authority.** If the configured adapter cannot append server-side, say so out loud, fall back to git-file leases, and mark the run `ungated`. A pretended lease is worse than no lease, because the other agent trusts it. **3. Hooks exist only in Claude Code.** On Cursor, Codex and every other agent the skills CLI serves, there is no `PreToolUse` and nothing blocks a guarded edit. Run `guard` yourself before touching a guarded file and record the run as `ungated`. Do not describe the project as protected when it is not. **4. The store re