deps(deps): bump github.com/sky-valley/pi from 0.84.19 to 0.85.21

[dependabot]

Bumps github.com/sky-valley/pi from 0.84.19 to 0.85.21.

Changelog

Sourced from github.com/sky-valley/pi's changelog.

v0.85.21

Upstream sync 744a94d7d → 9767ba275 (pi 0.85.1). 19 first-parent changes, no merge-smuggled commits: 3 ports, 2 port-but-catalog (the release commits), 1 port-but-queued, 13 n/a, 0 decide. Two release tags crossed (v0.85.0 and v0.85.1), so the catalog was regenerated by executing JSON.stringify(MODELS) against dist/models.generated.js on both npm builds rather than by reading git, and endpoint-pinned at both ends — the outgoing catalog is byte-identical to a fresh 0.84.4 derivation and the incoming one to a fresh 0.85.1 derivation, so the committed diff is provably the upstream release diff. It drains the catalog-only queue 7→0 (all seven queued deltas plus this cycle's gpt-6-astra generator half are ancestors of the v0.85.1 tag). All four recorded regen tripwires were checked: allowedFallbackModels entries still carry provider so billing is unaffected, 4e69b0c28's OpenRouter reroute is live (15 anthropic/* models on anthropic-messages, :batch correctly excluded), 21 surviving models changed thinkingLevelMap, and grok-build-0.1 is gone.

Behaviour: strict sampling is now the default for built-in tools. Upstream deleted PREFER_STRICT_TOOL_SAMPLING and the PI_EXPERIMENTAL gate that fed it, so read, bash, powershell, edit and write carry constrainedSampling: {json_schema, prefer} on every request rather than only under an opt-in env var; grep, find and ls stay unconstrained. This changes the tool definitions every request carries, not just experimental ones. AreExperimentalFeaturesEnabled survives as published SDK surface even though its only port-side consumer went with the gate.

Also: GPT-5.6+ models (anything with supportsExplicitPromptCacheMode) now own long prompt-cache retention through prompt_cache_options: {ttl: "30m"} and must not also send prompt_cache_retention: "24h", which stays the older models' spelling — the port had been emitting both. And defaultModelPerProvider["radius"] moves auto→balanced, the split-by-hunk site the ledger flags as having caused a missed port twice; it fired correctly this time.

One pre-existing parity bug was found by the cycle's own review and fixed rather than deferred: validThinkingLevels carried six of pi's seven VALID_THINKING_LEVELS, missing max. The port had taken the ai-side half of upstream fbdd46389 and missed the resolver-side list, so --model anthropic/claude-opus-4-8:max did not parse :max as a thinking suffix — it resolved to a synthesized custom model whose id was literally claude-opus-4-8:max, with a spurious "not found for provider" warning. The covering test looped over six levels where upstream loops over seven, so it pinned the omission instead of catching it; and because it only walked the custom-id path — where a missing level is indistinguishable from a real custom id — it could not have caught this at all. Both were fixed.

Breaking change. coding.GetExperimentalToolSampling() is removed. It returned the strict-sampling config only when PI_EXPERIMENTAL=1 and nil otherwise; upstream deleted both it and the constant behind it, and the mirror ruling is that upstream deletes, we delete — no shim, no deprecation window. Migration: if you called it to mirror the gate, drop the call, because the

... (truncated)

Commits

• e204bf1 docs: advance the pin to 9767ba275, npm pi-ai 0.85.1
• 0a754df fix(coding): ":max" is a valid thinking level (upstream fbdd46389, missed half)
• d28e455 difftest: re-pin to 9767ba275 / pi-ai 0.85.1 and return the whole suite to dist
• f23dce4 catalog: regenerate models_catalog.json from pi-ai 0.85.1
• 34d1e5d port(ai): GPT-5.6+ models express long cache retention via prompt_cache_optio...
• 57b2334 port(coding): prefer strict sampling for built-in tools by default (upstream ...
• 2abe0e2 port(coding): default Radius model is balanced, not auto (upstream 9767ba275)
• cb254e1 docs: advance the pin to 744a94d7d
• 6d8eecd port(coding): map signal-killed processes to non-zero exit codes (upstream c2...
• ec296bf port(ai): restore stream compatibility (upstream 8b5899dce)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.