Fix broken warded launcher in read-only director surfaces #961
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!961
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-951"
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 #951
This copies the staged ward binary into /usr/local/bin/ward, keeps warded as the public symlink to that local copy, and preserves the warded --help startup smoke check so read-only surfaces fail fast if dispatch is unavailable.
WARD-OUTCOME: blocked 🛑
details
workflow: pull-requests; review summary: skip because --skip-preflight / --no-preflight also skips review
The launcher fix is in place and validated locally with
go test ./cmd/ward -run 'TestEntrypoint|TestLaunchAgentReportsOOMKilled'andpre-commit run --all-files.Forgejo PR #961 failed twice in CI setup before checkout. Run 1564 failed in 3s with no job logs, and the retrigger commit
373656d5produced the same failure as run 1565.canRerunis false and the job page exposes no step logs, so there is nothing actionable left to patch in-repo.confidence: medium
surprise: the workflow dies in setup, not in the test steps, so this looks like a runner/setup outage or platform regression.
follow-up: rerun the PR once the Forgejo runner lane is healthy.