Adopt the ward-kdl multi-guardfile merge convention #83

New issue

Closed

opened 2026-06-11 00:39:27 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-11 00:39:27 +00:00

Owner

Adopt the multi-guardfile merge convention now that specverb-gen merges guardfiles by wrap binary name (cli-guard#133).

Rename cmd/ward-kdl/ward-kdl.guardfile.kdl -> ward-kdl.forgejo.guardfile.kdl and its reference doc to ward-kdl.forgejo.guardfile.md (the ward-kdl.<api>.guardfile.kdl convention).
Makefile build-ward-kdl points at the renamed guardfile; the driver discovers and merges every sibling sharing the wrap ward-kdl name, so a new API is one new Guardfile with no Makefile change.
pyproject.toml + .gitignore track the renamed doc; docs/ops-forgejo.md documents the merge.

Adding a real second API (its own ward-kdl.<api>.guardfile.kdl against a lockable spec) is the natural follow-up.

Adopt the multi-guardfile merge convention now that specverb-gen merges guardfiles by `wrap` binary name (cli-guard#133). - Rename `cmd/ward-kdl/ward-kdl.guardfile.kdl` -> `ward-kdl.forgejo.guardfile.kdl` and its reference doc to `ward-kdl.forgejo.guardfile.md` (the `ward-kdl.<api>.guardfile.kdl` convention). - Makefile `build-ward-kdl` points at the renamed guardfile; the driver discovers and merges every sibling sharing the `wrap ward-kdl` name, so a new API is one new Guardfile with no Makefile change. - pyproject.toml + .gitignore track the renamed doc; docs/ops-forgejo.md documents the merge. Adding a real second API (its own `ward-kdl.<api>.guardfile.kdl` against a lockable spec) is the natural follow-up.

coilysiren referenced this issue from a commit

2026-06-11 00:40:12 +00:00

feat(ward-kdl): adopt multi-guardfile merge convention

coilysiren closed this issue

2026-06-11 00:40:12 +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