fix: align pi recovery dependencies (#2423)

[agent-think]

Requested by @aron-cf

Closes #2423

What was wrong

experimental/pi-recovery/package.json still requested @earendil-works/pi-agent-core and @earendil-works/pi-ai at ^0.80.2, while #2423's Pi harness branch uses the published 0.99.2 release. That left the recovery fixture on the older Pi/Serif dependency graph.

What changed

• Bumped both direct Pi dependencies in experimental/pi-recovery/package.json to ^0.99.2, matching the Pi version used by Use published Pi version and clean up the PiHarness options #2423.
• Regenerated pnpm-lock.yaml so the fixture resolves both packages at 0.99.2 and their matching transitive Pi packages.
• Added @earendil-works/* to minimumReleaseAgeExclude, matching Use published Pi version and clean up the PiHarness options #2423's branch; 0.99.2 was published less than the workspace's 24-hour minimum release age when requested.

This is the smallest dependency-only change needed to keep the recovery fixture on the same Pi line as the harness branch.

Testing

• pnpm install --frozen-lockfile — passed
• pnpm --filter agents build — passed
• pnpm --filter @cloudflare/agents-pi-recovery exec tsc --noEmit — passed
• pnpm --filter @cloudflare/agents-pi-recovery test — passed (32 tests)
• pnpm --filter @cloudflare/agents-pi-recovery test:e2e — passed (1 SIGKILL/recovery test; persistence redirected to container-local /temp because the workspace VFS does not support the SQLite locks used by local Wrangler)
• pnpm --filter @cloudflare/agents-pi-recovery exec wrangler deploy --dry-run — passed
• pnpm -w exec oxfmt --check experimental/pi-recovery/package.json pnpm-workspace.yaml pnpm-lock.yaml — passed

Demo

Demo URL (expires after 60 mins): https://pi-recovery.congruous-hat.workers.dev

Click the URL to see the fixture's HTTP control surface (pi-recovery: POST /pi/start | GET /pi/status). It runs this branch's installed pi-recovery fixture with Pi 0.99.2; this dependency-only fixture is private and has no separately packable package.

Context: requested in the review thread on #2423.

🤖 generated by the pr-agent — please review carefully

---

[changeset-bot]

⚠️ No Changeset found

Latest commit: f131aea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[devin-ai-integration]

Devin Review found 2 potential issues.

[devin-ai-integration]

🔍 Lockfile refresh affects other workspaces

The lockfile also changes Hono and Vite/esbuild resolutions used outside the Pi fixture. Review whether those unrelated upgrades belong in this dependency-only PR.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🟨 Release-age safeguard bypassed for all Pi packages

When Pi dependencies resolve anew, minimumReleaseAgeExclude lets any @earendil-works release bypass the 24-hour wait. Future installs can select unvetted releases across the entire scope.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[agent-think]

🟢 agents import sizes: 1 entry point changed, no growth

	Entry point	Exports	Largest gzip change	Size now
🟢	agents/vite	1 resized	-121.3 KiB (-28.96%)	297.6 KiB

Changed exports (1)

	Import	Gzip change	Size now
🟢	agents/vite#default	-121.3 KiB (-28.96%)	297.6 KiB

How this works

Each runtime export is bundled on its own, minified, and gzipped. Changes smaller than 100 B, or smaller than 1% and 1 KiB, are ignored. Growth over 10% or 5 KiB is marked 🔴. This report is informational and does not fail CI. The workflow artifact contains every measurement.

_{Compared 6e1c3467 → f131aea1 · workflow run · reported by agent-think[bot]}