I've been doing similar for many scripts within project workflows... I've started calling the directory in question ./run/ by convention, so I type run/scriptname to run stuff... I've got bash (extnsionless) and powershell (ps1) scripts in place on my work project).

I'll also lean into docker+compose usage for any background services, and even development in order to reduce the running footprint switching projects.

How amazing that git launched this way ahead of it becoming the ubiquitous choice for AI native development workflows

To the blog post author commenting here: Your comment got flagged / dead, probably because it reads as AI generated so it won't be visible to anyone.

Author here. Parallel worktrees showed me where Git’s isolation ends. Files stayed separate; ports, databases, cache keys, queues, and Compose resources did not. We now share compatible services and isolate names per worktree. Which shared resource has been hardest for your team to isolate, and why?