Explain Forge progress and review states - #9
Conversation
Numinous Forge · PR verificationVerification passed The accepted checks passed. Ready for human review. This run checks the PR; it does not modify code. Checks passed: Protocol, Documentation. Revision: Open workflow and results · Task Last observed 2026-09-06 06:10 UTC. This comment updates as work progresses. |
Numinous Forge · Engineering taskVerification passed The proposed change passed its accepted checks. PR verification is reported separately. Checks passed: Protocol, Documentation. Source revision: Open pull request · Task Last observed 2026-09-06 06:04 UTC. This comment updates as work progresses. |
Numinous Forge · Change and verificationResult: PR progress comments added and merged into this fork. Contributors can follow work in the PR conversation. What changed: One verification comment updates as checks queue, run, fail, or pass. An attached engineering task has a separate progress comment, so preparing a change and checking that change are distinguishable. What we exercised on this PR:
How to use it: Push a commit to rerun PR checks. Read the current verification comment for the result and workflow link. An attached task's comment reports its own progress. Maintainers still review the behavior and decide what to merge. These change summaries explain the work and its test evidence; the separate progress comments report current execution state. Review summary for 69ebc779cbfe. Live task and CI progress are reported separately. |
Explain how contributors follow Forge work on a PR and respond to failed checks. The guide separates agent progress from independent verification, links readers to the tested revision and results, and keeps merge decisions with maintainers. The generated status formatter also distinguishes a proposed change passing checks from PR verification and identifies tasks that end without a patch.
Validation: real PR verification reported an intentional test failure, then a passing corrected revision in the same comment. The temporary test was removed. An attached engineering task progressed through a recorded revision and independent protocol/documentation checks; its patch was applied only after its hash and Git tree matched the verification record. The final wording and generated workflow receive fresh required PR checks before merge.