coilyco-flight-deck/ward
Archived
Watch
2
0
Code Issues Pull requests Projects Releases 820 Packages 1 Wiki Activity Actions

fix: neutralize baked ward-kdl bundle #914

Merged
coilyco-ops merged 6 commits from issue-893 into main 2026-07-10 06:20:57 +00:00
Conversation 1 Commits 6 Files changed 6 +30 -30
coilyco-ops commented 2026-07-10 00:57:14 +00:00
Owner
Copy link

Neutralize the baked ward-kdl bundle so the shipped default is example-safe and operator-specific config comes from a selected bundle.

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

Neutralize the baked ward-kdl bundle so the shipped default is example-safe and operator-specific config comes from a selected bundle. closes #893 ward.workflow: pull-requests-and-merge
feat: neutralize baked ward-kdl bundle
Some checks failed
test / test (pull_request) Failing after 44s
Details
dc81bccdb3
fix: satisfy lint thresholds
All checks were successful
test / test (pull_request) Successful in 21s
Details
a73c0a2df6
merge origin/main into issue-893
All checks were successful
test / test (pull_request) Successful in 25s
Details
b73b15292b
coilyco-ops commented 2026-07-10 01:06:54 +00:00
Author
Owner
Copy link

NO-GO on this shape.

This PR moves in the right direction by neutralizing values, but it does not go nearly far enough. The problem is not just the concrete endpoint and token values. The whole legacy specgen bundle is still being carried in ward, including the huge .ward/ward-kdl/forgejo.swagger.v1.json payload and the custom coilyco-oriented KDL/spec assets.

The desired shape:

  • ward keeps a tiny, example-safe default bundle only, anchored on the existing examples/toy/ / examples/ward-specs/ model.
  • deployment-specific KDL and specgen assets move out of ward into aos-owned config, then get selected as a config source or overlay.
  • ward retains loader/parser/generator behavior and tests, but not Kai's custom fleet/operator bundle as tracked product source.
  • the generated docs/assets should reflect that split instead of preserving the legacy block under neutral values.

Closing this PR as superseded. The replacement work should remove the legacy bundle from ward rather than sanitize it in place.

NO-GO on this shape. This PR moves in the right direction by neutralizing values, but it does not go nearly far enough. The problem is not just the concrete endpoint and token values. The whole legacy specgen bundle is still being carried in ward, including the huge `.ward/ward-kdl/forgejo.swagger.v1.json` payload and the custom coilyco-oriented KDL/spec assets. The desired shape: * ward keeps a tiny, example-safe default bundle only, anchored on the existing `examples/toy/` / `examples/ward-specs/` model. * deployment-specific KDL and specgen assets move out of ward into aos-owned config, then get selected as a config source or overlay. * ward retains loader/parser/generator behavior and tests, but not Kai's custom fleet/operator bundle as tracked product source. * the generated docs/assets should reflect that split instead of preserving the legacy block under neutral values. Closing this PR as superseded. The replacement work should remove the legacy bundle from ward rather than sanitize it in place.
coilyco-ops closed this pull request 2026-07-10 01:07:01 +00:00
coilyco-ops reopened this pull request 2026-07-10 01:09:03 +00:00
merge origin/main into issue-893
Some checks failed
test / test (pull_request) Failing after 6s
Details
e135771911
Merge remote-tracking branch 'origin/main' into issue-893
All checks were successful
test / test (pull_request) Successful in 37s
Details
dfd352d24b 
# Conflicts:
#	cmd/ward/agent_director.go
Merge remote-tracking branch 'origin/main' into issue-893
All checks were successful
test / test (pull_request) Successful in 23s
Details
4b31068ea9 
# Conflicts:
#	cmd/ward/agent_director.go
coilyco-ops referenced this pull request from a commit 2026-07-10 06:20:57 +00:00
Merge pull request #914
Commenting is not possible because the repository is archived.
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

  
autonomy
async-consult
 A human needs to consult on the issue to upgrade it to headless

  
autonomy
epic
 This issue has many units of sub work - its size makes it meaningfully exclusive with other autonomy types

  
autonomy
headless
 The agent can perform the work on its own

  
autonomy
live-collab
 The agent and the human need to work together in realtime

  
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.

  
priority
P0
 priority tier

  
priority
P1
 priority tier

  
priority
P2
 priority tier

  
priority
P3
 priority tier

  
priority
P4
 priority tier

  
qa-fixture
Disposable issue admitted to the bounded Ward QA verification lane.

  
role/advocate
requires work from the Developer Advocate seat

  
role/director
requires work from the Portfolio Director seat

  
role/exec
requires work from the exec role

  
role/frontend
requires work from the Frontend Engineer seat

  
role/gamedev
requires work from the Game Developer seat

  
role/human
requires a person, and specifically not an agent seat

  
role/platform
requires work from the Platform Engineer seat

  
role/qa
requires work from the QA role

  
role/science
requires work from the Applied Scientist seat

  
role/sysadmin
requires work from the Systems Administrator seat

  
state
ambient
 ambient and ephemeral work, held as a maintained document rather than a queue

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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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!914
No description provided.