chore: enforce pnpm 11

[Sheraff]

Adds engines.pnpm >=11.0.0 to TanStack/cli.

Scenario	Result
pnpm@11+ install	Allowed
pnpm@11+ run ...	Allowed
pnpm@9 install	Blocked by engines.pnpm
pnpm@9 run ...	Blocked by engines.pnpm
pnpm@10 install with default pnpm version management	Usually hands off to packageManager and runs as the declared pnpm version
pnpm@10 run ... with default pnpm version management	Usually hands off to packageManager and runs as the declared pnpm version
pnpm@10 install with version handoff disabled	Blocked by engines.pnpm
pnpm@10 run ... with version handoff disabled	Blocked by engines.pnpm
pnpm@9/10 list	Not blocked
pnpm@9/10 exec ...	Not blocked

Field	What It Does
packageManager	Helps tools/newer pnpm select or hand off to the declared pnpm version
engines.pnpm: ">=11.0.0"	Fails important project workflows when an older pnpm is actually executing them
engines.pnpm	Does not intercept every pnpm subcommand

Summary by CodeRabbit

• Chores
  • Updated project requirements to specify pnpm version 11.0.0 or higher as the minimum supported package manager for installation and development.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b7103291-3577-4c62-95be-56a0b98729ea

📥 Commits

Reviewing files that changed from the base of the PR and between efb411e and dd94d3f.

📒 Files selected for processing (1)

• package.json

---

📝 Walkthrough

Walkthrough

This PR adds a package manager version constraint to package.json, specifying that the project requires pnpm version 11.0.0 or higher via the engines field. No other package configuration was modified.

Changes

Package Configuration

Layer / File(s)	Summary
pnpm version constraint package.json	An engines block declares pnpm >= 11.0.0 as the minimum supported version.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit hops through package lands,
Where pnpm must be eleven or more,
The engines field now understands,
Version constraints at the door! 🐰

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: enforce pnpm 11' accurately reflects the main change: adding an engines requirement for pnpm >= 11.0.0 to package.json.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}