chore: migrate pnpm config from package.json to pnpm-workspace.yaml

[alx-xo]

Summary

pnpm v10 no longer reads the "pnpm" field in package.json, emitting noisy [WARN] on every run (shows in agent runs as well)

• overrides migrated recharts to pnpm-workspace.yaml
• ignoredBuiltDependencies was migrated to pnpm-workspace.yaml
• Removed override for react-is, and removed unused dep react-is as wasn't used

Root cause

pnpm v10 deprecated the package.json#pnpm config block in favour of pnpm-workspace.yaml. The existing glob override was already in the right place; only overrides and ignoredBuiltDependencies needed moving.

Test plan

• pnpm install runs with no [WARN] about ignored pnpm fields
• Lock file resolves overrides correctly

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
gram-docs-redirect	Ready	Preview, Comment	May 20, 2026 6:01pm

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

_{Tip: disable this comment in your organization's Code Review settings.}

[linear-code]

AGE-2436

[changeset-bot]

⚠️ No Changeset found

Latest commit: c4f340e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[disintegrator]

Can we confirm that these overrides are still needed before merging?

[alx-xo]

Good question!

• "react-is" was not being used at all. Its use case is for tests. Have removed it from overrides and package.json
• "recharts" is used, but is listed in devDeps as the same version so didn't need to have an override listing

Actually turns out the override for recharts was needed to prevent another dep from resolving Recharts to v3