Unless I misunderstand something but why not just roll a couple of helper shell scripts that create a new git worktree for you, copy over a local .env file (or

Unless I misunderstand something but why not just roll a couple of helper shell scripts that create a new git worktree for you, copy over a local .env file (or any other config file) and populate it with ports/variables that are unique across all worktrees (to avoid collisions if you're on localhost, but you could also do this with Docker) and a helper script for tearing down a worktree after you've merged the changes back into main. I'm even supplying unique chrome debug ports and unique temp user data dirs for isolated automated testing in chrome via chrome devtools mcp. Like, I'm not sure why an external library/tool is needed for this.