coilyco-flight-deck/ward
2
0
Fork 0
Code Issues 105 Pull requests Projects Releases 737 Packages Wiki Activity Actions 1

Make ward agent roles config-defined presets instead of hard-coded names #906

Merged
coilyco-ops merged 6 commits from issue-895 into main 2026-07-10 06:21:17 +00:00
Conversation 2 Commits 6 Files changed 14 +732 -70
coilyco-ops commented 2026-07-10 00:50:53 +00:00
Member
Copy link

closes #895
ward.workflow: pull-requests-and-merge

Summary:

  • resolve agent roster rows from built-in role definitions plus effective fleet overlays
  • surface overlay summaries in the roster without changing the shipped commands
  • keep the roster doc generated from the resolved definitions
closes #895 ward.workflow: pull-requests-and-merge Summary: - resolve agent roster rows from built-in role definitions plus effective fleet overlays - surface overlay summaries in the roster without changing the shipped commands - keep the roster doc generated from the resolved definitions
refactor agent roster onto role definitions
Some checks failed
test / test (pull_request) Failing after 33s
Details
59c7921545
coilyco-ops commented 2026-07-10 00:54:34 +00:00
Author
Member
Copy link

This is a step in the right direction, but do not merge this shape as the final implementation.

The role definitions should not be hard-coded Go data plus fleet overlays. The implementation should introduce a special-purpose agent role KDL file type, embedded into ward at compile time, and resolve the shipped role presets from that KDL. The fleet config can still provide operator overlays, but the base role schema (name, tagline, semantic capabilities, invocation modes, posture, default harness/overlay hooks) should live in the embedded role KDL source rather than in builtInAgentRoleDefinitions().

Requested direction:

  • Add a dedicated role-definition KDL asset, separate from ward-kdl.fleet.kdl and separate from edge guardfiles.
  • Embed that file into ward at compile time as ward-owned product defaults.
  • Parse it into the role definition model that ward agent roster and launch planning consume.
  • Keep fleet KDL as the operator override layer, not the source of shipped role definitions.
  • Keep the current PR’s resolver/roster work if useful, but move the source of truth out of Go literals and into the embedded role KDL file type.

Please treat the current PR as an intermediate step that needs amendment, not merge-ready.

This is a step in the right direction, but do not merge this shape as the final implementation. The role definitions should not be hard-coded Go data plus fleet overlays. The implementation should introduce a special-purpose **agent role KDL file type**, embedded into ward at compile time, and resolve the shipped role presets from that KDL. The fleet config can still provide operator overlays, but the base role schema (name, tagline, semantic capabilities, invocation modes, posture, default harness/overlay hooks) should live in the embedded role KDL source rather than in `builtInAgentRoleDefinitions()`. Requested direction: - Add a dedicated role-definition KDL asset, separate from `ward-kdl.fleet.kdl` and separate from edge guardfiles. - Embed that file into ward at compile time as ward-owned product defaults. - Parse it into the role definition model that `ward agent roster` and launch planning consume. - Keep fleet KDL as the operator override layer, not the source of shipped role definitions. - Keep the current PR’s resolver/roster work if useful, but move the source of truth out of Go literals and into the embedded role KDL file type. Please treat the current PR as an intermediate step that needs amendment, not merge-ready.
fix lint on agent launch
All checks were successful
test / test (pull_request) Successful in 33s
Details
f3e9213e59
coilyco-ops force-pushed issue-895 from f3e9213e59
All checks were successful
test / test (pull_request) Successful in 33s
Details
to 8ee2108604
Some checks failed
test / test (pull_request) Failing after 3s
Details
2026-07-10 05:18:42 +00:00 Compare
chore: retrigger CI
Some checks failed
test / test (pull_request) Failing after 4s
Details
ba159e1ff1
feat: embed shipped agent role presets
Some checks failed
test / test (pull_request) Failing after 2s
Details
b1c85c3c56 
closes #895
coilyco-ops commented 2026-07-10 05:37:42 +00:00
Author
Member
Copy link

WARD-OUTCOME: blocked 🛑

details

workflow: pull-requests; review summary: skipped by ~/.ward/config.yaml default
Local validation is green (ward exec test, pre-commit run --all-files), but Forgejo Actions run test / test (pull_request) for head b1c85c3c5610c8f505a591071f5c5d5d3ec08ee0 is failing after 2s with no job logs exposed. This looks like a CI runner/setup blocker outside the repo. Follow-up: retry the PR once the runner issue clears.

— Codex, via `ward agent`
WARD-OUTCOME: blocked 🛑 <details><summary>details</summary> workflow: pull-requests; review summary: skipped by ~/.ward/config.yaml default Local validation is green (`ward exec test`, `pre-commit run --all-files`), but Forgejo Actions run `test / test (pull_request)` for head `b1c85c3c5610c8f505a591071f5c5d5d3ec08ee0` is failing after 2s with no job logs exposed. This looks like a CI runner/setup blocker outside the repo. Follow-up: retry the PR once the runner issue clears. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
Merge remote-tracking branch 'origin/main' into issue-895
All checks were successful
test / test (pull_request) Successful in 36s
Details
de13738334 
# Conflicts:
#	cmd/ward/agent_director.go
Merge remote-tracking branch 'origin/main' into issue-895
All checks were successful
test / test (pull_request) Successful in 30s
Details
c389983ee0 
# Conflicts:
#	cmd/ward/agent_director.go
#	docs/FEATURES.md
coilyco-ops referenced this pull request from a commit 2026-07-10 06:21:21 +00:00
Merge pull request #906
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
pressure-test
Cold-read release pressure-test findings and coordination

  
sunday-sprint
Burn-down by Sunday 2026-06-07

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
pressure-test
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/ward!906
No description provided.