fix(sandbox): run pnpm on native disk

[iamjr15]

Why

A restored project could fail during preparation with EPERM futime because pnpm still executed from Daytona persistent object-store FUSE. The previous npm_config_modules_dir environment value is not a supported pnpm 11 modules-directory boundary, and moving node_modules alone does not stop pnpm from touching project state.

What changed

• execute direct project pnpm and pnpx commands from the existing native-disk source mirror
• synchronize command-produced source changes back transactionally with optimistic conflict detection
• share one lock-aware source mirror between package commands and long-running preview processes
• reject shell-wrapped package managers because they cannot participate safely in the synchronization contract
• keep dependencies, Next cache, and build output off persistent FUSE
• document the package-runtime boundary

No database migration, environment change, or Daytona snapshot rebuild is required.

Verification

• pnpm lint
• pnpm typecheck
• pnpm turbo build --force
• pnpm deadcode
• pnpm architecture:check
• pnpm turbo skills:build
• Python synchronization script syntax check
• local transaction check: successful source commit plus concurrent-write conflict preservation
• production sandbox reproduction confirmed pnpm fails on persistent FUSE and succeeds from the native-disk mirror

Production browser acceptance will run after the protected Cloudflare deployment reaches the exact merged main SHA.

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
cheatcode	Skipped		Aug 9, 2026 9:55am