Fix WARD_CONFIG_REF smart-default deadlock during ops command startup #907
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/ward!907
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-876"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
closes #876
ward.workflow: pull-requests-and-merge
WARD-OUTCOME: blocked 🛑
details
workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default The merge/retrigger path is blocked by Forgejo CI. PR #907 fails in the test job before checkout on two consecutive pushes (runs 1498 and 1502), while local `ward exec test` passes. Confidence: high. Surprise: the job dies during setup, so this looks external to the patch. Follow-up: retry once the Forgejo runner is healthy.