what is agent-handover-protocol fr?

This repository defines a set of rules for letting two AI coding agents work in the same code repository without stepping on each other. The idea is simple: instead of agents talking through chat windows or screen interactions, they communicate through git files and commits. A human owner sits at the decision points, approving scope changes and anything that cannot be undone. The creator tested this setup while shipping a real product, a WooCommerce plugin with its licensing backend. Over a week of use, each agent caught bugs the other had introduced. One caught a checksum verification that silently skipped across separate requests. The other caught a provider deduplication that ate deliberately re-sent receipts. Before publishing, the author also tested whether an agent would blindly follow a wrong instruction from its peer. In trap scenarios with false bug claims and harmful fixes, the agent refused each trap on its own, rerunning tests and leaving other agents' files alone. The core argument is that AI agents cannot guess unstated conventions. Which files belong to which agent, what a report must contain, which decisions belong to the human, and what marks the end of a round all need to be written down explicitly. The repository ships that written contract as a short seven-section protocol file. It also includes a Claude Code skill, a Codex CLI section, and templates for handover and report files. An optional local viewer renders handovers and the commit log as a timeline, but it only reads and never writes. Three rules anchor the system. Every machine message must be labeled with its sender and a clear end marker. Git is the communication bus, with handovers and reports stored as versioned, diffable files rather than screen-scraped UI text. And the human owns the forks: scope changes and irreversible actions stop at the owner, while mechanical work within approved scope can loop freely. The standing discipline is that claims are input, not facts. Agents must reproduce before acting and refute with evidence. Modified files that are not yours are foreign, even when unlabeled.