In shared checkouts, prove your deploy landed
When several AIs share code, 'deploy succeeded' doesn't mean your change is the one live.
how it works
Concurrent sessions deploy the same Worker; probe production after deploy; dirty files and git authorship can't identify an owner, which motivated worktree-per-session.
Technique: A pattern or hard-won lesson, written down so it isn't learned twice.
The code for this one lives in a private repo. This page explains the idea so you can build your own.