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

ward-container: residual goose work on coilyco-flight-deck/ward #705

Merged
coilysiren merged 1 commit from ward-salvage/ward-c58e9c43 into main 2026-07-08 22:05:18 +00:00
Conversation 0 Commits 1 Files changed 2 +59 -3
coilysiren commented 2026-07-08 22:05:11 +00:00
Owner
Copy link

Co-Authored-By: Goose goose@ward.agent

Summary

Related issue

Checklist

  • I opened an issue first and referenced it above (see CONTRIBUTING.md).
  • The change stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb.
  • I ran the dev verbs locally: ward exec build, ward exec test, ward exec vet, ward exec lint.
  • Docs updated where behaviour changed (docs/, README.md, docs/FEATURES.md).
Co-Authored-By: Goose <goose@ward.agent> <!-- ward is Forgejo-canonical and mirrored read-only to GitHub. GitHub is the external front door for everyone except the maintainer: fork, push a branch, open your PR here. A maintainer replays an accepted PR onto Forgejo `main` and closes the matching Forgejo issue. If you are working directly in the canonical repo, use Forgejo instead. See CONTRIBUTING.md. --> ## Summary <!-- What does this change do, and why? --> ## Related issue <!-- Link the GitHub issue this addresses, e.g. Fixes #123. The internal Forgejo `closes #N` link is added by whoever carries the change across - you don't need it unless you're the maintainer working directly on Forgejo. --> ## Checklist - [ ] I opened an issue first and referenced it above (see CONTRIBUTING.md). - [ ] The change stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb. - [ ] I ran the dev verbs locally: `ward exec build`, `ward exec test`, `ward exec vet`, `ward exec lint`. - [ ] Docs updated where behaviour changed (`docs/`, `README.md`, `docs/FEATURES.md`).
ward-container: residual goose work on coilyco-flight-deck/ward
Some checks failed
test / test (pull_request) Failing after 50s
Details
4b3cbed7e5 
Co-Authored-By: Goose <goose@ward.agent>
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!705
No description provided.