[edgehero]

Moves every pi pin from 1.2.0 to 1.3.0 and re-resolves pi's tree in package-lock.json. Prepared by the pi bump workflow; a person reviews, makes it ready and merges it. Nothing here merges on its own (CONST-MERGE-NEVER-AUTOMATIC).

Always opened as a draft. The workflow runs no pi code, so it cannot say whether the bump holds. This pull request's own required checks do: the suite on the new pi, the pinned-assumption and derived-table tests, and the image job's zero-spend smoke. Each red check names what broke.

pi releases in this bump

Read each one before merging. They are linked, not copied here.

• v1.3.0

How to review

• If worker/test/pi-derived.test.mjs is red, run node .github/scripts/pi-derived.mjs --write on this branch and commit the result. Read the hosts it reports added: a new catalog host widens the cost guard (a capped call there is bounded by the output field pi picks for it).
• Every other red test is a pinned assumption about pi that no longer holds. Fix the code or the copy against the new release, never the assertion. A red content-hash test names the pi file that changed: re-verify the copy against it, then move the hash (CLAUDE.md, "pi bumps").
• Fixes go on this branch as signed-off commits. Once it carries one, the workflow never rebuilds it: a newer pi waits, with a comment here, until this pull request is merged or closed. Without fixes, a run for a newer pi, or after the base changed a pin file or the lockfile, rebuilds the branch on the base.

Review checklist (OQ-005)

• Read each release above for a change to what pi reads from the environment, the model or auth wiring, the tools, or the package layout.
• dist/core/sdk.d.ts in the new tarball: createAgentSession's options, how model is obtained, excludeTools still string[].
• EXCLUDABLE_TOOL_NAMES matches allToolNames. If it moved, grow image/runner/src/tools.mjs, docs/exclude-tools.md and triggers.example.json with it, and check pi still ignores an unknown name silently.
• Every catalog host added: which output field pi sends there.
• The human-judged copies (provider steering variables, pricing pins, the admin's width table): their tests name what changed.
• Each red content-hash test: re-verify the copied logic against the named pi file, then update the hash in the same commit.
• The image job's zero-spend smoke passed: a fake key reaches the provider, gets a 401, is metered, and costs $0.
• The release notes name the new pi version.