Roll ward-kdl to cli-guard v0.13.0 + sync ops-forgejo.md #85

New issue

Closed

opened 2026-06-11 01:24:36 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-11 01:24:36 +00:00

Owner

Manual cli-guard release v0.13.0 cut (the auto-pipeline lagged), so roll ward-kdl onto the clean tag and clean up the out-of-sync docs.

Makefile: REF pinned from the commit pseudo-version to v0.13.0; re-locked (specverb.lock cliGuard now v0.13.0, spec lock unchanged).
docs/ops-forgejo.md: rewritten to match current reality - no isolated Go module / committed go.mod/go.sum (the build materializes out-of-band), the full 40-leaf forgejo surface (not the orgs-only proving slice), the pruned spec lock, and make build-ward-kdl.

Manual cli-guard release v0.13.0 cut (the auto-pipeline lagged), so roll ward-kdl onto the clean tag and clean up the out-of-sync docs. - `Makefile`: REF pinned from the commit pseudo-version to `v0.13.0`; re-locked (`specverb.lock` cliGuard now `v0.13.0`, spec lock unchanged). - `docs/ops-forgejo.md`: rewritten to match current reality - no isolated Go module / committed `go.mod`/`go.sum` (the build materializes out-of-band), the full 40-leaf forgejo surface (not the orgs-only proving slice), the pruned spec lock, and `make build-ward-kdl`.

coilysiren referenced this issue from a commit

2026-06-11 01:24:51 +00:00

build(ward-kdl): roll to cli-guard v0.13.0 and sync ops-forgejo.md

coilysiren closed this issue

2026-06-11 01:24:51 +00:00

~~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:13 +00:00