test(server): remove exact-duplicate workspace-runtime provisioning test (BLO-21118)

[allyblockcast]

Thinking Path

• Paperclip is the open source app people use to manage AI agents for work.
• The CI suite is the safety net for every PR entering the merge queue.
• server/src/__tests__/workspace-runtime.test.ts had one provisioning-heavy test duplicated byte-for-byte.
• The duplicate copy used a shorter timeout than neighboring provisioning tests, so unrelated PRs could fail under runner contention.
• This pull request removes the duplicate and keeps the surviving test at the timeout used by equivalent provisioning tests.
• The benefit is the same coverage with less flake pressure on unrelated PRs.

Linked Issues or Issue Description

Paperclip issue BLO-21118 tracks CI server-shard flakes caused by the duplicate workspace-runtime provisioning test. The observed failure was on PR #956, run 30954922141, in General tests (server 3/4).

What Changed

• Removed the byte-identical duplicate provisions worktree-local pnpm node_modules instead of reusing base-repo links test from server/src/__tests__/workspace-runtime.test.ts.
• Kept the surviving test and raised its timeout from 30_000 to 120_000, matching nearby real git worktree plus pnpm install provisioning tests.

Verification

CI is the verifying signal: the workspace-runtime test no longer appears twice, and the surviving provisioning-heavy test has the same timeout budget as sibling tests that do equivalent work.

Risks

Low risk. This removes duplicate coverage rather than removing a unique assertion. The timeout change affects only the surviving heavy provisioning test and aligns it with existing neighboring tests.

Model Used

Claude Sonnet 5 (claude-sonnet-5[1m]), agentic coding session with repository inspection and CI log analysis.

Checklist

• I have included a thinking path that traces from project context to this change
• I have specified the model used (with version and capability details)
• I have searched GitHub for duplicate or related PRs and linked them above
• I have either linked an existing issue or described the issue in-PR
• I have considered and documented risks above

[allyblockcast]

🔗 Paperclip issue: BLO-21118
🔗 Paperclip issue: BLO-21953

[allyblockcast]

🔗 Paperclip issue: BLO-21118
🔗 Paperclip issue: BLO-21953

[allyblockcast]

Hey @allyblockcast[bot]! Before this PR can be reviewed, a few things need attention:

Missing or incomplete:

• Missing section: ## Thinking Path
• Missing section: ## What Changed
• Missing section: ## Verification
• Missing section: ## Risks
• Missing section: ## Model Used

Once updated, push a new commit and these checks will re-run automatically.

— commitperclip

[kkroo]

Approved: removes a byte-identical duplicate provisioning test and aligns the surviving heavy test timeout with neighboring provisioning tests, preserving coverage while reducing CI flake pressure.

[allyblockcast]

Ally — Consolidated PR Review

Lenses: pr-review-toolkit (code, tests, comments, errors, types) + gstack/review + native-codex.
Reviewed head: 9aacbfb

Looks good. No Critical or Important issues found.

Strengths

• The removed test duplicated the surviving provisioning setup and all four assertions, so behavioral coverage remains intact.
• The surviving 120_000 timeout matches neighboring provisioning-heavy integration tests and avoids contention-driven flakes without weakening an explicit performance contract.
• The relevant General tests (server 3/4) check passed on this head.

Recommended Action

The analysis is clean, but this PR is authored by app/allyblockcast. The exact head must be reopened under an independent author before the Ally App can provide the gate-authorizing approval.

[allyblockcast]

Ally — Consolidated PR Review

Lenses: pr-review-toolkit (code, tests, comments, errors, types) + gstack/review + native-codex.
Reviewed head: 5d40c9f

Looks good. No Critical or Important issues found.

Strengths

• The removed test duplicated the surviving fixture setup, workspace realization, and all four assertions, so behavioral coverage remains intact.
• Raising the surviving test timeout to 120_000 matches the provisioning-heavy neighboring tests and removes the duplicate's inconsistent 15_000 budget.
• The patch is isolated to test code and does not alter production, SQL, side-effect, type, error-handling, or trust-boundary behavior.

Recommended Action

The analysis is clean, but this PR is authored by app/allyblockcast. The exact head must be reopened under an independent author before the Ally App can provide the gate-authorizing approval.