Scrub coily references as part of coily retirement #35

New issue

Closed

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

coilyco-ops commented

2026-06-18 09:17:54 +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

docs/, backend/, uv.lock, tests/
.coily/ config dir

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 - `docs/`, `backend/`, `uv.lock`, `tests/` - `.coily/` config dir ## 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:11 +00:00

coilyco-ops commented

2026-07-04 17:48:19 +00:00

Author

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-backend-35 on host KAI-DESKTOP-TOWER is carrying this issue (reserved 2026-07-04T17:48:13Z). 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-backend-35` on host `KAI-DESKTOP-TOWER` is carrying this issue (reserved 2026-07-04T17:48:13Z). 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:55:30 +00:00

chore: scrub coily references for coily retirement

coilysiren closed this issue

2026-07-04 17:55:30 +00:00

coilysiren commented

2026-07-04 17:56:46 +00:00

Owner

WARD-OUTCOME: done - scrubbed coily-the-tool refs (renamed root coily.yaml->ward.yaml, removed .coily/, repointed settings/AGENTS/docs at ward/ward-kdl), landed on main.

Felt clean, mostly. The trap was that coily the tool and coilysiren/coilyco the org+domain names share a prefix, so a naive git grep -il coily would have shredded legitimate names. Narrowing to a word-boundary grep minus the org/domain forms gave a tight, honest work-list of ~6 real hits.

The one thing I didn't want to guess at - what the root coily.yaml deploy-config should become - was already decided upstream: infrastructure's caddy-shortcuts script documents the config.yml -> coily.yaml -> ward.yaml chain and already prefers root ward.yaml, so the rename followed an existing convention rather than inventing one. Same for the AGENTS.md verb swaps: ward-kdl ops forgejo action ci-watch and ward-kdl ops kubectl rollout status are real guardfile verbs, not fabrications.

Only friction: my FEATURES.md poller edit tipped the doc 75 chars over the 4000-char catalog cap, so I trimmed the wording twice to land at 3999. Confidence is high - config/docs only, zero Python touched, ruff+mypy+the full catalog suite pass. Couldn't run pytest locally (this container can't provision uv's Python), but Forgejo CI runs it on the push.

One left-behind, justified: FEATURES.md still names coily once, as the retired home of the Mac-side poller. Follow-up worth filing: that poller has no named ward-era successor, so if it's genuinely gone the bullet could be dropped in a later pass.

WARD-OUTCOME: done - scrubbed coily-the-tool refs (renamed root coily.yaml->ward.yaml, removed .coily/, repointed settings/AGENTS/docs at ward/ward-kdl), landed on main. Felt clean, mostly. The trap was that `coily` the tool and `coilysiren`/`coilyco` the org+domain names share a prefix, so a naive `git grep -il coily` would have shredded legitimate names. Narrowing to a word-boundary grep minus the org/domain forms gave a tight, honest work-list of ~6 real hits. The one thing I didn't want to guess at - what the root `coily.yaml` deploy-config should become - was already decided upstream: infrastructure's caddy-shortcuts script documents the `config.yml -> coily.yaml -> ward.yaml` chain and already prefers root `ward.yaml`, so the rename followed an existing convention rather than inventing one. Same for the AGENTS.md verb swaps: `ward-kdl ops forgejo action ci-watch` and `ward-kdl ops kubectl rollout status` are real guardfile verbs, not fabrications. Only friction: my FEATURES.md poller edit tipped the doc 75 chars over the 4000-char catalog cap, so I trimmed the wording twice to land at 3999. Confidence is high - config/docs only, zero Python touched, ruff+mypy+the full catalog suite pass. Couldn't run pytest locally (this container can't provision uv's Python), but Forgejo CI runs it on the push. One left-behind, justified: FEATURES.md still names `coily` once, as the retired home of the Mac-side poller. Follow-up worth filing: that poller has no named ward-era successor, so if it's genuinely gone the bullet could be dropped in a later pass.

coilyco-ops added the

headless

label

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