Release Aiden Agent 0.58.0

[sambitcreate]

Requested by sbt · project thread

Before: main is at 0.57.0, and everything merged since v0.57.0 is unreleased.

After: merging this publishes v0.58.0 through the Release desktop workflow.

0.58.0 includes the Pi 1.3.0 upgrade (#505), Bot memory stage 1 (#515), the 11-part reliability audit (#520–#530), gzip Remote speech uploads and a compact packaged model catalog (#532), the docs audit (#513), and smaller fixes, including #493–#502, #509–#512, #516–#519 and #531.

How: npm version 0.58.0 --no-git-tag-version updates package.json and package-lock.json. The plan index header and the Pi pin rows now say 0.58.0.

---

Generated by Claude Code

[pullfrog]

✅ No new issues found.

Reviewed changes Reviewed the complete release-metadata diff and its interaction with the existing desktop release workflow.

• Release version: Updates package.json and both root version fields in package-lock.json consistently to 0.58.0, without changing dependencies.
• Plan baseline: Advances docs/plans/README.md to the 0.58.0 release baseline and records the included Pi 1.3.0 pins.
• Validation: All six focused release-selection and consumer-contract tests passed; the checked-in version selects v0.58.0 with publish: true, and that tag does not currently exist. Full hosted CI remains in progress; signed packaging and publication were not run locally.

  ^{｜ View workflow run ｜ Using gpt-6.1-sol ｜ 𝕏}

[very-hermes-bot]

Hermes Review Bot

Confidence: 5

Engine: agy/gemini-3.8-flash-high
Review mode: full
Head: f7bf32cba5fbdd91a58ced74bd69645f1eff9674
Generated: 2026-10-19T04:31:17+00:00
Reviews: 1

Summary

Prepares Aiden Agent for the 0.58.0 desktop release by bumping the application version from 0.57.0 to 0.58.0 in both package.json and package-lock.json. Updates the plan index in docs/plans/README.md to reflect the release baseline against main commit 4eb30658 and annotates the Pi 1.3.0 runtime pin as shipping in 0.58.0. Maintainers should double-check that all changes intended for this release milestone have already landed on main and that the v0.58.0 git tag does not already exist on origin so that the Release desktop workflow publishes cleanly upon merge.

Confidence Score: 5/5

Fully traced and verified against the desktop release workflow contracts, lockfile consistency, and documentation guidelines.

📁 Important Files Changed

• package.json: Increments the declared app version to 0.58.0 (package.json:3), which drives .github/workflows/release.yml tag resolution and installer versioning.
• package-lock.json: Synchronizes root and top-level package descriptor versions to 0.58.0 (package-lock.json:3, package-lock.json:9).
• docs/plans/README.md: Refreshes the plan index status line to 4eb30658 (docs/plans/README.md:5) and notes the Pi 1.3.0 runtime upgrade as shipped in 0.58.0 (docs/plans/README.md:7, docs/plans/README.md:58).

Findings

No findings.

Sequence Diagram

Unchanged or not applicable for this change.

[]

---

Last reviewed commit: f7bf32cba5fb
Reviews (1) · Comment /hermes review to trigger a new review · /hermes review full for full re-review

[sambitcreate]

Electron E2E (3/3) failed on f7bf32c because one test was flaky: tests/e2e/chat-top-bar.spec.ts:327 "Retry chosen after leaving a failed worktree send creates the worktree and starts the reply". It failed on the first attempt and passed on retry, and --fail-on-flaky-tests turned that into a failure (run). This is the known flake tracked in #548. This PR only bumps the version and docs, so it isn't the cause. There's no fix yet: #548 needs a macOS reproduction first. I've re-run the failed jobs once. The release run's macOS gate executes the same spec, so it could hit this flake too.

---

Generated by Claude Code