fix: surface director launch config in print plan #1161

Closed
coilyco-ops wants to merge 0 commits from issue-1137 into main
Member

Adds a structured director pre-launch summary so the print path shows:

  • selected config source
  • limit, max-parallel, poll-interval, max-cycles
  • explicit engineer harness value

Also adds a regression test for the print output.

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

Adds a structured director pre-launch summary so the print path shows: - selected config source - limit, max-parallel, poll-interval, max-cycles - explicit engineer harness value Also adds a regression test for the print output. closes #1137 ward.workflow: pull-request-and-merge
fix: surface director launch config in print plan
All checks were successful
test / test (pull_request) Successful in 33s
bc344293b1
Author
Member

The burn-down session working for Kai landed this PR on main at 5f1570b25a (merge of origin/issue-1137 into main). The Forgejo native merge endpoint returned 405 (ward#1168), so the burn-down session merged locally, pushed to main, and now closes this PR by hand. The single conflict in cmd/ward/broker_exec.go was a comment-only rewrap and the burn-down session kept main's wording. ward build, ward test, and pre-commit all match clean main.

The burn-down session working for Kai landed this PR on main at 5f1570b25a501cb26a9bc144574ea404e45dd273 (merge of origin/issue-1137 into main). The Forgejo native merge endpoint returned 405 (ward#1168), so the burn-down session merged locally, pushed to main, and now closes this PR by hand. The single conflict in cmd/ward/broker_exec.go was a comment-only rewrap and the burn-down session kept main's wording. ward build, ward test, and pre-commit all match clean main.
coilyco-ops closed this pull request 2026-07-13 06:46:43 +00:00
All checks were successful
test / test (pull_request) Successful in 33s

Pull request closed

Sign in to join this conversation.
No description provided.