A worktree-per-agent workflow for parallel development
Running several agents against one repo turns every shared resource into a race. A worktree per agent is the cheapest fix that actually holds — here is the setup, the port math, and the one teardown step that bites you if you skip it.
Why worktrees
One checkout per agent means no fighting over the working tree, the dev server port, or the database. This is a placeholder body — the real post is authored in a later phase.