Developer rebuilds entire automation workflow after rogue bot switched git branch mid-deploy

A developer discovered a critical flaw in their automation setup when a scheduled bot silently switched git branches while a deploy was still running, causing the wrong build to land on the device. The root cause was multiple automated workflows sharing the same working directory, creating collisions when two processes ran simultaneously or overlapped with manual work. The fix involved adopting git worktree, a feature available since git 2.5 that lets each automation operate in its own isolated folder while sharing a single .git object store. The developer rebuilt all 10 automation workflows around this approach, ensuring no bot can ever interfere with the directory a human is actively using. Each workflow now follows a five-step pattern: trigger, isolate, work, verify, and notify without committing, keeping human judgment as the final step.