chore: align pnpm on 12.11.2

[silveltman]

Project pins select older pnpm releases even after the machine default is updated. Pin pnpm 12.11.2 and align its package-manager lockfile so local installs and CI select the same version.

Only packageManager fields and the pnpm tool graph change. Application dependency resolutions and configuration dependencies are preserved. Existing installed dependencies remain warm. The store format is independent of the CLI version, so store/v11 is expected.

Validation: manifests differ only in packageManager; application lockfile graphs and configuration dependencies compare equal before/after; frozen offline lockfile-only installation passes for 1 tracked lockfile(s); git diff --check passes. Full application builds and release validation have not run. This PR remains draft.

Summary by CodeRabbit

• Chores
  • Updated the project’s package management tooling. This maintenance change does not alter the app’s features or behavior.

[netlify]

✅ Deploy Preview for silveltman canceled.

Name	Link
🔨 Latest commit	37013f3
🔍 Latest deploy log	https://app.netlify.com/projects/silveltman/deploys/6ad132bcb16111fafefa1405

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Essentials
• Run ID: b9f5cd68-3566-420d-a0e9-bc0fd42c92e7

📥 Commits

Reviewing files that changed from the base of the PR and between e380f6c and 37013f3.

⛔ Files ignored due to path filters: 1

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing: 1

• package.json

Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

📝 Walkthrough

The packageManager declaration in package.json changed from pnpm@12.8.1 to pnpm@12.11.2.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 37013

The pnpm pin matches the lockfile, and inspected Node 24 install paths meet pnpm’s requirements. No actionable merge risk is established; full builds and release validation have not run.

Pre-merge checks: 5

Check name	Status	Explanation
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Title check		The title clearly identifies the pnpm version alignment, which is the main change.
Description check		The description accurately explains the pnpm pin update, lockfile alignment, preserved dependency resolutions, and validation results.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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