Repair Goose residual landing path after PR #997 diagnostics-only fix

coilyco-ops commented

2026-07-10 10:04:10 +00:00

Owner

closes #998

ward.workflow: pull-requests-and-merge

This replaces the diagnostics-only PR with a dirty-only Goose landing path and a normal-success fixture that proves the reaper repairs the closing reference before teardown only when the worker never committed.

closes #998 ward.workflow: pull-requests-and-merge This replaces the diagnostics-only PR with a dirty-only Goose landing path and a normal-success fixture that proves the reaper repairs the closing reference before teardown only when the worker never committed.

coilyco-ops added 2 commits

2026-07-10 10:04:10 +00:00

fix: distinguish Goose residual commit states 9b7a6d0395

closes #993

fix(goose): repair dirty-only residual landing

test / test (pull_request) Failing after 19s

Details

bc64395637

closes #998

coilyco-ops commented

2026-07-10 10:07:05 +00:00

Author

Owner

verdict: block
confidence: medium
summary: PR #1002 adds the dirty-only Goose residual landing path that ward#998 asked for, including a normal-success fixture, but the live required PR check is red on the current head. I also attempted the focused local Go tests, but this director container's filesystem is full and Go failed during compilation before reaching the tests, so the authoritative blocker is the Forgejo check state.
findings:

severity: high
file: n/a
line: n/a
problem: Forgejo reports test / test (pull_request)=failure for head bc64395637c73e85392081f5802c972adae64101, target /coilyco-flight-deck/ward/actions/runs/1610/jobs/0, description Failing after 19s.
impact: The PR cannot satisfy the issue's green-gate requirement or be safely merged by the director lane while the required test context is red.
conclusion: The patch appears to target the right missing behavior from ward#998, but the current PR head is blocked on a failing required test check. The next worker should diagnose run 1610, update the branch or replacement PR, and keep the dirty-only landing fixture plus close-reference diagnostics intact.

verdict: block confidence: medium summary: PR #1002 adds the dirty-only Goose residual landing path that ward#998 asked for, including a normal-success fixture, but the live required PR check is red on the current head. I also attempted the focused local Go tests, but this director container's filesystem is full and Go failed during compilation before reaching the tests, so the authoritative blocker is the Forgejo check state. findings: - severity: high file: n/a line: n/a problem: Forgejo reports `test / test (pull_request)=failure` for head `bc64395637c73e85392081f5802c972adae64101`, target `/coilyco-flight-deck/ward/actions/runs/1610/jobs/0`, description `Failing after 19s`. impact: The PR cannot satisfy the issue's green-gate requirement or be safely merged by the director lane while the required test context is red. conclusion: The patch appears to target the right missing behavior from ward#998, but the current PR head is blocked on a failing required test check. The next worker should diagnose run 1610, update the branch or replacement PR, and keep the dirty-only landing fixture plus close-reference diagnostics intact.

coilysiren closed this pull request

2026-07-10 10:07:09 +00:00

coilyco-ops referenced this pull request

2026-07-10 10:09:06 +00:00

Replace closed-unmerged dirty-only Goose residual landing PR #1006

coilyco-ops referenced this pull request

2026-07-10 10:10:13 +00:00

Keep director surfaces from running out of writable test space #1008

coilyco-ops referenced this pull request

2026-07-14 15:42:03 +00:00

docs: name ward#1002 as the closed-unmerged example #1286

Rows
Columns

Repair Goose residual landing path after PR #997 diagnostics-only fix #1002