Upgrading pnpm needs pnpm-workspace.yaml

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Target branch: unstable

Observed behavior

After commit a3e678bd6 ("Add minReleaseAge to pnpm settings to reduce likelihood of supply chain compromises"), pnpm install and all pnpm run commands fail locally with:

ERROR  packages field missing or empty
For help, run: pnpm help install

This affects every pnpm command - including pnpm install, pnpm run test, and pnpm run devserver.

Errors and logs

$ pnpm install
 ERROR  packages field missing or empty
For help, run: pnpm help install

$ pnpm run test
 ERROR  packages field missing or empty
For help, run: pnpm help run

Expected behavior

pnpm install completes successfully and all pnpm run scripts work, as they did before pnpm-workspace.yaml was introduced.

User-facing consequences

Any contributor who pulls the latest unstable and tries to set up or run the frontend locally is completely blocked. CI still passes because pnpm/action-setup@v5 in GitHub Actions handles the workspace config differently, so the breakage isn't visible there.

Steps to reproduce

1. Clone the repo and check out unstable
2. Run pnpm install
3. See ERROR packages field missing or empty

Context

OS: macOS (confirmed), likely affects all platforms

AI usage

Used Claude Code to diagnose the root cause from error logs and trace it to the missing packages field. I verified the fix myself by running pnpm install locally before filing.

Inspect pnpm-workspace.yaml and the changes from commit a3e678bd6. Reproduce the failure with pnpm install, then verify the workspace configuration by running pnpm install and the affected pnpm run commands, including test and devserver. Done means installation and the listed scripts complete without the packages-field error.