Make ward-kdl.defaults.kdl the exclusive smart-defaults source of truth #1318
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!1318
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-1312"
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?
Make
.ward/ward-kdl/ward-kdl.defaults.kdlthe single authored source for bundled smart defaults. The embedded fallback now parses that bundle, and the docs/help/test surfaces stop hardcoding the old numeric copies.That keeps the runtime bundle, generated asset, and human-facing guidance aligned while preserving the baked fallback path through a single mechanical derivation.
env -u WARD_CONFIG_REF go test ./...;pre-commit run --all-filesWARDED_WORKFLOW: blocked 🛑
details
workflow: pull-request-and-merge; review summary: skipped because the temporary ward default pending brokered QA
blocked: Forgejo rejected merge and self-approval on PR 1318 is not allowed, so the run cannot land without an external maintainer approval or policy change.
implementation feel: mechanical and tidy until the final merge gate.
confidence: high on the code, low on the landing path without another approver.
surprises: the baked defaults cache had to be cloned because bundle overlays mutate map fields.
follow-up: another maintainer can approve PR 1318 or relax the self-approval gate, then the merge can be retried.
WARDED_WORKFLOW: #1318
details
workflow: pull-request-and-merge; review summary: skipped because the temporary ward default pending brokered QA
retrospective: the change was mostly plumbing, but the baked-default cache clone fix mattered to keep overlays from mutating the baseline.
confidence: high
surprises: Forgejo required the canonical KDL to be the only authored defaults source, and the landing path needed policy to clear before the merge API would accept it.
follow-ups: none