Ship the release
Run tests and update changelog until both pass without altering the public API.
Use this when
You are cutting a release and the definition of done is mechanical — tests green and changelog current — but you do not want the agent fixing things by changing the public API along the way.
Done when
✓ Exit requires both success conditions to hold at once. Still check the diff for API-surface changes — the constraint is an instruction, not a type-checker. Keep the actual publish/tag/deploy step for a human.
Why it works
/goal encodes both the success condition (tests pass and changelog updated) and a constraint (do not touch the public API), so the loop can iterate on failures without widening its own scope. --mode ordered makes it get tests green before touching the changelog.
Source: willytop8 ↗graded C · 65/100 — how grades work (Safety Score v2) →
Similar loops
All testing loops →Fix the flaky checkout test
Run checkout tests repeatedly until 20 consecutive passes, logging failure modes and hypotheses after each iteration.
Fix flaky tests, get CI green
Run an agent to identify and fix flaky tests until your CI pipeline passes completely.
Reach a coverage target
Add focused tests for the least-covered files and re-measure each turn until coverage hits 80 percent or the turn cap.