Finish coily -> ward migration (install binary, repoint hooks + catalog, drop bridge) #30

New issue

Closed

opened 2026-06-02 05:59:27 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-02 05:59:27 +00:00

Owner

Follow-up from the Helm chart work (#25). That change started the coily -> ward migration for this coilyco-flight-deck repo.

Done so far:

.ward/ward.yaml is the canonical command allowlist (full verb set + the chart verbs docker / helm-lint / helm-template), lint-clean by construction (run == make <verb>, descriptions match each Makefile target's ## desc).
.coily/coily.yaml is kept in parallel as a transition bridge, because the ward binary is not installed on the dev hosts yet and the repo's pre-commit hooks (check-coily-yaml, catalog-block-present) plus the cross-repo catalog graph still key off .coily/coily.yaml.
AGENTS / README / FEATURES say ward is canonical, coily is the bridge.

Remaining to finish the migration:

Install the ward binary fleet-wide (brew tap coilyco-flight-deck/ward ...; brew install ...; ward install-hooks).
Repoint the pre-commit hooks from .coily/coily.yaml to .ward/ward.yaml (the agentic-os-managed hook block), and move the catalog: block to .ward/ward.yaml.
Run ward lint to confirm the verb/target/description contract holds.
Remove the .coily/coily.yaml bridge once ward is the only gate.

Operator/deploy verbs (helm install, kubectl, ssh) stay in coily and never move into ward.

Follow-up from the Helm chart work (#25). That change started the coily -> ward migration for this coilyco-flight-deck repo. Done so far: - `.ward/ward.yaml` is the canonical command allowlist (full verb set + the chart verbs `docker` / `helm-lint` / `helm-template`), lint-clean by construction (`run` == `make <verb>`, descriptions match each Makefile target's `## desc`). - `.coily/coily.yaml` is kept in parallel as a transition bridge, because the `ward` binary is not installed on the dev hosts yet and the repo's pre-commit hooks (`check-coily-yaml`, `catalog-block-present`) plus the cross-repo catalog graph still key off `.coily/coily.yaml`. - AGENTS / README / FEATURES say ward is canonical, coily is the bridge. Remaining to finish the migration: - Install the `ward` binary fleet-wide (`brew tap coilyco-flight-deck/ward ...; brew install ...; ward install-hooks`). - Repoint the pre-commit hooks from `.coily/coily.yaml` to `.ward/ward.yaml` (the agentic-os-managed hook block), and move the `catalog:` block to `.ward/ward.yaml`. - Run `ward lint` to confirm the verb/target/description contract holds. - Remove the `.coily/coily.yaml` bridge once ward is the only gate. Operator/deploy verbs (helm install, kubectl, ssh) stay in coily and never move into ward.

coilysiren added the

label

2026-06-04 08:16:41 +00:00

coilysiren commented

2026-06-17 08:23:50 +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:23:51 +00:00