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

Fix broken warded launcher in read-only director surfaces #961

Merged
coilyco-ops merged 4 commits from issue-951 into main 2026-07-10 06:59:42 +00:00
Conversation 1 Commits 4 Files changed 9 +146 -19
coilyco-ops commented 2026-07-10 06:49:52 +00:00
Member
Copy link

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.

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.
fix: stabilize warded launcher
Some checks failed
test / test (pull_request) Failing after 3s
Details
94086d1cbe
ci: retrigger PR checks
Some checks failed
test / test (pull_request) Failing after 2s
Details
373656d5d7
coilyco-ops commented 2026-07-10 06:54:44 +00:00
Author
Member
Copy link

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' and pre-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 373656d5 produced the same failure as run 1565. canRerun is 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.

WARD-OUTCOME: blocked 🛑 <details><summary>details</summary> 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'` and `pre-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 `373656d5` produced the same failure as run 1565. `canRerun` is 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. </details>
Merge remote-tracking branch 'origin/main' into pr-961
All checks were successful
test / test (pull_request) Successful in 25s
Details
bf58f10140 
# Conflicts:
#	cmd/ward/agent_director.go
coilyco-ops referenced this pull request from a commit 2026-07-10 06:59:44 +00:00
Merge pull request #961
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!961
No description provided.