Use selected bundle defaults for warded #1383

Merged

coilyco-ops merged 2 commits from issue-1227 into main

2026-07-15 10:25:54 +00:00

coilyco-ops commented

2026-07-15 10:19:02 +00:00

Owner

Selected-bundle defaults now drive warded launch resolution when a bundle defines them, so warded director and ward agents list pick up the active bundle instead of baked-only defaults.

This keeps the launch default and role catalog in the same precedence path, while preserving baked fallback when the selected bundle omits a value.

warded director --print now inherits bundle harness defaults.
ward agents list --json and the role roster read the selected bundle’s fleet/role catalog.
Added regression coverage and restored the missing generated defaults asset.

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

Selected-bundle defaults now drive warded launch resolution when a bundle defines them, so `warded director` and `ward agents list` pick up the active bundle instead of baked-only defaults. This keeps the launch default and role catalog in the same precedence path, while preserving baked fallback when the selected bundle omits a value. - `warded director --print` now inherits bundle harness defaults. - `ward agents list --json` and the role roster read the selected bundle’s fleet/role catalog. - Added regression coverage and restored the missing generated defaults asset. closes #1227 ward.workflow: pull-request-and-merge

coilyco-ops added 1 commit

2026-07-15 10:19:02 +00:00

Use selected bundle defaults for warded

test / test (pull_request) Failing after 36s

Details

af2b11ad5a