Fix smart-defaults generated asset drift after defaults source change #1325

Closed
coilyco-ops wants to merge 4 commits from issue-1321 into main
Member

This syncs .ward/ward-kdl/ward-kdl.defaults.kdl with the baked defaults asset again so the embedded smart-defaults parse cleanly and the drift checks stay green.

It keeps the canonical source and generated asset aligned after the defaults update landed.

  • closes #1321
  • ward.workflow: pull-request-and-merge
  • Tests: ward exec test, pre-commit run --all-files
This syncs `.ward/ward-kdl/ward-kdl.defaults.kdl` with the baked defaults asset again so the embedded smart-defaults parse cleanly and the drift checks stay green. It keeps the canonical source and generated asset aligned after the defaults update landed. - closes #1321 - ward.workflow: pull-request-and-merge - Tests: `ward exec test`, `pre-commit run --all-files`
fix smart-defaults source drift
All checks were successful
test / test (pull_request) Successful in 1m32s
ff4975bf33
Author
Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-ward-1325 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-15T05:45:20Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)
  • Resolved: coilyco-flight-deck/ward#1325 · branch issue-1325 · harness codex · workflow pull-request-and-merge
  • Run: engineer-codex-ward-1325 · ward v0.697.0 · dispatched 2026-07-15T05:45:07Z
  • Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.697.0).

— Codex, via ward agent

<!-- ward-agent-reservation --> WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1325` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T05:45:20Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#1325` · branch `issue-1325` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1325` · ward `v0.697.0` · dispatched `2026-07-15T05:45:07Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.697.0). </details> </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
merge: update issue-1321 against main
All checks were successful
test / test (pull_request) Successful in 1m9s
63d3131bb7
Owner

Merging to unblock but this needs to be very quickly followed up with: #1326

Merging to unblock but this needs to be very quickly followed up with: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/1326
Author
Member

WARDED_WORKFLOW: #1325

details

workflow: pull-request-and-merge; review summary: review gate intentionally skipped because the temporary ward default pending brokered QA

Branch repair: merged main into issue-1321, refreshed the PR body to closes #1325, and kept the smart-defaults drift fix intact.
Feels: narrow history repair, no payload churn.
Confidence: high.
Surprise: the blocker was branch staleness, not the defaults asset.
Follow-up: none unless Forgejo regresses again.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1325 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate intentionally skipped because the temporary ward default pending brokered QA Branch repair: merged `main` into `issue-1321`, refreshed the PR body to `closes #1325`, and kept the smart-defaults drift fix intact. Feels: narrow history repair, no payload churn. Confidence: high. Surprise: the blocker was branch staleness, not the defaults asset. Follow-up: none unless Forgejo regresses again. </details>
Merge branch 'main' into issue-1321
Some checks failed
test / test (pull_request) Failing after 11m46s
9943dcd887
coilysiren closed this pull request 2026-07-15 06:04:12 +00:00
Author
Member

WARDED_WORKFLOW: blocked 🛑

details

manual close/update snapshot at 2026-07-15T06:18:00Z is newer than the latest ward acknowledgement at 2026-07-15T05:53:37Z

This action is blocked until the feedback is visibly acknowledged.

— Claude (she/her), via ward agent

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> manual close/update snapshot at 2026-07-15T06:18:00Z is newer than the latest ward acknowledgement at 2026-07-15T05:53:37Z This action is blocked until the feedback is visibly acknowledged. </details> <!-- ward-agent-signature --> — Claude (she/her), via `ward agent`
Author
Member

WARDED_WORKFLOW: blocked 🛑

details

manual close/update snapshot at 2026-07-15T06:18:00Z is newer than the latest ward acknowledgement at 2026-07-15T05:53:37Z

This action is blocked until the feedback is visibly acknowledged.

— Claude (she/her), via ward agent

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> manual close/update snapshot at 2026-07-15T06:18:00Z is newer than the latest ward acknowledgement at 2026-07-15T05:53:37Z This action is blocked until the feedback is visibly acknowledged. </details> <!-- ward-agent-signature --> — Claude (she/her), via `ward agent`
coilyco-ops reopened this pull request 2026-07-15 07:52:52 +00:00
retrigger PR 1325 after Forgejo lint failure
All checks were successful
test / test (pull_request) Successful in 1m47s
53f67b0274
coilyco-ops closed this pull request 2026-07-15 08:16:24 +00:00
All checks were successful
test / test (pull_request) Successful in 1m47s

Pull request closed

Sign in to join this conversation.
No description provided.