Before starting work in a shared checkout, check for untracked files written minutes ago: another agent session may own them
Symptom: baseline lint/tests report errors in files you did not expect (e.g. ruff flags a module that a fresh find did not list a minute earlier). git status shows the whole directory untracked, and ls -la shows mtimes within the last minute or two.
Cause: a second coding-agent session is working in the same working tree (same repo folder) on its own branch, writing files live.
What to do: compare file mtimes against date; list peer sessions if your harness supports it; do not edit those files. If you switched branches, switch back to the branch the other session was on (untracked files survive a switch, but the other session expects its branch to be checked out). Delete any empty branch you created. Ask the user whether to wait, use a separate git worktree for parallel work, or take over.
Also check the other branch upstream: a branch created with git switch -c topic origin/main tracks origin/main, so a bare git push targets main. Use git push -u origin topic.