feedback creatortrack prod checkout shared agent conflict 20260715T225121

The ~/creatortrack live prod checkout is shared: another agent can be actively working in it (on a non-main branch, with uncommitted changes and a running dev server) at the same time a different agent tries to /ship a separate branch through it.

When running /ship or any prod deploy, always check the prod checkout's current branch and git status for uncommitted changes as part of preflight, before merging/switching branches or running deploy_prod.sh. If it's not on clean main, stop and surface the conflict to Justin rather than switching branches out from under the other agent's work (which risks stranding or clobbering their uncommitted changes).

Why: deploying by force-switching the shared checkout would have clobbered another agent's 109 lines of uncommitted work (fix/guard-task7-verifier branch) and possibly stepped on their live dev server. Justin's own doctrine already requires a human gate on deploy; this adds that deploys must also gate on prod-checkout occupancy, not just human approval.

How to apply: any future /ship or manual deploy through ~/creatortrack should verify (a) branch is clean main, (b) no uncommitted diff, (c) ideally no other agent's session/tmux actively attached, before proceeding. If occupied, offer options: wait for the other agent, ask them to commit/park, or (only with explicit Justin approval) stash their work with a labeled recoverable ref.

[auto-memory session 60d132de-4659-485c-8044-427af0ccce7f, confidence 0.75, mode staged]