Scrub coily references as part of coily retirement #182

New issue

Closed

opened 2026-06-18 09:18:05 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

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

cmd/ (~56), docs/ (~25), .forgejo/, .claude/
.claude/lockdown-deny.sh still exec coily hook pre-tool-use (the successor repo's own lockdown has not been cut over)

Note: ward intentionally documents the migration FROM coily, so many refs are deliberate. Scrub the stale/functional ones: regenerate its own lockdown to ward hook pre-tool-use, drop any compat shims no longer needed. Keep the migration narrative in docs.

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 - `cmd/` (~56), `docs/` (~25), `.forgejo/`, `.claude/` - `.claude/lockdown-deny.sh` still `exec coily hook pre-tool-use` (the successor repo's own lockdown has not been cut over) **Note:** ward intentionally documents the migration FROM coily, so many refs are deliberate. Scrub the stale/functional ones: regenerate its own lockdown to `ward hook pre-tool-use`, drop any compat shims no longer needed. Keep the migration narrative in docs. ## 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

priority

autonomy

headless

labels

2026-06-24 04:15:22 +00:00

coilyco-ops commented

2026-06-24 04:36:09 +00:00

Author

Member

🔒 Reserved by ward agent claude — container ward-ward-issue-182-claude-19dc04e3 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-06-24T04:36:08Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent claude` — container `ward-ward-issue-182-claude-19dc04e3` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-06-24T04:36:08Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`