ward doctor should not require fleet defaults #1230

Merged

coilysiren merged 1 commit from issue-1197 into main

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

coilyco-ops commented

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

Member

Relax fleet doctor validation so missing fleet defaults blocks fall back to the baked defaults instead of failing the run. This keeps ward doctor aligned with the fleet parser, which already accepts sparse agents blocks.

The regression test covers a bundle with the defaults child removed from the fleet fixture.

What changed: doctor now skips fleet-default validation when the block is absent.
Why: sparse bundles should stay valid for ward doctor.
Tests: ward exec test, pre-commit run --all-files.

closes #1197
ward.workflow: pull-request-and-merge

Relax fleet doctor validation so missing fleet defaults blocks fall back to the baked defaults instead of failing the run. This keeps `ward doctor` aligned with the fleet parser, which already accepts sparse `agents` blocks. The regression test covers a bundle with the `defaults` child removed from the fleet fixture. - What changed: `doctor` now skips fleet-default validation when the block is absent. - Why: sparse bundles should stay valid for `ward doctor`. - Tests: `ward exec test`, `pre-commit run --all-files`. closes #1197 ward.workflow: pull-request-and-merge

coilyco-ops added 1 commit

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