Scrub coily references as part of coily retirement #1

New issue

Closed

opened 2026-06-18 09:18:00 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-06-18 09:18:00 +00:00

Member

What

Scrub coily references from this repo as part of retiring coily in favor of ward / ward-kdl. coily has been uninstalled on kais-macbook-pro; the operator surface now lives in ward-kdl ops (aws/ssm, tailscale, kubectl, forgejo, trello) and the contributor surface in ward (exec/git/pkg/audit/hook/agent/container).

Where coily refs live in this repo

Formula/ (the coily formula itself, ~4), docs/, AGENTS.md, README.md
.coily/ config dir

Note: This repo ships the coily Homebrew formula. Removing the formula is the final step of full retirement. Coordinate so every consumer is cut over before the formula is pulled, otherwise brew install coily breaks for other hosts (e.g. kai-server still needs it for gaming).

Acceptance

Functional refs (configs, scripts, allowlists, hooks, CI) no longer assume coily is installed.
Doc / skill / AGENTS refs updated to point at ward or ward-kdl as appropriate.
git grep -il coily returns only intentional/historical mentions, each justified.

Context

Part of the coily to ward/ward-kdl cutover. The coilyco-gaming repos are intentionally excluded (gaming still runs through coily on kai-server). Capability status: gcloud/flyctl dropped as not load-bearing, general-use docker going away, gaming has no successor yet.

## What Scrub `coily` references from this repo as part of retiring coily in favor of ward / ward-kdl. coily has been uninstalled on kais-macbook-pro; the operator surface now lives in `ward-kdl ops` (aws/ssm, tailscale, kubectl, forgejo, trello) and the contributor surface in `ward` (exec/git/pkg/audit/hook/agent/container). ## Where coily refs live in this repo - `Formula/` (the coily formula itself, ~4), `docs/`, `AGENTS.md`, `README.md` - `.coily/` config dir **Note:** This repo ships the coily Homebrew formula. Removing the formula is the final step of full retirement. Coordinate so every consumer is cut over before the formula is pulled, otherwise `brew install coily` breaks for other hosts (e.g. kai-server still needs it for gaming). ## Acceptance - Functional refs (configs, scripts, allowlists, hooks, CI) no longer assume coily is installed. - Doc / skill / AGENTS refs updated to point at ward or ward-kdl as appropriate. - `git grep -il coily` returns only intentional/historical mentions, each justified. ## Context Part of the coily to ward/ward-kdl cutover. The coilyco-gaming repos are intentionally excluded (gaming still runs through coily on kai-server). Capability status: gcloud/flyctl dropped as not load-bearing, general-use docker going away, gaming has no successor yet.

coilyco-ops added the

label

2026-07-04 17:37:59 +00:00

coilyco-ops commented

2026-07-04 17:50:50 +00:00

Author

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-homebrew-tap-1 on host KAI-DESKTOP-TOWER is carrying this issue (reserved 2026-07-04T17:50:45Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-homebrew-tap-1` on host `KAI-DESKTOP-TOWER` is carrying this issue (reserved 2026-07-04T17:50:45Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh** — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-07-04 17:54:02 +00:00

chore: scrub coily references in favor of ward / ward-kdl

coilysiren closed this issue

2026-07-04 17:54:02 +00:00

coilysiren referenced this issue from a commit

2026-07-04 17:54:02 +00:00

Merge branch 'issue-1': scrub coily references (closes #1)

coilysiren commented

2026-07-04 17:54:41 +00:00

Owner

WARD-OUTCOME: done - migrated .coily/coily.yaml -> .ward/ward.yaml and repointed every coily doc/AGENTS/formula-comment ref to ward / ward-kdl; landed on main.

This one was smaller than the issue body implied, which was the main surprise. The issue expected "the coily formula itself, ~4" refs living in Formula/, but this tap ships no coily.rb at all - the formulae are ward, repo-recall, and session-lattice (+puller). So there was no installable formula to pull, and the "coordinate consumer cutover before removing the formula" caveat did not apply here. The real work was: move the .coily/ config dir to .ward/, and swap the routing prose in AGENTS.md / README.md / docs/FEATURES.md plus two comment lines in session-lattice.rb.

The one judgment call worth naming: most coily substring hits in this repo are coilyco-flight-deck (the org slug) and coilysiren (the forge host and a home-dir path), which are load-bearing and stay. I only scrubbed standalone coily-the-tool references. git grep -iw coily is now empty; the remaining substring matches are all org/host names, each justified.

Confidence is high. No CI or pre-commit gate in this repo to run, the diff is text-only, and a clean main fetch confirms the push landed.

One rough edge / follow-up: session-lattice.rb carries # BEGIN RESOURCES (managed by ward exec brew-resources), which I rewrote from coily exec. If the upstream session-lattice release pipeline still emits that block with the old coily exec marker, the next resources regen will reintroduce it. Worth confirming session-lattice upstream is cut over to ward before assuming this stays clean.

WARD-OUTCOME: done - migrated .coily/coily.yaml -> .ward/ward.yaml and repointed every coily doc/AGENTS/formula-comment ref to ward / ward-kdl; landed on main. This one was smaller than the issue body implied, which was the main surprise. The issue expected "the coily formula itself, ~4" refs living in `Formula/`, but this tap ships no `coily.rb` at all - the formulae are ward, repo-recall, and session-lattice (+puller). So there was no installable formula to pull, and the "coordinate consumer cutover before removing the formula" caveat did not apply here. The real work was: move the `.coily/` config dir to `.ward/`, and swap the routing prose in AGENTS.md / README.md / docs/FEATURES.md plus two comment lines in session-lattice.rb. The one judgment call worth naming: most `coily` substring hits in this repo are `coilyco-flight-deck` (the org slug) and `coilysiren` (the forge host and a home-dir path), which are load-bearing and stay. I only scrubbed standalone `coily`-the-tool references. `git grep -iw coily` is now empty; the remaining substring matches are all org/host names, each justified. Confidence is high. No CI or pre-commit gate in this repo to run, the diff is text-only, and a clean `main` fetch confirms the push landed. One rough edge / follow-up: session-lattice.rb carries `# BEGIN RESOURCES (managed by ward exec brew-resources)`, which I rewrote from `coily exec`. If the upstream session-lattice release pipeline still emits that block with the old `coily exec` marker, the next resources regen will reintroduce it. Worth confirming session-lattice upstream is cut over to ward before assuming this stays clean.

coilyco-ops added the

headless

label

2026-07-10 11:57:50 +00:00