forge 0.14.1

A patch release: three fixes from a 0.13.14 Codex run that took about 11½ hours for four tasks. This page covers what changed since 0.14.0 (PR #150).

Reused finding ids no longer halt as regressions (#144)

Reviewers write their own finding ids (f1, f2, …), and they are never shown the findings an earlier review resolved. A new finding that happened to reuse a resolved id halted the run as regression. Every halt re-invokes the run with a cold reviewer, which numbers from f1 again, so the halts fed each other: nine in a row, about two hours.

• regression now halts only when acceptance goes from green to red, or when a widening that was already resolved is rejected again. Widening ids are built by the runner, so a match there really is the same file.
• A reviewer finding whose id matches a resolved one is an ordinary fix finding and goes to rework. A defect that genuinely comes back is raised again and reworked, and stuck and the backstop still bound a loop that can't fix it.
• Inline runs are unchanged: there the same agent raises and remembers its own findings.

Reviewers no longer have to prove the repository unchanged (#149)

The reviewer contract said the repository "must be byte-for-byte as you found it". Reviewers inventoried every file, saw the runner's own gitignored .forge/ logs change during the review, and reported preservation as unverifiable. That caused three unverified halts.

Reviewers now never write in the repository and leave that check to the orchestrator's fingerprint (working tree, index, HEAD, branch). Gitignored paths are out of scope.

Workers no longer run acceptance (#147)

Standard and complex workers ran the task's acceptance commands, and then the orchestrator ran them again. With a full suite in acceptance, that cost about an hour on a recent eight-task run. Workers now run the test files their change touches, and the orchestrator alone runs acceptance; a failure comes back as a rework lap. Trivial-tier (forge-light) workers still run acceptance, because their batch has no review.

Codex

No hooks/hooks.json change since 0.14.0, so Codex doesn't ask you to re-trust forge's hooks.

Install

claude plugin marketplace update forge
claude plugin update forge@forge        # or: claude plugin install forge@forge

Restart the session to apply. On Codex: codex plugin marketplace add forcetrainer/forge --ref forge--v0.14.1, then codex plugin add forge@forge.