ward doctor should not require fleet defaults #1230
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/ward!1230
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-1197"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Relax fleet doctor validation so missing fleet defaults blocks fall back to the baked defaults instead of failing the run. This keeps
ward doctoraligned with the fleet parser, which already accepts sparseagentsblocks.The regression test covers a bundle with the
defaultschild removed from the fleet fixture.doctornow skips fleet-default validation when the block is absent.ward doctor.ward exec test,pre-commit run --all-files.closes #1197
ward.workflow: pull-request-and-merge