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

Correct launch pre-flight seed reservation re-check status #1424

Merged
coilyco-ops merged 2 commits from issue-1417 into main 2026-07-15 12:19:30 +00:00
Conversation 1 Commits 2 Files changed 2 +38 -23
coilyco-ops commented 2026-07-15 12:12:34 +00:00
Member
Copy link

The launch pre-flight seed now tells the truth about the reservation re-check at construction time. Instead of claiming a future pass, it marks the re-check deferred, which keeps both the normal launch path and --skip-preflight honest.

  • What changed: moved the launch seed wording from passed to deferred and pinned that behavior in tests.
  • Why: the launched agent should not see a re-check result that has not happened yet.
  • Tests: go test ./...

closes #1417
ward.workflow: pull-request-and-merge

The launch pre-flight seed now tells the truth about the reservation re-check at construction time. Instead of claiming a future pass, it marks the re-check deferred, which keeps both the normal launch path and `--skip-preflight` honest. - What changed: moved the launch seed wording from `passed` to `deferred` and pinned that behavior in tests. - Why: the launched agent should not see a re-check result that has not happened yet. - Tests: `go test ./...` closes #1417 ward.workflow: pull-request-and-merge
Correct launch pre-flight seed re-check status (#1417)
Some checks failed
test / test (pull_request) Failing after 33s
Details
5b969fabb1
coilyco-ops commented 2026-07-15 12:17:57 +00:00
Author
Member
Copy link

Forgejo PR check failed on go test for commit 5b969fabb19c22c202213ff2a25875339520e6a4 (run 8531 / job 14285).

I reproduced the repo checks locally with make vet, make test, and make lint; they all pass here, so this looks like a runner/transient mismatch rather than a code regression. I am retriggering the PR workflow with a fresh push to confirm.

Forgejo PR check failed on `go test` for commit `5b969fabb19c22c202213ff2a25875339520e6a4` (run 8531 / job 14285). I reproduced the repo checks locally with `make vet`, `make test`, and `make lint`; they all pass here, so this looks like a runner/transient mismatch rather than a code regression. I am retriggering the PR workflow with a fresh push to confirm.
chore: retrigger PR #1417 checks
All checks were successful
test / test (pull_request) Successful in 50s
Details
bf85adf851
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!1424
No description provided.