chore(pi): upgrade agent to 1.0.0 - #8585

Summary

Upgrade the embedded Pi SDK and sandbox recipes from 0.80.10 to exact 1.0.0 while preserving the existing Local Dev/Review Code SDK and Plan/Create PR/Update PR/Babysit CLI architecture.

• Adapt the sealed resource loader to the new prompt-source interface and explicitly disable cache warming in embedded sessions and private CLI settings.
• Regenerate the installed chat-model catalog and keep Sim's provider/model filtering. Saved workflows using models removed by Pi fail before credential resolution or remote setup and ask users to choose a supported Pi model; there are no substitutions or legacy definitions.
• Check the sandbox CLI version before every agent invocation. Existing Pi images must be rebuilt or updated to 1.0.0 before these cloud modes can run. Node requirements and sandbox sizing stay unchanged.
• Keep the test diff focused on removed-model handling, stale sandbox runtime rejection, and private CLI settings. Reuse existing backend, credential, event, and search coverage. No new public block fields, operations, outputs, or migrations.

Live Pi testing and cloud image rollout deferred.

Type of Change

• Breaking change
• Other: dependency upgrade

Testing

• Focused Pi, search, provider/model-option, and sandbox tests pass; regression cases were demonstrated failing before fixes or with their corresponding guards removed.
• Root bun run test passes: 19 workspace tasks, including 34,648 passing app tests (25 existing skips).
• Root workspace type checking, lint, all 58 audits, block-registry validation against origin/staging, docs-manifest checks, and whitespace checks pass.
• Pi catalog generation is byte-identical on repeat. Required in-repo artifact generation completed, and unrelated generated sandbox-bundle changes were excluded.
• Offline checks against the real installed SDK/CLI passed using a loopback provider; validation tooling and reports remain outside Git.
• Production Next standalone build passes. A copied artifact outside the checkout executes a real offline SDK tool cycle with the packaged 1.0.0 runtime and assets.
• Trigger.dev's deploy bundler completes without deployment or cloud API calls; its worker package manifest pins both Pi dependencies to 1.0.0. Existing externalization is retained.

Remaining acceptance/rollout: build versioned E2B and Daytona images, verify CLI 1.0.0, exercise both providers and every Pi mode with disposable resources, check real model access/cancellation/usage/cost/search/Babysit continuation, and coordinate app/worker image configuration with rollback references before deployment.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)