When two or more AI coding sessions share a repository concurrently — or an AI session and a human work in parallel — git is the coordination protocol. Sessions share files and history, not state. Load when spawning a second session on a live repo, when uncommitted changes appear that you didn't mak
When two or more AI coding sessions share a repository concurrently — or an AI session and a human work in parallel — git is the coordination protocol. Sessions share files and history, not state. Load when spawning a second session on a live repo, when uncommitted changes appear that you didn't make, when a `git stash` is tempting in a multi-session repo, or when cloud routines need to know rules