fix(server): keep long multi-repo setup terminal ids distinct

[LoganRupe]

What Changed

Follow-up to #328, from Copilot's review there.

• A setup terminal id over the 128-character limit now keeps a short hash of the full id instead of being cut off. Two repos whose names differ only near the end still get their own terminals. Before, they could share one, and reopening that shared terminal in the other worktree stopped the first repo's script. Normal-length ids are unchanged.
• A new runner test checks that T3CODE_REPO_ROOT and the per-repo terminal id reach terminalManager.open. feat(server): run the setup script in every repo of a multi-repo worktree #328's server test mocked the runner, so it never covered this.

Why

The collision takes a very long script id or repo name, but when it happens a setup script is killed with no message. The env test closes the coverage gap Copilot pointed out.

[Copilot]

Copilot review overview

🟢 Approval recommended

The focused implementation correctly addresses the collision and includes appropriate regression coverage.

Review effort: Balanced
Findings: None

What changed in this PR

Prevents collisions between long multi-repo setup terminal IDs while preserving existing IDs within the limit.

Changes:

• Adds deterministic hash suffixes when generated IDs exceed 128 characters.
• Verifies per-repo terminal IDs and T3CODE_REPO_ROOT propagation.

File	Description
apps/​server/​src/​project/​ProjectSetupScriptRunner.ts	Generates bounded, collision-resistant setup terminal IDs.
apps/​server/​src/​project/​ProjectSetupScriptRunner.test.ts	Covers multi-repo environment propagation and long-ID distinction.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.