ward config KDL file should be able to set the ward agent image and tag #1143

New issue

Closed

opened 2026-07-13 03:05:07 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-07-13 03:05:07 +00:00

Owner

The problem

so there's 2 less errant configs

Proposed change

Alternatives considered

Before filing

I searched existing issues and this is not a duplicate.
This stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb.

### The problem so there's 2 less errant configs ### Proposed change // ### Alternatives considered // ### Before filing - [x] I searched existing issues and this is not a duplicate. - [x] This stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb.

coilyco-ops commented

2026-07-13 03:22:48 +00:00

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-1143 on host KAI-DESKTOP-TOWER.

Reserved by ward agent --harness codex (reserved 2026-07-13T03:22:45Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (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#1143 · branch issue-1143 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1143 · ward v0.633.0 · dispatched 2026-07-13T03:22:45Z
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.633.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-1143` on host `KAI-DESKTOP-TOWER`. Reserved by `ward agent --harness codex` (reserved 2026-07-13T03:22:45Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (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#1143` · branch `issue-1143` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1143` · ward `v0.633.0` · dispatched `2026-07-13T03:22:45Z` - **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.633.0). </details> </details>  — Codex, via `ward agent`

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

2026-07-13 03:40:16 +00:00

ward config KDL file should be able to set the ward agent image and tag #1157

coilyco-ops commented

2026-07-13 03:41:27 +00:00

Member

WARD-OUTCOME: submitted

details

workflow: pull-request-and-merge; review summary: skipped because the temporary ward default pending brokered QA
Implementation felt contained. Confidence: high. Surprises: none beyond the repo-wide hook noise during local validation. Follow-up: merge the PR when the director loop is ready.

WARD-OUTCOME: submitted <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped because the temporary ward default pending brokered QA Implementation felt contained. Confidence: high. Surprises: none beyond the repo-wide hook noise during local validation. Follow-up: merge the PR when the director loop is ready. </details>

coilyco-ops closed this issue

2026-07-13 03:42:29 +00:00