Reflow #502 remainder: profile-gen package, seed template repo, ward adopter wiring

coilysiren commented

2026-06-04 11:04:05 +00:00

Owner

Follow-up to the agent-guard -> ward reflow (coilyco-bridge/agentic-os-kai#502). The headline of that issue (rename agent-guard -> ward + coherent cli-guard consumer-fleet naming scheme) is delivered and recorded in data/repo-split-decisions.yaml (naming_scheme block). These remaining fleet items are spun out so the umbrella can close:

Remaining

profile-gen / init package in cli-guard. Move the ward init --profile=<x> scaffolder into cli-guard as a package so every consumer (coily, ward, kap) dogfoods it transitively, instead of a separate un-dogfooded repo. ward currently has no init command.
seed template repo. Create the GitHub template repo seed - the click-to-fork skeleton for a new warded public repo, plus CI that compiles it so it does not rot. Coined name (not ward-template, which mixed the framework/consumer registers). Lifecycle: plant a seed, it grows into a ward.
Wire a first public-repo adopter onto ward. ward self-hosts its own .ward/ward.yaml, but no external public repo (cli-mcp, repo-recall, o2r, etc.) is wired onto ward yet to validate the contributor gate end to end.

Already tracked / done

app-dir de-defaulting (stop hardcoding .coily, make it consumer-supplied) is tracked in cli-guard#50.
rename + module path + binary + Formula + tap + .ward/ward.yaml + README/mission rewrite: done in the ward repo.

Follow-up to the agent-guard -> ward reflow (coilyco-bridge/agentic-os-kai#502). The headline of that issue (rename agent-guard -> ward + coherent cli-guard consumer-fleet naming scheme) is delivered and recorded in `data/repo-split-decisions.yaml` (`naming_scheme` block). These remaining fleet items are spun out so the umbrella can close: ## Remaining - [ ] **profile-gen / `init` package in cli-guard.** Move the `ward init --profile=<x>` scaffolder into cli-guard as a package so every consumer (coily, ward, kap) dogfoods it transitively, instead of a separate un-dogfooded repo. ward currently has no `init` command. - [ ] **`seed` template repo.** Create the GitHub template repo `seed` - the click-to-fork skeleton for a new warded public repo, plus CI that compiles it so it does not rot. Coined name (not `ward-template`, which mixed the framework/consumer registers). Lifecycle: plant a seed, it grows into a ward. - [ ] **Wire a first public-repo adopter onto ward.** ward self-hosts its own `.ward/ward.yaml`, but no external public repo (cli-mcp, repo-recall, o2r, etc.) is wired onto ward yet to validate the contributor gate end to end. ## Already tracked / done - app-dir de-defaulting (stop hardcoding `.coily`, make it consumer-supplied) is tracked in cli-guard#50. - rename + module path + binary + Formula + tap + `.ward/ward.yaml` + README/mission rewrite: done in the ward repo.

coilysiren added this to the sunday-sprint milestone

2026-06-05 03:41:15 +00:00

coilysiren added the

sunday-sprint

label

2026-06-05 03:41:15 +00:00

coilysiren added the

P2

label

2026-06-06 04:27:06 +00:00

coilysiren referenced this issue

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