Goose engineer can answer in logs and exit clean without carrying the issue #886

Merged
coilyco-ops merged 8 commits from issue-697 into main 2026-07-10 06:25:45 +00:00
Member

closes #697
ward.workflow: pull-requests-and-merge

This branch tightens the Goose engineer launch/seed path and surfaces clean no-outcome exits as failed issue comments.

closes #697 ward.workflow: pull-requests-and-merge This branch tightens the Goose engineer launch/seed path and surfaces clean no-outcome exits as failed issue comments.
fix goose engineer no-op runs
Some checks failed
test / test (pull_request) Failing after 30s
184bd34687
Merge remote-tracking branch 'origin/main' into issue-697
Some checks failed
test / test (pull_request) Failing after 22s
ef68e66138
# Conflicts:
#	cmd/ward/agent_dispatch_broker.go
#	cmd/ward/agent_dispatch_broker_test.go
#	cmd/ward/agent_reserve.go
#	cmd/ward/forgejo_ops.go
Author
Member

WARD-OUTCOME: blocked 🛑

details

workflow: pull-requests-and-merge; review summary: skipped: review gate skipped by ~/.ward/config.yaml default

Repaired PR #886 by merging current main into issue-697 and pushed ef68e66.
ward exec test passed.
ward agent director merge --repo coilyco-flight-deck/ward --dry-run --limit 100 no longer reports #886 as a plain merge-conflict skip, but it still blocks on the base branch: current main does not declare required status check contexts.

Next step: fix or relax that base-branch gate, then rerun the director dry-run.

WARD-OUTCOME: blocked 🛑 <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: skipped: review gate skipped by ~/.ward/config.yaml default Repaired PR #886 by merging current `main` into `issue-697` and pushed `ef68e66`. `ward exec test` passed. `ward agent director merge --repo coilyco-flight-deck/ward --dry-run --limit 100` no longer reports #886 as a plain merge-conflict skip, but it still blocks on the base branch: current `main` does not declare required status check contexts. Next step: fix or relax that base-branch gate, then rerun the director dry-run. </details>
Merge main into issue-697
Some checks failed
test / test (pull_request) Failing after 30s
7dd4e73eb3
merge main into issue-697
Some checks failed
test / test (pull_request) Failing after 3s
971ffb6601
chore: retry ci
Some checks failed
test / test (pull_request) Failing after 3s
add90181ed
Author
Member

WARD-OUTCOME: blocked 🛑

details

workflow: pull-requests-and-merge; review summary: skipped: review gate skipped by ~/.ward/config.yaml default
blocker: Forgejo Actions run 1508 for add90181ed397d93bde404f67d42287f38a1d3ed fails in Set up job before checkout. The job summary reports test / test (pull_request) as failure after 3s and exposes no step logs.
retry: an empty retry commit (add9018) reproduced the same 3s setup failure on run 1508.

WARD-OUTCOME: blocked 🛑 <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: skipped: review gate skipped by ~/.ward/config.yaml default blocker: Forgejo Actions run 1508 for `add90181ed397d93bde404f67d42287f38a1d3ed` fails in `Set up job` before checkout. The job summary reports `test / test (pull_request)` as failure after 3s and exposes no step logs. retry: an empty retry commit (`add9018`) reproduced the same 3s setup failure on run 1508. </details>
Merge remote-tracking branch 'origin/main' into issue-697
All checks were successful
test / test (pull_request) Successful in 28s
cd96b32bc2
# Conflicts:
#	cmd/ward/agent_director.go
Merge remote-tracking branch 'origin/main' into issue-697
All checks were successful
test / test (pull_request) Successful in 31s
9ce75c1988
# Conflicts:
#	cmd/ward/agent_director.go
Merge remote-tracking branch 'origin/main' into issue-697
All checks were successful
test / test (pull_request) Successful in 35s
ecd496a492
coilyco-ops referenced this pull request from a commit 2026-07-10 06:25:46 +00:00
Sign in to join this conversation.
No description provided.