Remove obsolete ward-kdl mount friction from native agent launches #1549
No reviewers
Labels
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/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/ward!1549
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-1546"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Native
ward agentcontrol-plane paths now stay on baked product defaults, so a stale edgeWARD_CONFIG_REFcannot trigger generated ward-kdl mount resolution or contaminate container bootstrap. Explicit generated operator surfaces still resolve their configured bundle and still surface genuine mount errors.opstree only forward ops.ward exec test,ward exec vet, andward exec lint.closes #1546
ward.workflow: pull-request-and-merge