ward-kdl: wire to the kin-openapi parse layer (bump cli-guard REF + re-lock) #76

New issue

Closed

opened 2026-06-09 06:24:04 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-09 06:24:04 +00:00

Owner

Follow-up to ward#74 (engine decision) and the cli-guard tracer f31117f.

Context

The kin-openapi parse layer landed on cli-guard branch feat/specverb-kin-parse-layer. ward-kdl still builds against the released cli-guard pinned in cmd/ward-kdl/specverb.lock and Makefile (REF ?= v0.6.0), so it does not yet exercise the new parse layer.

The work

Land cli-guard feat/specverb-kin-parse-layer on cli-guard main (cuts a minor release tag).
Bump ward's Makefile REF to the new cli-guard tag.
Re-run make lock so specverb.lock resolves the new module graph, and rebuild ward-kdl.
Confirm ward-kdl ops forgejo org create --username probe --dry-run --output json still emits the resolved POST /api/v1/orgs request, now through the kin parse layer.

Note

This is the rollout half of the authoring-vs-rollout split: the parse-layer logic is authored in cli-guard, this issue pulls it down the dependency arrow into ward. No carve-out, just the normal consumer self-bump off a cli-guard tag.

Follow-up to ward#74 (engine decision) and the cli-guard tracer `f31117f`. ## Context The kin-openapi parse layer landed on cli-guard branch `feat/specverb-kin-parse-layer`. ward-kdl still builds against the released cli-guard pinned in `cmd/ward-kdl/specverb.lock` and `Makefile` (`REF ?= v0.6.0`), so it does not yet exercise the new parse layer. ## The work 1. Land cli-guard `feat/specverb-kin-parse-layer` on cli-guard main (cuts a minor release tag). 2. Bump ward's `Makefile` `REF` to the new cli-guard tag. 3. Re-run `make lock` so `specverb.lock` resolves the new module graph, and rebuild ward-kdl. 4. Confirm `ward-kdl ops forgejo org create --username probe --dry-run --output json` still emits the resolved `POST /api/v1/orgs` request, now through the kin parse layer. ## Note This is the rollout half of the authoring-vs-rollout split: the parse-layer logic is authored in cli-guard, this issue pulls it down the dependency arrow into ward. No carve-out, just the normal consumer self-bump off a cli-guard tag.

coilysiren referenced this issue

2026-06-15 15:22:05 +00:00

Epic: coily -> ward -> ward-kdl consolidation (umbrella) #91

coilysiren added this to the coily to ward to ward-kdl consolidation milestone

2026-06-15 15:31:11 +00:00

coilysiren added the

label

2026-06-17 07:05:39 +00:00

coilysiren commented

2026-06-17 08:21:58 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:21:59 +00:00