coilyco-flight-deck/ward

Fork 0

Fix ward release CI failure on current head #1313

New issue

Closed

opened 2026-07-15 04:42:55 +00:00 by coilyco-ops · 3 comments

coilyco-ops commented

2026-07-15 04:42:55 +00:00

Member

ward release is red on the current branch head while main is green.

Evidence from the director babysit loop:

main head: 2f706034a5445df9dd1a369296f5118651ed9e39, feat(director): raise burndown default to 6 (#1311)
release head: 2f706034a5445df9dd1a369296f5118651ed9e39, same commit
Exact-head main run: 2079, promote.yml, success, created 2026-07-15T04:38:36Z, stopped 2026-07-15T04:41:43Z
Exact-head release run: 2080, release.yml, failure, created 2026-07-15T04:41:41Z, stopped 2026-07-15T04:42:21Z
Run URL: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/actions/runs/2080

Please identify the failing release job, fix the release branch CI state, and leave final green run evidence for both main and release.

ward `release` is red on the current branch head while `main` is green. Evidence from the director babysit loop: * `main` head: `2f706034a5445df9dd1a369296f5118651ed9e39`, `feat(director): raise burndown default to 6 (#1311)` * `release` head: `2f706034a5445df9dd1a369296f5118651ed9e39`, same commit * Exact-head `main` run: `2079`, `promote.yml`, `success`, created `2026-07-15T04:38:36Z`, stopped `2026-07-15T04:41:43Z` * Exact-head `release` run: `2080`, `release.yml`, `failure`, created `2026-07-15T04:41:41Z`, stopped `2026-07-15T04:42:21Z` * Run URL: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/actions/runs/2080 Please identify the failing release job, fix the release branch CI state, and leave final green run evidence for both `main` and `release`.

coilyco-ops commented

2026-07-15 04:43:32 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-ward-1313 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-15T04:43:31Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#1313 · branch issue-1313 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1313 · ward v0.697.0 · dispatched 2026-07-15T04:43:20Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.697.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1313` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T04:43:31Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#1313` · branch `issue-1313` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1313` · ward `v0.697.0` · dispatched `2026-07-15T04:43:20Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.697.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue

2026-07-15 04:48:34 +00:00

Restore promote-only release branch contract #1315

coilyco-ops added the

headless

labels

2026-07-15 04:51:12 +00:00

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-15 04:53:34 +00:00

fix(cmd/ward): widen engineer visibility test timeout #1316

coilyco-ops commented

2026-07-15 04:54:01 +00:00

Author

Member

WARDED_WORKFLOW: #1316

details

workflow: pull-request-and-merge; review summary: review gate intentionally skipped because the temporary ward default pending brokered QA

felt like a timing race in the dispatch-broker visibility test.

confidence: high

surprise: the release failure was a CI timeout edge, not a product logic break.

follow-up: none

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1316 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate intentionally skipped because the temporary ward default pending brokered QA felt like a timing race in the dispatch-broker visibility test. confidence: high surprise: the release failure was a CI timeout edge, not a product logic break. follow-up: none </details>

coilysiren closed this issue

2026-07-15 04:56:00 +00:00

coilysiren referenced this issue from a commit

2026-07-15 04:56:02 +00:00

fix(cmd/ward): widen engineer visibility test timeout (#1316)

coilyco-ops added this to the warded control plane coherence milestone

2026-07-15 05:14:47 +00:00

coilyco-ops commented

2026-07-15 07:16:41 +00:00

Author

Member

WARD-TRIAGE: warded control plane coherence milestone

This issue is part of the warded control plane coherence sprint. The release thesis is to make warded feel like one dependable control plane for agent work: higher safe parallelism, coherent config defaults, reliable broker/container behavior, human-feedback gates, and enough structured evidence for the next actor after a paused or failed run.

For this sprint, headless means an engineer should be able to carry the issue from current issue context to a merged change without new human decisions. If the issue discovers a missing decision, split or demote the unclear part instead of guessing.

WARD-TRIAGE: warded control plane coherence milestone This issue is part of the `warded control plane coherence` sprint. The release thesis is to make `warded` feel like one dependable control plane for agent work: higher safe parallelism, coherent config defaults, reliable broker/container behavior, human-feedback gates, and enough structured evidence for the next actor after a paused or failed run. For this sprint, `headless` means an engineer should be able to carry the issue from current issue context to a merged change without new human decisions. If the issue discovers a missing decision, split or demote the unclear part instead of guessing.