Remove stale ward specs bundle validator #503
Labels
No labels
burndown-2026-06
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/agentic-os#503
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Remove the stale ward specs bundle pre-commit validator and all hardcoded bundle-path test residue.
Context:
agentic_os/pre_commit/check_ward_specs_bundle.pyshould not exist anymore.27eccc205a1c76d9fff3996f0ca545e988f9b4f7moved tests away from encoding config values, but a simple grep still finds stale bundle/default path coupling.rg -n "check_ward_specs_bundle|ward\\.bundle|ward specs bundle|bundle\\.kdl|defaults\\.kdl|workflow\\.kdl" .agentic_os/pre_commit/check_ward_specs_bundle.pytests/test_ward_specs_bundle.pyRequired fix:
agentic_os/pre_commit/check_ward_specs_bundle.pyentirely.tests/test_ward_specs_bundle.pycontent that is only testing hardcoded config paths.ward doctor, not pytest assertions against KDL paths or literals.check_ward_specs_bundleward.bundle.kdldefaults.kdlwhere it means the old workflow/defaults fileward-kdl.defaults.kdlward specs bundlewhere the wording no longer matches the live model.ward/defaults.kdlto.ward/workflow.kdland the move fromdefaults.agent-workflowto a top-levelworkflowblock. If that change has already landed, this fix should build on it. If it has not landed, preserve compatibility only where genuinely necessary and call out any follow-up.Acceptance:
agentic_os/pre_commit/check_ward_specs_bundle.pyis gone.ward doctorremains the config-validity gate.WARD-OUTCOME: submitted
details
workflow: pull-request-and-merge; review summary: skip - in-container review gate intentionally skipped because the temporary ward default pending brokered QA
felt: straightforward cleanup, no config behavior changed
confidence: high
surprises: none after the live workflow rename had already landed
follow-ups: director merge once the PR stays green