coilyco-flight-deck/ward
2
0
Fork 0
Code Issues 105 Pull requests Projects Releases 737 Packages 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
Member
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
Member
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
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!914
No description provided.