chore(release): sync versions to 0.9.435 [skip release]

[github-actions]

Automated write-back from auto-tag.yml: v0.9.435 was just released, and this PR records that version everywhere the sources carry one —

• [workspace.package].version in Cargo.toml (inherited by every crate)
• the workspace-member entries in Cargo.lock
• packaging/homebrew/stella.rb (build-from-source formula)
• CHANGELOG.md — whatever was under [Unreleased] now sits under [0.9.435]

The workflow approves this PR's parked workflow runs, waits for the required checks, and merges once they are green (#5589). No action is needed unless a check fails.

Summary by Sourcery

Synchronize all tracked project versions and release notes with version 0.9.435.

Build:

• Update the project and Homebrew package metadata to version 0.9.435.

Documentation:

• Move the current unreleased changelog entries into the 0.9.435 release section.

Chores:

• Synchronize workspace and lockfile package versions with the 0.9.435 release.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This automated release write-back records v0.9.433 consistently across the workspace manifest, lockfile, Homebrew formula, and changelog; review primarily for complete and internally consistent version propagation.

File-Level Changes

Change	Details	Files
Synchronize the workspace release version to 0.9.433 and propagate it to dependent lockfile metadata.	Update the inherited workspace package version. Refresh workspace-member package versions in the lockfile.	Cargo.toml Cargo.lock
Update the Homebrew source formula to build the newly released tag.	Point the formula URL at tag v0.9.433. Set the formula version to 0.9.433.	packaging/homebrew/stella.rb
Move the changelog entries from the unreleased section into the 0.9.433 release section.	Rename or promote the Unreleased heading to 0.9.433 while preserving its contents.	CHANGELOG.md

Possibly linked issues

• ci(auto-tag): approve the version-sync PR's parked runs and merge under protection #5672: This automated write-back is the next version-sync PR whose parked-run approval and protected merge issue ci(auto-tag): approve the version-sync PR's parked runs and merge under protection #5672 requires observing.

---

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 assessment

Approved.

---

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

• X
• Mastodon
• LinkedIn
• Facebook

[macanderson]

Adversarial review round 1: the stamp is correct, but v0.9.434 was cut from an older commit than v0.9.433.

This diff matches the v0.9.434 release commit exactly. git diff --stat 0ddda15a 240084db shows only #6547's AGENTS.md and SCR-006 files, and no other manifest carries the version. The one finding is in .github/workflows/auto-tag.yml, the workflow that produced this PR.

This PR will not merge on its own yet. The main is not known-broken hold is failing because main-red issue #6548 ("prose fails on the merged tree") is still open. This diff did not cause that. The body's line "No action is needed unless a check fails" applies now: the PR waits until #6548 closes.

[cursor]

Round 1 has one finding, a P2. No P0 or P1. This pull request stays a version write-back.

The failing check is main is not known-broken. #6548 (main is red: prose fails on the merged tree) is still open. This diff did not cause it. The pull request waits until that issue closes.

The residue issue could not be opened: gh issue create returned 403 Resource not accessible by integration (this token needs issues=write). The definition of done is on the inline reply.

  

_{Sent by Cursor Automation: Fix Review Comments & CI Failures}