coilyco-flight-deck/ward
2
0
Fork 0
Code Issues 105 Pull requests Projects Releases 737 Packages Wiki Activity Actions

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

Closed
coilyco-ops wants to merge 2 commits from issue-998 into main
pull from: issue-998
merge into: coilyco-flight-deck:main
Conversation 1 Commits 2 Files changed 21 +6572 -22
coilyco-ops commented 2026-07-10 10:04:10 +00:00
Member
Copy link

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.
closes #993
fix(goose): repair dirty-only residual landing
Some checks failed
test / test (pull_request) Failing after 19s
Details
bc64395637 
closes #998
coilyco-ops commented 2026-07-10 10:07:05 +00:00
Author
Member
Copy link

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
Some checks failed
test / test (pull_request) Failing after 19s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
pressure-test
Cold-read release pressure-test findings and coordination

  
sunday-sprint
Burn-down by Sunday 2026-06-07

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
pressure-test
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/ward!1002
No description provided.