chore(deps): upgrade pi to 1.5.0

Merged
WA
1d ago
+99-90

Summary

  • @earendil-works/pi-ai and @earendil-works/pi-coding-agent 1.0.0 → 1.5.0, and PI_PACKAGE_VERSION to match. pi-coding-agent 1.0–1.4 pin undici exactly at the vulnerable 8.10.2; 1.5.0 pins 8.12.3
  • Regenerated pi-model-catalog.generated.ts from pi-ai 1.5.0. The Pi block stops offering models pi removed (Mistral devstral-medium-2507, devstral-small-2507, mistral-large-2411; NVIDIA nemotron-3-super-120b-a12b; several OpenRouter IDs), and saved Pi blocks on them fail with the existing "model not available" error. The Pi block's default model is unchanged
  • pi-providers.test.ts: the NVIDIA mapping case uses a model both catalogs still list
  • 1.5.0 moves tool-argument validation to @earendil-works/pi-schema (different wording in validation messages shown to the model); none of Sim's tool schemas use TypeBox-only features. Every SDK symbol Sim imports is unchanged, and the CLI flags Sim passes are still supported

Rollout (draft until both images exist)

Create PR, Update PR, Babysit, and Plan run the pi CLI inside a sandbox and require its pi --version to equal PI_PACKAGE_VERSION, so the images switch in the same release as this change:

  • E2B template sim-pi-1-5-0 is built from this branch's build-pi-e2b-template.ts (verified: pi --version = 1.5.0, Bun 1.4.4)
  • Daytona: build sim-pi:<new tag> with build-pi-daytona-snapshot.ts
  • Set E2B_PI_TEMPLATE_ID / DAYTONA_PI_SNAPSHOT_ID to the new images on staging when this merges, and on production in the release that ships it. Never rebuild the existing image names in place; the running app still checks for 1.0.0
  • Local Dev and Review Code use the in-process SDK and do not depend on the images

Type of Change

  • Dependency update / security

Testing

  • Pi suites (executor/handlers/pi, providers/pi-*, scripts/pi-*, blocks/pi-*): 26 files, 206 pass / 1 skipped
  • Built the E2B template and ran pi --version, node, bun, rg, gh in a sandbox from it
  • Lint, type-check, and check:audits run in CI

Checklist

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