chore(deps): update dependency @earendil-works/pi-coding-agent to v0.85.1

[renovate-fullsend]

This PR contains the following updates:

Package	Change	Age	Confidence
@earendil-works/pi-coding-agent (source)	0.85.0 → 0.85.1

---

Release Notes

earendil-works/pi (@​earendil-works/pi-coding-agent)

v0.85.1

Compare Source

New Features

• GPT-6 Astra — Available through OpenAI API keys and OpenAI Codex subscriptions. See API Keys and OpenAI Codex.

Added

• Added GPT-6 Astra for OpenAI API keys and OpenAI Codex subscriptions.
• Added five-times-faster mouse wheel scrolling while holding Alt in fullscreen mode (#​9166 by @​xl0).

Fixed

• Fixed configurable save keybindings in the model and thinking selectors (#​9149 by @​rwachtler).
• Fixed SDK import failures caused by unintentionally publishing internal experimental code and dependencies in 0.85.0. The experimental client and experimental/plugin subpaths and server/client commands are now source-only through pi-test.sh; the supported local SDK and stdio RPC API are unchanged (#​9132).
• Fixed mouse hover changing selection and recentering autocomplete and settings lists, causing clicks to target a different item.
• Fixed long prompt-cache requests for GPT-5.6+ Responses models to use prompt_cache_options.ttl: "30m" instead of prompt_cache_retention: "24h".

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:21 PM UTC · Completed 3:35 PM UTC

Commit: d28c9a4 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.47

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[fullsend-ai-review]

Risk Assessment: moderate (2/5)

Details

Bot-authored single-file 2-line dependency bump in a protected but historically high-churn, multi-author path; the tiny change footprint and bot authorship keep the composite risk moderate despite the files active churn and fix-commit history — signals unchanged from prior assessment, prior score of 2 preserved.

Previous run

Risk Assessment: moderate (2/5)

Details

Bot-authored single-file 2-line dependency bump in a protected but historically high-churn path; tiny change footprint, zero regression and revert history, and bot authorship keep the composite risk moderate despite the file's active history — signals unchanged from prior assessment, prior score of 2 preserved.

Previous run (2)

Risk Assessment: moderate (2/5)

Details

A bot-authored single-file 2-line dependency bump in a protected but historically high-churn path; tiny change footprint and bot authorship keep composite risk moderate despite the file's active history.

[fullsend-ai-review]

Review

Findings

High

• [protected-path] images/sandbox/Containerfile — This PR modifies images/sandbox/Containerfile, which is under the protected path prefix images/. The PR has no linked issue providing authorization for modifying governance or infrastructure files. Human approval is required for all protected-path changes.

Medium

• [verification gap] images/sandbox/Containerfile:101 — The comment block at lines 98–100 explicitly states "the pi stream parser fixtures must be re-verified when this pin moves." Multiple Go source files echo this requirement: pi_progress.go:260 ("re-checked at the pinned 0.85.0"), pi_run.go:30–31 ("re-check it against the pinned pi's anthropic.json on a bump"), and pi_run.go:602 ("Re-verify it on a PI_VERSION bump"). The PR bumps PI_VERSION from 0.85.0 to 0.85.1 but does not update any verification markers or fixture files.
  Remediation: Run internal/runtime/testdata/pi/regen.sh, internal/runtime/testdata/pi/check-vertex-catalog.sh, and internal/runtime/testdata/pi/jiti-cache-check.sh against the new pin. If fixtures are unchanged, update the "re-checked at" comments from "0.85.0" to "0.85.1".

Low

• [stale comment] images/sandbox/Containerfile:84 — Lines 84–86 describe the 0.85.0 dependency tree structure (@earendil-works/chord → esbuild reachable from dist/experimental/). With the pin now at 0.85.1, this comment describes the previous version's dependency tree, not the current one. The --ignore-scripts flag remains correct regardless.

• [stale-version-reference] docs/contributing/runtime-implementation.md:669 — Contains the literal version string "0.85.0" in prose ("At the pinned 0.85.0 the loader modules cited below..."). The Containerfile now pins PI_VERSION=0.85.1, making this reference stale.
  Remediation: Update the version string from 0.85.0 to 0.85.1 in that sentence.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run

Review

Findings

High

• [protected-path] images/sandbox/Containerfile — This PR modifies images/sandbox/Containerfile, which is under the protected path prefixes images/ and Containerfile. The PR has no linked issue providing authorization for modifying governance or infrastructure files. Human approval is required for all protected-path changes.

Medium

• [verification gap] images/sandbox/Containerfile:101 — The comment block at lines 98–100 explicitly states "the pi stream parser fixtures must be re-verified when this pin moves." Multiple Go source files echo this requirement: pi_progress.go:260 ("re-checked at the pinned 0.85.0"), pi_run.go:30–31 ("re-check it against the pinned pi's anthropic.json on a bump"), and pi_run.go:602 ("Re-verify it on a PI_VERSION bump"). The PR bumps PI_VERSION from 0.85.0 to 0.85.1 but does not update any verification markers or fixture files. While 0.85.1 is a patch release whose release notes do not mention wire format changes, the project's own policy requires this check on every pin move.
  Remediation: Run internal/runtime/testdata/pi/regen.sh, internal/runtime/testdata/pi/check-vertex-catalog.sh, and internal/runtime/testdata/pi/jiti-cache-check.sh against the new pin. If fixtures are unchanged, update the "re-checked at" comments from "0.85.0" to "0.85.1".

Low

• [stale comment] images/sandbox/Containerfile:84 — Lines 84–86 describe the 0.85.0 dependency tree structure (@earendil-works/chord → esbuild reachable from dist/experimental/). The 0.85.1 release notes state "Fixed SDK import failures caused by unintentionally publishing internal experimental code and dependencies in 0.85.0," suggesting this dependency tree may have changed. The --ignore-scripts flag remains correct regardless.

• [stale-version-reference] docs/contributing/runtime-implementation.md:669 — Contains the literal version string "0.85.0" in prose ("At the pinned 0.85.0 the loader modules cited below..."). The Containerfile now pins PI_VERSION=0.85.1, making this reference stale.
  Remediation: Update the version string from 0.85.0 to 0.85.1 in that sentence.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (2)

Review

Findings

High

• [protected-path] images/sandbox/Containerfile — This PR modifies a file under the protected path prefix images/. The PR has no linked issue providing authorization for modifying governance or infrastructure files. Human approval is required for all protected-path changes. The Containerfile comment notes that Renovate is configured to track this ARG via a customManagers entry in renovate.json, but infrastructure image changes require explicit human sign-off regardless of automation source.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:28 AM UTC · Completed 3:47 AM UTC

Commit: 6b0aa8a · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $4.47

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:22 PM UTC · Completed 3:37 PM UTC

Commit: 2817836 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $3.03

[fullsend-ai-review]

Note: The following review comments could not be posted on the diff (GitHub returned 422) and are included here instead:

• images/sandbox/Containerfile (file-level): Line 84 · [low] stale comment

Lines 84-86 describe the 0.85.0 dependency tree structure. With the pin now at 0.85.1, this comment describes the previous versions dependency tree, not the current one. The --ignore-scripts flag remains correct regardless.

[fullsend-ai-review]

See the review comment for full details.

[fullsend-ai-review]

[medium] verification gap

The comment block at lines 98-100 explicitly states the pi stream parser fixtures must be re-verified when this pin moves. Multiple Go source files echo this requirement: pi_progress.go:260 (re-checked at the pinned 0.85.0), pi_run.go:30-31, and pi_run.go:602. The PR bumps PI_VERSION from 0.85.0 to 0.85.1 but does not update any verification markers or fixture files.

Suggested fix: Run internal/runtime/testdata/pi/regen.sh, internal/runtime/testdata/pi/check-vertex-catalog.sh, and internal/runtime/testdata/pi/jiti-cache-check.sh against the new pin. If fixtures are unchanged, update the re-checked at comments from 0.85.0 to 0.85.1.