Skip to content

fix(forge): zero-change tasks -> nochange, not false done/gate=ok (task 7894af1c)#13

Merged
eveselove merged 1 commit into
mainfrom
fix/forge-nochange
Jun 20, 2026
Merged

fix(forge): zero-change tasks -> nochange, not false done/gate=ok (task 7894af1c)#13
eveselove merged 1 commit into
mainfrom
fix/forge-nochange

Conversation

@eveselove

Copy link
Copy Markdown
Owner

Forge dogfood finding: 0-file-change agy runs were reported done/gate=ok (empty commit on green base). _commit_work now returns (sha, has_changes); worker sets status=nochange (terminal-bad, not green) + reconciles gateway failed instead of gate->done. Designed by forge/Opus (bf_d96b7574), applied by hand (forge can't yet commit .py: pre-commit black/ruff whole-repo). task 7894af1c

Designed by forge (agy/Opus, batch bf_d96b7574 / task-3a13769e); applied cleanly
by hand (forge could not commit it: pre-commit black --check blocks the
unformatted repo and ruff --fix mutated ~30 .py incl. dropping a still-used
`import hashlib` — a separate forge-unblock needed for .py tasks).

_commit_work now returns (sha, has_changes). When an agy run yields zero file
changes, the worker sets node status='nochange' (added to ST_TOKEN + TERMINAL_BAD,
NOT in TERMINAL_GOOD) and reconciles the gateway as failed, instead of
empty-commit -> gate-ok -> done. Stops no-op/silently-failed agent runs from being
reported as completed/green in `forge status`. Real-change tasks keep
commit -> gate -> done. Empty commit still created for diffability.

task 7894af1c

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@eveselove eveselove merged commit ef192ac into main Jun 20, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant