release: 0.5.66

[its-miso]

🤖 I have created a release beep boop

0.5.66 (2026-09-27)

Features

• groomer: recheck saved empty searches for freshness (#1114) (ecddbec)
• queue: honor native GitHub blocked_by dependencies (#1095) (47c7353)

Bug Fixes

• groomer: ground already_done closes in the issue's own acceptance (#1100) (124b5b2), closes #1099
• pr-fix: cap fix attempts, not evidence, and always baseline fresh attempts (#1107) (babe44b)
• pr-fix: keep the item URL as the PR URL when CI evidence re-enqueues it (#1117) (f94ba28)
• pr-fix: retract needs-human on every exit from BLOCKED (#1108) (0bbdaf7), closes #1105
• pr-fix: stale PR-fix items in archived repos and refuse requeuing them (#1109) (cadc05c)

Documentation

• groomer: define close proof policy (#1112) (7c0348e)

---

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) — primary route

Recommendation: approve

This is an automated Release Please release-PR that only bumps the project version from 0.5.65 to 0.5.66 and appends the corresponding changelog entry. It does not modify any application code, dependencies, or build configuration.

Change-by-change findings

• .release-please-manifest.json — bumps "version" from 0.5.65 to 0.5.66. Single-line release-please bookkeeping. No behavioral impact.
• CHANGELOG.md — appends a 0.5.66 (2026-09-27) section listing the features, bug fixes, and docs changes that landed since 0.5.65 (blocked_by dependencies, close-grounding for already_done, PR-fix attempt capping, needs-human retraction, archived-repo PR-fix requeue refusal, saved empty-search recheck, close proof policy doc). These are summaries of commits already present in main; the diff itself only adds prose.
• charts/dispatch/Chart.yaml — bumps Helm chart version and appVersion from 0.5.65 to 0.5.66. Standard chart-release convention.
• package-lock.json — only the package version field changes (0.5.65 → 0.5.66). No dependency versions, lockfile integrity entries, or transitive resolutions change.
• package.json — only the top-level "version" field changes (0.5.65 → 0.5.66). No dependencies, devDependencies, engines, or scripts are touched.

Must-check responses

• check for breaking API changes in updated dependencies — Not applicable. The diff does not modify any dependency. package.json and package-lock.json show only the project-version field changing; no @dnd-kit/*, Prisma, Next.js, vitest, or other pinned dependency entries are bumped, and no peer/engine constraints shift. There is therefore no API surface to re-evaluate.
• run full test suite after upgrade — Verified out-of-band via CI. The CI status set for the release-PR head (0c3d83b) reports Tests, Coverage, Database integration, Build, Typecheck, Lint, Workflow lint, npm audit, Docker Build, Docker Build (MCP), Database migrations, and smoke all as success, which is a stronger signal than a single test-suite invocation and is the appropriate evidence for a release-PR that introduces no code change of its own.

Sources

• PR body (release-please generated notes) and the diff itself.
• CI status API results for 0c3d83b346a49ee90f5176b3b91f5aa6a2180d07.
• Repository Impact Scan / Repository History, which confirm the version bump is the only artifact of this delta and that the cited issue numbers map to commits already merged to main.

Standards Compliance

• Lint/typecheck blocks CI; must pass — CI shows both Lint and Typecheck checks as success for the release head, satisfying this AGENTS.md normative requirement.
• Token secrecy — the delta adds no logging, no env files, and no new code paths; DISPATCH_AGENT_TOKEN and GITHUB_TOKEN remain untouched by this diff, so the no-logging / no-persist rule is preserved.
• Versioning, Helm chart versioning, and release-process conventions are consistent with AGENTS.md's release/PR conventions.

Unknowns or Needs Verification

• The GitHub compare endpoint for v0.5.65...v0.5.66 returned no structured metadata at fetch time, so I could not enumerate the per-PR file list beyond what the PR body and diff already cover. Given the diff's contents (version + changelog only) and the green CI matrix, this gap does not affect the verdict, but it is noted for completeness.

[its-miso]

🤖 Created releases:

• v0.5.66

🌻