chore(deps): bump turbo to 2.11.10 - #9903

Summary

• Bumps turbo 2.9.14 → 2.11.10 (root devDependency; the Docker prune stages read the version from it). Schema URL moved to v2-11-10.
• Landing route-group globs. app/(landing)/** was never a valid glob: ( starts a group in Turborepo's glob engine. 2.9.14 skipped the bad glob in turbo query (so landing edits fell into ci:shared and selected every suite) and failed turbo run on any ci:* task outright. 2.11 falls back to "every task affected" for the whole repo. Wrote the folder as a character class, app/[(]landing[)]/**, which matches the literal folder in both affected detection and hashing.
• Task-level affectedTasks needs a future flag in 2.11. Since fix: Include virtual tasks in affected query vercel/turborepo#13805 (2.10.x), affectedTasks matches turbo run --affected: without futureFlags.affectedUsingTaskInputs or futureFlags.filterUsingTasks, it reports every task of an affected package. Enabled filterUsingTasks. CI's --filter calls only name packages, so they select the same tasks (checked with --dry=json). affectedUsingTaskInputs would also work, but it makes turbo prune @sim/app keep apps/desktop, apps/docs, and apps/realtime, because @sim/app tasks depend on pkg#task there, and the app image build relies on desktop being pruned away.
• Prerequisites in affectedTasks.items. 2.11 also lists the runnable prerequisites of affected tasks (reason "required by an affected task"). docs#build is one for ci:e2e-docs-platform, so every backend change would have run the full docs-site suite. ci-plan.gql now picks docs#build with its own task filter, which Turborepo applies before it adds prerequisites. No other task ci-plan.ts reads is a prerequisite of anything.
• Added a ci-changes case for a landing route-group edit (it selects only SEO). It fails with the old glob.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation
• Other: dependency upgrade

Testing

• scripts/ci-changes.test.ts (real git + real Turborepo fixtures): 63/63 pass on 2.11.10. The 62 existing expectations are unchanged. Reverting each fix turns tests red: the glob fallback breaks broadly, the missing flag gives "package is affected" for every ci:* task, and dropping the docs selection fails the two platform-docs cases.
• Full root scripts suite (vitest --config scripts/vitest.config.ts): 43 files, 744 tests pass.
• Ran turbo query on this repo for the last 27 staging commits that don't touch orchestration. 2.9.14 and 2.11.10 selected identical non-prerequisite tasks and the same docs-site decision on every one.
• Cache inputs (turbo run ci:shared ci:e2e-seo build --filter=@sim/app --dry=json): ci:shared, ci:server, and ci:ui hash 0 landing files, while ci:e2e-seo and build hash the whole app/(landing) tree. With the old glob, turbo run on these tasks fails with "Invalid glob" on both versions.
• turbo prune @sim/app --docker gives identical out/json with and without the flag (apps: sim only). check:realtime-prune passes, and bun install --frozen-lockfile is clean.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

🤖 Generated with Claude Code