Setup脚本应支持Git Worktrees

开发团队提出了一项Setup脚本设计方案，以支持Git Worktrees在并行检出环境中的安全运行1。该方案通过为每个Worktree分配唯一标识符及独立的应用端口、数据库名称和测试数据库名称，同时共享单一Docker栈，实现了开发环境的资源隔离1。

Setup脚本的核心职责包括引导工具链、诊断系统依赖、启动共享服务以及生成配置文件1。由于多个Worktree可能并发启动Setup进程，资源注册表的分配需要锁机制来避免冲突1。此外，诊断工具bin/doctor应在Setup流程早期独立运行，以快速识别问题并输出完整的修复步骤1。

该设计还强调了对共享资源的保护。重启共享数据库会影响所有Worktree的运行，因此包含破坏性迁移或服务版本不兼容的分支应使用专用栈1。bin/teardown工具应仅释放相应Worktree的资源，确保其他检出和共享卷不被误删1。

A proposal has been presented for a setup script design that enables Git Worktrees to operate safely in parallel development environments 1. The approach allocates each worktree a unique identifier along with independent ports, database names, and resource names while sharing a single Docker stack, facilitating concurrent development without conflicts 1.

The setup script is designed to perform several critical functions during initialization 1. It bootstraps the toolchain, diagnoses system dependencies, launches shared services, assigns resource identifiers, generates configuration files, and validates dependency accessibility 1. To handle concurrent setup processes, a locking mechanism is required when allocating resources to the registry 1. Additionally, the bin/doctor diagnostic tool should execute early in the setup process and remain independently executable, providing rapid assessment and comprehensive remediation steps 1.

The proposal also addresses operational considerations for maintaining environment stability 1. Restarting the shared database would disrupt all worktrees, so branches with destructive migrations or incompatible service versions should use dedicated stacks 1. Furthermore, the bin/teardown command should release only resources associated with that specific worktree, protecting other checkouts and shared volumes from accidental deletion 1.