chore: update pnpm-policy dev dependencies

[pyramation]

Summary

Self-applied makage update-deps --from <dev-utils>: the only outdated dev-utils-sourced deps here are the policy tools.

• @constructive-io/pnpm-policy 0.2.1 → 0.3.1
• pnpm-policy ^0.2.2 → ^0.4.0

The lockfile diff is large because regenerating with the CI pnpm (10.12.2) rewrites the committed lockfile's quoting and collapses redundant peer-suffixed resolutions; the only dependency-graph change is the two packages above.

pnpm install --frozen-lockfile, pnpm run policy:check, pnpm build, and pnpm test (56 tests) pass locally with pnpm 10.12.2.

Link to Devin session: https://app.devin.ai/sessions/bb89d57636c84c7383305191a303b1d4
Open in Devin Desktop: https://app.devin.ai/desktop/session/bb89d57636c84c7383305191a303b1d4?variant=devin
Requested by: @pyramation

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​constructive-io/​pnpm-policy@​0.3.1
	pnpm-policy@​0.4.0

View full report

[tenki-reviewer]

Review complete. No issues found — approved ✅.

---

This PR updates two dependency pins in the root package.json only. No source code changes, no lockfile changes, and no behavioral impact on the monorepo build. The version bumps are consistent with the existing caret/semver conventions already used across the other devDependencies, and there is no in-repo evidence of a manifest/lockfile disagreement.

_{Reviewed commit: 26a57b5}