Rename fleetconfig syntax to agents and singular guardfile

coilyco-ops commented

2026-07-10 10:11:35 +00:00

Member

Problem

The aos ward-specs bundle is being reshaped in coilyco-flight-deck/agentic-os#431, and part of that requested shape changes the fleetconfig dialect that cli-guard owns today.

Current cli-guard evidence:

pkg/fleetconfig/fleetconfig.go hard-codes the embedded top-level block as fleet.
pkg/fleetconfig/fleetconfig.go parses role guardfile bindings from a plural guardfiles node.
docs/fleetconfig.md, docs/kdl-description.md, and pkg/fleetconfig/fleetconfig_test.go describe and test the old names.

The new aos shape wants:

agents {
    schema-version 2
    defaults { ... }
    agent claude { ... }
}

and role guardfile bindings as repeated singular child nodes in the roles file:

agent-roles {
    role engineer {
        ...
        guardfile "guardfile.forgejo.read.kdl"
        guardfile "guardfile.forgejo.readactions.kdl"
        guardfile "guardfile.forgejo.write.kdl"
    }
}

Scope

Update cli-guard's typed KDL config parser and docs for the renamed dialect pieces:

Accept agents { ... } as the embedded roster block instead of fleet { ... }.
Prefer repeated singular guardfile "..." nodes under role blocks instead of guardfiles ....
Preserve the parsed Go shape if useful (Role.Guardfiles.List can still be the in-memory representation), but the source KDL should be singular repeated nodes.
Decide whether compatibility for old fleet / guardfiles is needed. If compatibility is kept, document it as a temporary legacy alias and add explicit tests. If compatibility is not kept, fail closed with clear errors.
Update docs/fleetconfig.md, docs/kdl-description.md, docs/architecture.md references if they name the old top-level dialect.
Update fleetconfig tests, including duplicate guardfile handling and the no-guardfile role case.

Coordination

This is a consumer prerequisite for agentic-os#431. The aos issue should not land a bundle that ward cannot parse. Ward may also need a consumer-side update for renamed bundle filenames and the split defaults.kdl / repos.kdl files.

Acceptance criteria

pkg/fleetconfig parses the new agents block shape.
Role guardfile bindings parse from repeated singular guardfile nodes.
Tests cover the new syntax and the chosen old-syntax behavior.
Docs no longer present fleet / guardfiles as the primary syntax.
The cli-guard test suite passes.

ward.workflow: pull-requests-and-merge

## Problem The aos ward-specs bundle is being reshaped in `coilyco-flight-deck/agentic-os#431`, and part of that requested shape changes the fleetconfig dialect that cli-guard owns today. Current cli-guard evidence: * `pkg/fleetconfig/fleetconfig.go` hard-codes the embedded top-level block as `fleet`. * `pkg/fleetconfig/fleetconfig.go` parses role guardfile bindings from a plural `guardfiles` node. * `docs/fleetconfig.md`, `docs/kdl-description.md`, and `pkg/fleetconfig/fleetconfig_test.go` describe and test the old names. The new aos shape wants: ```kdl agents { schema-version 2 defaults { ... } agent claude { ... } } ``` and role guardfile bindings as repeated singular child nodes in the roles file: ```kdl agent-roles { role engineer { ... guardfile "guardfile.forgejo.read.kdl" guardfile "guardfile.forgejo.readactions.kdl" guardfile "guardfile.forgejo.write.kdl" } } ``` ## Scope Update cli-guard's typed KDL config parser and docs for the renamed dialect pieces: * Accept `agents { ... }` as the embedded roster block instead of `fleet { ... }`. * Prefer repeated singular `guardfile "..."` nodes under `role` blocks instead of `guardfiles ...`. * Preserve the parsed Go shape if useful (`Role.Guardfiles.List` can still be the in-memory representation), but the source KDL should be singular repeated nodes. * Decide whether compatibility for old `fleet` / `guardfiles` is needed. If compatibility is kept, document it as a temporary legacy alias and add explicit tests. If compatibility is not kept, fail closed with clear errors. * Update `docs/fleetconfig.md`, `docs/kdl-description.md`, `docs/architecture.md` references if they name the old top-level dialect. * Update fleetconfig tests, including duplicate `guardfile` handling and the no-guardfile role case. ## Coordination This is a consumer prerequisite for `agentic-os#431`. The aos issue should not land a bundle that ward cannot parse. Ward may also need a consumer-side update for renamed bundle filenames and the split `defaults.kdl` / `repos.kdl` files. ## Acceptance criteria * `pkg/fleetconfig` parses the new `agents` block shape. * Role guardfile bindings parse from repeated singular `guardfile` nodes. * Tests cover the new syntax and the chosen old-syntax behavior. * Docs no longer present `fleet` / `guardfiles` as the primary syntax. * The cli-guard test suite passes. ward.workflow: pull-requests-and-merge

coilyco-ops commented

2026-07-10 10:11:45 +00:00

Author

Member

WARD-DISPATCH: deferred ⏸

deferred details

This forwarded dispatch was deferred after the issue was already reserved.

Attempted harness: codex
Attempted run: ward agent engineer coilyco-flight-deck/cli-guard#219 --harness codex --ward-version v0.579.0
Container: engineer-codex-cli-guard-219
Container created: no running engineer was observed.
Host log: /Users/kai/.ward/agent-logs/dispatch/20260710T101140Z-director-codex-rh98-coilyco-flight-deck-cli-guard-219.log
Capacity: ward agent engineer --harness codex: global engineer limit is reached: 12 running (limit 12); wait for a run to finish or run ward agent reap for stale engineers

Retry: the issue stays queued and the director will try again when a slot opens.

— Codex, via ward agent

