isolatelisted

# Isolate One tree per task. The failure this prevents has no error message: two agents in one working copy overwrite each other's edits, and git reports nothing, because from git's side the second write is just the current state of the file. ## Before creating anything, check nobody is already on it ```bash git ls-remote --heads origin gh pr list --state all --limit 30 ``` Two commands, seconds each. A branch that already exists under the name you were about to create is the cheapest possible warning that someone is on the same problem. Read that branch before renaming around it, and if the work is duplicated keep the better implementation rather than yours. **But a branch name is not evidence about its content.** Test whether its commit is an ancestor of the default branch, and run a control so a uniform answer cannot pass as a finding: ```bash git merge-base --is-ancestor origin/<branch> origin/main # exit 0 = already landed git merge-base --is-ancestor HEAD origin/main # control, expect 1 ``` `[measured 2026-09-02]` a branch named `fix/always-on-without-a-trigger` was the only match for a search about skill triggers. It had already landed, and its tip commit was a telemetry path fix. The name matched the search and nothing else did. ### Neither command above can see unpushed work Both read the REMOTE. Where commits stay local until someone says push, which is the default in this estate, the normal state of work in progress is invisible to both. So