chore: move to pnpm 12.4.2

[altaywtf]

Problem

The repo pinned an older pnpm; 12.4.2 is current.

Solution

Bump packageManager. packageManagerDependencies tracks pnpm itself, so the lockfile diff is the pinned pnpm exe entries and nothing else — no application dependency re-resolves and lockfileVersion stays 9.0.

Proof

pnpm run verify passed.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-19T14:02:52.610428Z	7191835	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Copilot]

Copilot review overview

🟢 Approval recommended

The changes are a straightforward pnpm pin bump with lockfile updates consistent with the stated intent and no code-path impact.

Review effort: Lite
Findings: None

What changed in this PR

Updates this repo’s pinned package manager to a newer pnpm release, keeping the project’s package-manager pinning consistent via packageManager and lockfile packageManagerDependencies.

Changes:

• Bumped package.json packageManager from pnpm@12.0.0 to pnpm@12.4.2.
• Updated pnpm-lock.yaml packageManagerDependencies and refreshed the pinned pnpm executable entries accordingly.

File	Description
package.json	Updates the pinned pnpm version via the packageManager field.
pnpm-lock.yaml	Refreshes the lockfile’s pnpm pin (packageManagerDependencies) and the corresponding pnpm exe package entries.

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.