Make ward-kdl.defaults.kdl the exclusive smart-defaults source of truth #1318

Merged
coilysiren merged 1 commit from issue-1312 into main 2026-07-15 04:57:51 +00:00
Member

Make .ward/ward-kdl/ward-kdl.defaults.kdl the 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.

  • closes #1312
  • ward.workflow: pull-request-and-merge
  • Tests: env -u WARD_CONFIG_REF go test ./...; pre-commit run --all-files
  • Notes: help text points at the bundled defaults file, and the generated defaults asset is checked against the canonical KDL
Make `.ward/ward-kdl/ward-kdl.defaults.kdl` the 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. - closes #1312 - ward.workflow: pull-request-and-merge - Tests: `env -u WARD_CONFIG_REF go test ./...`; `pre-commit run --all-files` - Notes: help text points at the bundled defaults file, and the generated defaults asset is checked against the canonical KDL
fix: make smart defaults canonical
All checks were successful
test / test (pull_request) Successful in 1m10s
f7a6975325
Author
Member

WARDED_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: blocked 🛑 <details><summary>details</summary> 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. <!-- ward-agent-signature --> </details>
Author
Member

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

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1318 <details><summary>details</summary> 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 <!-- ward-agent-signature --> </details>
Sign in to join this conversation.
No description provided.