chore: update pnpm package lockfile

[abcxff]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[railway-app]

🚅 Deployed to the rivet-pr-5177 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
website	😴 Sleeping (View Logs)	Web	Jun 5, 2026 at 10:46 pm
frontend-cloud	😴 Sleeping (View Logs)	Web	Jun 5, 2026 at 10:46 pm
frontend-inspector	❌ Build Failed (View Logs)	Web	Jun 5, 2026 at 10:41 pm
ladle	✅ Success (View Logs)	Web	Jun 5, 2026 at 10:40 pm
kitchen-sink	❌ Build Failed (View Logs)	Web	Jun 5, 2026 at 10:39 pm
mcp-hub	✅ Success (View Logs)	Web	Jun 5, 2026 at 10:38 pm

[abcxff]

• chore: update pnpm package lockfile #5177 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

PR Review

This PR updates pnpm-lock.yaml only (1 file changed, +357/-2412 lines), removing lockfile entries for ~25 Vercel-specific example variants and consolidating others.

Issues

1. Empty PR description

The PR body is the unmodified template with all checkboxes unchecked. For a change that removes 2,400 lines from the lockfile, some context is needed: why are the Vercel-specific examples being removed? Was this driven by directory deletion, a workspace config change, or a pnpm install regeneration?

2. No corresponding package.json changes

Lockfile changes should be driven by package.json / workspace membership changes. Since only pnpm-lock.yaml changed, it is unclear what triggered the regeneration. The removed example entries (e.g., examples/actor-actions-vercel, examples/ai-agent-vercel, etc.) likely correspond to directories that were already removed or workspace entries cleaned up in a prior commit. If those directories still exist on disk, the lockfile will become inconsistent again on the next pnpm install.

3. examples/agent-os loses agent-os dependencies

The entries for @rivet-dev/agent-os-common, @rivet-dev/agent-os-core, @rivet-dev/agent-os-pi, @rivet-dev/agent-os-sandbox, and sandbox-agent are removed from examples/agent-os, leaving only rivetkit and zod. If examples/agent-os/package.json still references those packages, the lockfile will be incorrect. Please verify the package.json matches the updated lockfile.

Suggestions

• Fill in the PR description: what changed in the repo that required this lockfile update?
• Confirm the removed example directories have actually been deleted from the filesystem (or their package.json entries removed from the workspace) so the lockfile accurately reflects the current workspace state.
• If this is an intentional cleanup of Vercel deployment variants, consider referencing the related commit or PR that removed the directories.