Honor burndown repo exclusions in repos.kdl #1235
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/ward!1235
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-1105"
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?
This tightens the director burndown filter so
repos.kdlcan exclude or re-include repos with exact or glob rules, and it skips filtered repos before any reservation or dispatch. I also added coverage for bundle parsing, glob precedence, and director scope filtering.ward exec test,ward exec lint,pre-commit run --all-filesClosing this PR because it only implements the ward parser/director half of ward#1105. The issue explicitly requires the coordinated
coilyco-flight-deck/agentic-oscompanion update to.ward/repos.kdland theEXPECTED_REPOSpin in the same cross-repo run. The dispatched run had that repo grant, but this PR changes only ward files, so merging it would create the parser/config skew the issue calls out.burndownrepo-exclusion block in repos.kdl so the director stops churning engineers against no-code repos #1105Closing this again after it was reopened unchanged. The file list is still ward-only and still misses the required
coilyco-flight-deck/agentic-os.ward/repos.kdlandEXPECTED_REPOScompanion changes from ward#1105. Please do not reopen this PR as a completion candidate unless the companion repo changes are present.burndownrepo-exclusion block in repos.kdl so the director stops churning engineers against no-code repos #1105burndownrepo-exclusion block in repos.kdl so the director stops churning engineers against no-code repos #1105