Narrow WARD_CONFIG_REF to edge surfaces and protect ward core defaults #845

New issue

Closed

opened 2026-07-09 18:26:11 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-09 18:26:11 +00:00

Member

First slice:

Narrow WARD_CONFIG_REF so a broken or unreachable external bundle cannot break core agent/container behavior such as ward agent, ward agents list, reservation defaults, review timing, or topology needed to bring up containers.
Split the config-source seam into edge-surface source versus core-runtime source, even if some callers still use the old path behind the new boundary.
Keep generated ward ops edge surfaces working through the existing degrade-to-error-leaf pattern when their bundle fails to parse.
Add a boundary test proving a bad WARD_CONFIG_REF degrades edge-mounted surfaces without preventing core paths from loading their ward-native defaults.
Update docs that currently imply ward-kdl is ward core's runtime control plane.

Acceptance:

Core agent/container paths have ward-owned defaults and do not require a live KDL bundle to parse.
Edge ops surfaces still report bundle/build errors clearly.
Tests cover broken/unreachable config source behavior for core versus edge paths.
ward exec test passes.

Closes #721 when landed, unless the implementation splits a remaining follow-up explicitly.

Context: implementation follow-up from #721. The consult direction is settled: KDL and ward-kdl stay at the guarded edge surface, while ward core behavior moves back into ward-owned runtime data and helpers. First slice: * Narrow `WARD_CONFIG_REF` so a broken or unreachable external bundle cannot break core agent/container behavior such as `ward agent`, `ward agents list`, reservation defaults, review timing, or topology needed to bring up containers. * Split the config-source seam into edge-surface source versus core-runtime source, even if some callers still use the old path behind the new boundary. * Keep generated `ward ops` edge surfaces working through the existing degrade-to-error-leaf pattern when their bundle fails to parse. * Add a boundary test proving a bad `WARD_CONFIG_REF` degrades edge-mounted surfaces without preventing core paths from loading their ward-native defaults. * Update docs that currently imply ward-kdl is ward core's runtime control plane. Acceptance: * Core agent/container paths have ward-owned defaults and do not require a live KDL bundle to parse. * Edge ops surfaces still report bundle/build errors clearly. * Tests cover broken/unreachable config source behavior for core versus edge paths. * `ward exec test` passes. Closes #721 when landed, unless the implementation splits a remaining follow-up explicitly.

coilyco-ops added the

headless

labels

2026-07-09 18:26:11 +00:00

coilyco-ops referenced this issue

2026-07-09 18:26:23 +00:00

design: decouple ward core from ward-kdl runtime/specgen assumptions #721

coilyco-ops commented

2026-07-09 18:28:48 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-845 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T18:28:45Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force 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#845 · branch issue-845 · harness codex · workflow pull-request
Run: engineer-codex-ward-845 · ward v0.493.0 · dispatched 2026-07-09T18:28: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.493.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-845` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T18:28:45Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` 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#845` · branch `issue-845` · harness `codex` · workflow `pull-request` - **Run:** `engineer-codex-ward-845` · ward `v0.493.0` · dispatched `2026-07-09T18:28: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.493.0). </details> </details>  — Codex, via `ward agent`

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

2026-07-09 18:48:48 +00:00

Narrow WARD_CONFIG_REF to edge surfaces and protect ward core defaults #855

coilyco-ops commented

2026-07-09 18:52:24 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

workflow: pull-request; review summary: skipped (review gate skipped by ~/.ward/config.yaml default)
felt: narrow and mechanical, then one lint cleanup
confidence: high
surprises: Forgejo surfaced the real failure only in golangci-lint
follow-ups: none

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: pull-request; review summary: skipped (review gate skipped by ~/.ward/config.yaml default) felt: narrow and mechanical, then one lint cleanup confidence: high surprises: Forgejo surfaced the real failure only in golangci-lint follow-ups: none </details>

coilyco-ops closed this issue

2026-07-09 19:02:38 +00:00