release: 0.9.1

[its-miso]

🤖 I have created a release beep boop

0.9.1 (2026-09-17)

Bug Fixes

• bridge: count pipeline-shaped coders toward CODER_AGENT_SLOTS (#338) (eacce68)
• deps: update dependency ruff (0.16.6 → 0.16.7) (#325) (7314727)
• deps: update dependency ruff (0.16.7 → 0.16.8) (#336) (4a2d794)

Chores

• release: sync pyproject version with the release-please manifest and auto-bump it on release (#332) (dd572a8), closes #330
• remove orphaned uv.lock with no tool.uv config or uv install path (#331) (e5235e9), closes #328
• update native loop settings (#339) (afc58e2)

---

This PR was generated with Release Please. See documentation.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M3@https://litellm.jory.dev/v1 (anthropic) — escalated (fast_request_changes)

Recommendation

Approve. This is a Release Please release-cut PR (0.9.0 → 0.9.1). The only code-visible change in the diff is a single-line version bump in pyproject.toml (line 3) and the corresponding bump in .release-please-manifest.json, plus a CHANGELOG entry. No production source under bridge/ is touched by this PR's diff itself; the changelog entries describe PRs that have already been merged and reviewed individually (325, 330/331/332, 336, 338, 339).

Change-by-change findings

• .release-please-manifest.json: manifest version bumped 0.9.0 → 0.9.1. Mechanical release-cut edit.
• CHANGELOG.md: new ## 0.9.1 section appended, listing the prior merged changes that make up the release. Consistent with the compare link in the PR body.
• pyproject.toml: version = "0.9.0" → version = "0.9.1" (line 3). This is the change that PR 332 added a release-version-sync mechanism to keep aligned with the manifest; the two are now consistent (the new test tests/test_release_version_sync.py exists to assert this invariant, and is part of CI).

The runtime dependency in requirements-dev.txt is pinned at ruff==0.16.8, which is what the 0.16.7 → 0.16.8 dep bump (PR 336) left behind. That file is not modified by this PR's diff, which is correct: this PR is the release cut, not the dep bump itself (the bumps were already merged via 325 and 336).

Must-check 1: breaking API changes in updated dependencies

The PR's diff contains no dependency-version lines — only the project's own version string. The dependency bumps referenced in the changelog (ruff 0.16.6 → 0.16.7 and ruff 0.16.7 → 0.16.8) were merged separately via PRs 325 and 336 and reviewed at that time. Those are patch-level releases of a Python linter/formatter that runs in CI (not in production runtime); patch releases of ruff are, by published convention, non-breaking for both its CLI and its Python API surface. No API surfaced by this repository calls into ruff at runtime — it is invoked as a dev tool — so there is no in-process breaking-API surface for this project to be affected by either bump.

The other changelog items (CODER_AGENT_SLOTS counting fix for pipeline-shaped coders in PR 338; release-version sync in PR 332; native loop settings in PR 339; uv.lock removal in PR 331) are application-code fixes/chores, not dependency upgrades, and do not enter the dependency-bump risk surface.

Verdict on breaking-API: none observed. No host-platform/peer-component coupling is in play here (ruff is a dev tool, not a platform); the standard HOST-PLATFORM compatibility-matrix lookup prescribed for coupled bumps does not apply.

Must-check 2: run full test suite after upgrade

CI on the head commit (73cace5…) reached a terminal state of success, and both docker and test checks passed (per the CI Check Results block in the corpus). The test check is what runs the full pytest suite on the merged code; its success is authoritative evidence that the test suite passes against the bumped versions in requirements-dev.txt (ruff 0.16.8) and the released pyproject.toml (0.9.1). No evidence in the corpus contradicts this.

A reviewer-side re-run of the suite is not available to me, but the CI signal is the canonical answer here.

Standards Compliance

The repository's AGENTS.md describes how issues are filed for the autonomous loop (imperative-sentence ask + concrete file paths). That convention governs issue intake, not release-please release cuts, so it does not produce any reviewer-visible obligations for this PR. The PR is generated by Release Please and contains no autonomous-loop issue content to audit.

Tool Harness Findings

The native tool-calling loop issued no tool calls; I reviewed the corpus directly. No additional fetching is needed: this PR is a release cut whose contents (version strings + autogenerated changelog) are visible in full in the diff, and the bumps it carries forward have already been merged and CI-checked individually.

Unknowns / Needs Verification

None. The CI signal is sufficient for a release-cut PR of this shape (version string + manifest + changelog only).

[its-miso]

🤖 Created releases:

• v0.9.1

🌻