release: 0.59.2

[blooop]

Ships #666, which is on main but in no release.

#665 merged first and Auto-publish tagged and published v0.59.1 from it. #666 merged four minutes later with its own release: 0.59.1 commit. The tag already existed, so Auto-publish skipped it, and the published 0.59.1 still asks for the agent, model and effort on aid <workspace>. git merge-base --is-ancestor ed7ca66 v0.59.1 fails.

This moves the #666 changelog entry under 0.59.2 and bumps Cargo.toml, Cargo.lock, the README badge and the dl --version transcript.

Checked locally: cargo test --locked -p aid, cargo clippy --locked --all-targets -- -D warnings, cargo fmt --check all pass.

🤖 Generated with Claude Code

Summary by Sourcery

Release version 0.59.2 with the workspace launch fix that was omitted from 0.59.1.

Bug Fixes:

• Restore direct-to-editor behavior for workspace-specific promptless launches with aid <workspace>.
• Move the workspace launch fix into the 0.59.2 changelog entry so it is included in the release notes.

Build:

• Bump the Rust workspace and lockfile versions to 0.59.2.

Documentation:

• Update the README release badge and dl --version example to 0.59.2.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This release-only PR publishes the post-0.59.1 #666 fix as 0.59.2 by relocating its changelog entry and synchronizing the Cargo version, lockfile, README badge, and CLI version transcript; no functional source code changes are included.

File-Level Changes

Change	Details	Files
Correct the release metadata and changelog for the previously omitted workspace-launch fix.	Move the fix: aid <workspace> goes straight to the prompt editor again #666 fix entry from 0.59.1 to a new 0.59.2 section dated 2026-10-01. Bump the workspace package version and lockfile metadata to 0.59.2. Update the Conda badge and documented dl --version output to 0.59.2.	CHANGELOG.md rust/Cargo.toml rust/Cargo.lock README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.42%. Comparing base (db5fec1) to head (3616eb0).

Additional details and impacted files

Flag	Coverage Δ
python	42.98% <ø> (ø)
rust	94.64% <ø> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
shipped code (rust)	94.64% <ø> (-0.03%)	⬇️
harness and tooling (python)	42.98% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.