This PR is the wrong direction for the release-readiness config work. It syncs a custom Codex director overlay back into ward, but the intended solution is the opposite: move the whole custom fleet file, and every custom KDL file, out of ward and into the aos-owned bundle. Ward's shipped/default bundle should stay neutral, with operator-specific KDL selected through the config source path.

Superseded by the neutral-bundle/aos move direction in #893 and the merge-queue repair issue #903. Do not merge this PR as a fix for #897.

NO-GO for merge queue. This PR is the wrong direction for the release-readiness config work. It syncs a custom Codex director overlay back into ward, but the intended solution is the opposite: move the whole custom fleet file, and every custom KDL file, out of ward and into the aos-owned bundle. Ward's shipped/default bundle should stay neutral, with operator-specific KDL selected through the config source path. Superseded by the neutral-bundle/aos move direction in #893 and the merge-queue repair issue #903. Do not merge this PR as a fix for #897.

coilyco-ops referenced this pull request

2026-07-10 00:51:32 +00:00

Repair ward PR merge queue from failed prior runs #903

coilyco-ops added 1 commit

2026-07-10 00:54:59 +00:00

Merge main into issue-897

test / test (pull_request) Successful in 27s

Details

3070f65023

coilyco-ops merged commit da011ce39f into main

2026-07-10 00:56:12 +00:00

coilyco-ops referenced this pull request from a commit