ward doctor shouldn't require a "defaults" block #1197

New issue

Closed

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

coilysiren commented

2026-07-13 21:12:05 +00:00

Owner

they're... defaults :p

error message:

#26 4.106 FAIL smart defaults: bundle: missing top-level `defaults` block (fail-closed)

they're... defaults :p error message: ``` #26 4.106 FAIL smart defaults: bundle: missing top-level `defaults` block (fail-closed) ```

coilyco-ops commented

2026-07-14 06:36:26 +00:00

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-14T06:36:25Z). 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#1197 · branch issue-1197 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1197 · ward v0.667.0 · dispatched 2026-07-14T06:36:19Z
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.667.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1197` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-14T06:36:25Z). 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#1197` · branch `issue-1197` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1197` · ward `v0.667.0` · dispatched `2026-07-14T06:36:19Z` - **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.667.0). </details> </details>  — Codex, via `ward agent`

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

2026-07-14 06:44:00 +00:00

ward doctor should not require fleet defaults #1230

coilyco-ops commented

2026-07-14 06:46:03 +00:00

Member

WARDED_WORKFLOW: #1230

details

workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default

felt: narrow. I only touched the doctor fleet-default check and one regression test.

confidence: high.

surprises: fleet parsing already allows omitted defaults, so the fix stayed in validation.

follow-ups: none.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1230 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default felt: narrow. I only touched the doctor fleet-default check and one regression test. confidence: high. surprises: fleet parsing already allows omitted defaults, so the fix stayed in validation. follow-ups: none. </details>

coilyco-ops added the

headless

labels

2026-07-14 06:50:01 +00:00

coilysiren closed this issue

2026-07-14 06:58:11 +00:00

coilysiren referenced this issue from a commit

2026-07-14 06:58:12 +00:00

ward doctor should not require fleet defaults (#1230)