release: 0.7.1

[its-miso]

🤖 I have created a release beep boop

0.7.1 (2026-08-23)

Bug Fixes

• bridge: route run_tick's duplicate closures through BridgeRuntime (#207) (e05354d)
• claim: skip only renovate bot issues, log filtered candidates (#219) (32cd164)
• deps: pin msgpack exactly in requirements.txt (#211) (45cf953), closes #172
• env: sync OPTIONAL_VARS registry with env vars the bridge reads (#210) (3d9a369), closes #173
• release: synchronize Python project version (#212) (ac7f596), closes #174
• retry: make human escalation parking idempotent (#217) (c259c4c)
• retry: recover infra-parked workloads (#218) (db7a9f0)
• review-transition: report no-PR Workload verdict to dispatch instead of silent skip:no-pr (#214) (46fcac1), closes #213

---

This PR was generated with Release Please. See documentation.

[its-miso]

🤖 Created releases:

• v0.7.1

🌻

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M2.7@https://litellm.jory.dev/v1 (anthropic) — primary route

PR Review: release: 0.7.1

Summary

This is a bot-generated Release Please release PR that bumps the project version from 0.7.0 to 0.7.1 and updates the CHANGELOG with 8 bug fixes.

Change-by-Change Findings

.release-please-manifest.json

• Version bumped from "0.7.0" to "0.7.1" — expected mechanical change, consistent with prior release (v0.7.0 was similarly bumped from v0.6.32.

CHANGELOG.md

• Prepends a new ## [0.7.1] section documenting 8 bug fixes across bridge, claim, deps, env, release, retry (×2), and review-transition components.
• Each entry references its PR and commit SHA; 4 entries also cite upstream issue closes (PR 172, PR 173, PR 174, PR 213).
• All 8 commits listed in the PR body are present in the CHANGELOG with correct formatting.

Tool Harness Findings

No tool calls were issued; the corpus was reviewed directly without gathering additional evidence.

CI Check Results

Check	State
docker	success
test	success

Both checks passed for commit 16d2b1c.

Standards Compliance

The repository uses Release Please for automated releases (evidenced by .github/workflows/release-please.yaml and the PR body). This PR follows that pattern exactly: version manifest update + CHANGELOG prepend. The AGENTS.md documents the autonomous loop but does not impose additional requirements on release metadata changes.

Recommendation

This is a routine, mechanically-generated release PR. The diff is correct, CI passes, and all documented fixes are traceable to commits already in the repository history. Approve for merge.