[its-miso]

🤖 I have created a release beep boop

0.5.72 (2026-10-23)

Features

• deps: update dependency lucide-react (1.59.0 → 1.60.0) (#1318) (c7dc3ad)
• deps: update dependency lucide-react (1.60.0 → 1.61.0) (#1333) (24e3ccf)
• groomer: expose evidence revision, freshness, and mutation validation in run history (#1067) (#1294) (5758161)
• lifecycle: link authoritative PR merges and expose claim-to-merge timelines (#1203) (#1296) (9f7ac6a)
• observability: export standalone queue, ownership and execution signals (#1252) (#1332) (3656b5c)
• ownership: optional worker renewal capability + fenced claim evidence (#1251) (#1300) (a26e7d7)
• ownership: reconcile abandoned claims with fenced audit-first release (#1254) (#1344) (530876a)
• pr-fix: reactivate on fresh feedback with bounded reconciliation (#1253) (#1304) (a75d8b8)
• rate-limit: throttle mutating endpoints still unthrottled after #1307 (#1323) (#1346) (25db384)

Bug Fixes

• agent-work: checkpoint selects current claim's work via shared ordering rule (#1328) (#1330) (2bcd8cb)
• agent-work: finish selects current claim's work via shared ordering rule (#1331) (#1351) (50e22b6)
• agent-work: narrow stale sweep lease release to the marked claim epoch (#1317) (#1319) (30d6763)
• api: clamp and validate limit query param on list endpoints (#1308) (#1378) (c475b26)
• api: remove deprecated POST /api/repos compatibility endpoint (#1310) (#1382) (b584d4b)
• auth: derive rate-limit keys from the credential, not x-agent-name (#1322) (#1338) (d2366a6)
• automation-sync: persist merged PRs so the lifecycle backfill has an authoritative merge time (#1320) (504c987)
• automation-sync: refresh closed-unmerged PR rows to state closed (#1321) (313bc5a)
• automation-sync: refresh closed-unmerged PR rows to state closed (#1321) (5be26a2)
• deps: update dependency @modelcontextprotocol/sdk (1.32.1 → 1.32.2) (#1380) (f32b639)
• deps: update dependency astro (7.4.0 → 7.4.1) (#1311) (049ec4b)
• deps: update dependency astro (7.4.1 → 7.4.2) (#1339) (2725802)
• deps: update nextjs monorepo (16.4.2 → 16.4.3) (#1364) (3c62510)
• groomer: sanitize repository-context warnings before they reach GroomingRun.contextWarnings (#1353) (5883234), closes #1297
• guard: re-stamp the guard row at commit so a long fenced region cannot look stealable (#1367) (323341c)
• issues: durable idempotent replay of completed issue capacity handoffs (#1262) (#1295) (f1ff7c8)
• ownership: a blocked park owns its row's lease expiry so the stale sweep cannot reclaim it (#1316) (#1335) (bb8530b)
• ownership: align per-issue lease selection with the scan's activity key (#1312) (#1354) (482cafe)
• ownership: fold repo casing in the ownership-inspect pr-fix read (#1357) (#1371) (1227ace)
• ownership: fold repo casing in the ownership-reconciliation pr-fix reads (#1370) (#1373) (65ca72c)
• ownership: renew commits its lease CAS and AgentWork liveness write atomically (#1315) (#1336) (2ceba56)
• pr-fix: fold repo casing in the reconcileStalePrFixItems read (#1372) (#1376) (dd9cb26)
• pr-fix: restrict #940 stale-FIXED reopen to actionable evidence versions (#1303) (#1314) (b589fe4)
• rate-limit: throttle the remaining mutating POST routes (#1307) (#1325) (61c5447)
• review: enable specialist Anthropic effort support (#1352) (e0aa13b)
• stale-sweep: retry arm refuses a same-agent re-claim that postdates the mark (#1359) (#1365) (9178cdb)
• unassign: base the unassign label set on live GitHub labels instead of the cached row (#1377) (6fd6613)
• unassign: fence the remote label write in POST /api/issues/unassign (#1361) (#1368) (60eb0d2)
• unclaim: anchor the remote agent-label release under the per-issue mutation guard (#1367) (9a8800e)
• unclaim: anchor the remote agent-label release under the per-issue mutation guard (#1367) (3b7c6e0)
• unclaim: derive the fenced region budget from the observed label set (#1367) (cb2e15e)
• untriaged: cap the untriaged intake list in the query (#1309) (#1381) (2e9a5d1)

Chores

• deps: lock file maintenance (#1306) (f9a381b)
• dev: add reproducible Node development bootstrap (#1337) (c69e53e)

Refactors

• pr-fix-surfacing: share surface plumbing across blocked/parked/unblock notices (#1358) (c28571c)

---

This PR was generated with Release Please. See documentation.

Superseded by a newer automated review for this pull request.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M3.1-Flash (anthropic) — primary route · pr-reviewer-action v3.7.0

Recommendation: approve the 0.5.72 release metadata update.

Release metadata is internally consistent: the release-please manifest, npm package and lockfile, Helm chart version/appVersion, and changelog all resolve to 0.5.72, matching the release-please configuration.

Claim assessment

• Version claim: held; all six repository impact-scan hits for 0.5.72 agree, and the prior release is v0.5.71.
• Guard re-stamp, groomer history, list-limit clamping, and blocked-park lease claims: not independently verified from this release-only diff; the shared list-limit implementation and relevant historical commits were located, but their behavioral invariants were not re-audited here.

Required checks

• Breaking API changes in updated dependencies: not applicable because this diff changes no dependency version; the separately disclosed deprecated POST /api/repos removal is not dependency-related, while GET /api/repos remains available.
• Full test suite: satisfied by the successful Tests check, with Coverage, integration, build, lint, and typecheck also successful.

Tool Harness Findings

• Repository inspection confirmed release-please wiring, synchronized version locations, the shared parseListLimit implementation, CI coverage, and the retained GET repository endpoint.
• The tool budget was exhausted before linked issue bodies could be fetched, so issue-level acceptance criteria for historical entries were not independently inspected.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M3.1-Flash (anthropic) — primary route · pr-reviewer-action v3.7.0

Partial coverage: required-check coverage is incomplete — this review did not resolve every required check and must not be read as a complete pass.

Findings (1 minor)

Severity	Location	Finding
Minor	CHANGELOG.md:28	The automation-sync refresh fix is listed twice, creating duplicate release-note entries.

Recommendation: approve the 0.5.72 release metadata update.

Required checks: “check for breaking API changes in updated dependencies” is unresolved because the corpus contains no upstream dependency changelogs; “run full test suite after upgrade” is satisfied by the successful Tests check.

Claims: The guard re-stamp claim is supported by the fenced transaction’s explicit opening and commit-time updatedAt writes; the limit-validation claim holds across the located list consumers through bounded parsing; blocked-park lease ownership is unverified because the stale-work implementation path was not located; the dependency claim is reflected by the persisted package-lock versions, although upstream breaking-change details remain unverified.

Tool Harness Findings: Repository reads confirmed consistent0.5.72 values in the release manifest, package manifests, and Helm chart, and that release-please is configured to stamp both chart fields. The GitHub API lookup failed, and the stale-work path lookup failed, leaving the blocked-park claim unverified.

Sources: Changed release files, release-please-config.json, .github/workflows/publish-release.yml, src/lib/query-limit.ts, src/lib/issue-mutation-guard.ts, repository history, and CI results.

Unknowns or Needs Verification: Lint and typecheck were pending, so the normative CI requirement is not yet positively verified; upstream dependency release notes were not available to classify breaking API changes.

Unaddressed required checks

The classifier marked these checks as required for this PR's risk profile, but the review does not resolve or disposition them:

• check for breaking API changes in updated dependencies

Approval published with incomplete coverage: required-check coverage or the tool-loop investigation did not finish. The verdict above is the review's final verdict; the coverage notes remain informational.