WARD-DISPATCH: deferred ⏸ <details><summary>deferred details</summary> This forwarded dispatch was deferred after the issue was already reserved. Attempted harness: `codex` Attempted run: `ward agent engineer coilyco-flight-deck/cli-guard#219 --harness codex --ward-version v0.579.0` Container: `engineer-codex-cli-guard-219` Container created: no running engineer was observed. Host log: `/Users/kai/.ward/agent-logs/dispatch/20260710T101140Z-director-codex-rh98-coilyco-flight-deck-cli-guard-219.log` Capacity: `ward agent engineer --harness codex: global engineer limit is reached: 12 running (limit 12); wait for a run to finish or run `ward agent reap` for stale engineers` Retry: the issue stays queued and the director will try again when a slot opens. </details>  — Codex, via `ward agent`

coilyco-ops added the

headless

P2

labels

2026-07-10 10:24:47 +00:00

coilyco-ops commented

2026-07-10 16:43:13 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-cli-guard-219 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-10T16:43:13Z). 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/cli-guard#219 · branch issue-219 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-cli-guard-219 · ward v0.584.0 · dispatched 2026-07-10T16:43:13Z
Comment thread: 1 included in the pre-flight read, 0 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-10T10:11:45Z)

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

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-cli-guard-219` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T16:43:13Z). 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/cli-guard#219` · branch `issue-219` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-cli-guard-219` · ward `v0.584.0` · dispatched `2026-07-10T16:43:13Z` - **Comment thread:** 1 included in the pre-flight read, 0 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-10T10:11:45Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.584.0). </details> </details>  — Codex, via `ward agent`

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

2026-07-10 16:56:08 +00:00

Rename fleetconfig syntax to agents and singular guardfile #220

coilyco-ops commented

2026-07-10 16:57:35 +00:00

Author

Member

WARD-OUTCOME: merge-ready

details

workflow: pull-requests-and-merge; review summary: skipped (review gate skipped by ~/.ward/config.yaml default)
reservation: hand-back complete
implementation felt steady after the parser split. the only surprise was the repo comment cap and stale godoc snapshot.
confidence: high
surprises: godoc-current.txt needed regeneration after the comment edits.
follow-ups: none

WARD-OUTCOME: merge-ready <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: skipped (review gate skipped by ~/.ward/config.yaml default) reservation: hand-back complete implementation felt steady after the parser split. the only surprise was the repo comment cap and stale godoc snapshot. confidence: high surprises: godoc-current.txt needed regeneration after the comment edits. follow-ups: none </details>

coilyco-ops commented

2026-07-10 21:50:26 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-claude-cli-guard-219 on host KAI-DESKTOP-TOWER.

Reserved by ward agent --harness claude (reserved 2026-07-10T21:50:26Z). 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/cli-guard#219 · branch issue-219 · harness claude · workflow pull-requests-and-merge
Run: engineer-claude-cli-guard-219 · ward v0.605.0 · dispatched 2026-07-10T21:50:26Z
Comment thread: 2 included in the pre-flight read, 1 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-10T10:11:45Z), @coilyco-ops (2026-07-10T16:57:35Z)
- stripped: @coilyco-ops (2026-07-10T16:43:13Z)

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

— Claude (she/her), via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-claude-cli-guard-219` on host `KAI-DESKTOP-TOWER`. Reserved by `ward agent --harness claude` (reserved 2026-07-10T21:50:26Z). 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/cli-guard#219` · branch `issue-219` · harness `claude` · workflow `pull-requests-and-merge` - **Run:** `engineer-claude-cli-guard-219` · ward `v0.605.0` · dispatched `2026-07-10T21:50:26Z` - **Comment thread:** 2 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-10T10:11:45Z), @coilyco-ops (2026-07-10T16:57:35Z) - stripped: @coilyco-ops (2026-07-10T16:43:13Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.605.0). </details> </details>  — Claude (she/her), via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-10 21:56:16 +00:00

test(fleetconfig): cover guardfile/guardfiles mixing rejection

coilyco-ops commented

2026-07-10 21:58:40 +00:00

Author

Member

WARD-OUTCOME: merge-ready

details

workflow: pull-requests-and-merge; review summary: skipped (in-container review gate intentionally skipped by the temporary ward default pending brokered QA)
reservation: hand-back complete
pr: #220 at head f8d2fcc, CI green (test, lint, secrets), mergeable, waiting on the director merge
retrospective: a prior codex run had already landed the rename on issue-219 and opened #220. This claude run verified the branch against every acceptance criterion, ran the full suite plus vet and lint locally, and added three reject tests for the untested guardfile/guardfiles mixing and duplicate-legacy-alias error paths, then re-confirmed CI green on the new head.
confidence: high
surprises: none - the branch arrived merge-ready, only the mixing-rejection tests were missing.
follow-ups: none

WARD-OUTCOME: merge-ready <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: skipped (in-container review gate intentionally skipped by the temporary ward default pending brokered QA) reservation: hand-back complete pr: #220 at head f8d2fcc, CI green (test, lint, secrets), mergeable, waiting on the director merge retrospective: a prior codex run had already landed the rename on issue-219 and opened #220. This claude run verified the branch against every acceptance criterion, ran the full suite plus vet and lint locally, and added three reject tests for the untested guardfile/guardfiles mixing and duplicate-legacy-alias error paths, then re-confirmed CI green on the new head. confidence: high surprises: none - the branch arrived merge-ready, only the mixing-rejection tests were missing. follow-ups: none </details>

coilyco-ops closed this issue

2026-07-10 22:12:37 +00:00

Rows
Columns

Rename fleetconfig syntax to agents and singular guardfile #219

Problem

Scope

Coordination

Acceptance criteria