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 app features or behavior, so there are no user-facing changes in this release.

[netlify]

✅ Deploy Preview for fulldev-ui canceled.

Name	Link
🔨 Latest commit	0d29cf3
🔍 Latest deploy log	https://app.netlify.com/projects/fulldev-ui/deploys/6ad132cc353adcb0f2208aaa

[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: b7014577-4cb5-44ee-84b8-5c9f3129658f

📥 Commits

Reviewing files that changed from the base of the PR and between 4ecdd04 and 0d29cf3.

⛔ 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. Your plan provides up to 5 included reviews per hour; 3 remain after this review.

📝 Walkthrough

The packageManager field in package.json now specifies pnpm@12.11.2 instead of pnpm@12.8.1.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to 0d29c

The pnpm update is compatible with the repository’s Node 24 local, CI, and deployment environments, and the lockfile preserves application dependency resolutions. No actionable merge-blocking risk is evident.

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 and concisely describes the main change: aligning the project on pnpm 12.11.2.
Description check		The description directly explains the pnpm version pin, lockfile alignment, preserved dependency graphs, and validation results.

Full details: Docstring Coverage

Explanation

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 files. (1 skipped: 1 unsupported.)

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

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