Scrub coily references as part of coily retirement #21

New issue

Closed

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

coilyco-ops commented

2026-06-18 09:18:03 +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/, chart/, Makefile, lunch_money_mcp/
.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/`, `chart/`, `Makefile`, `lunch_money_mcp/` - `.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:38:48 +00:00

coilyco-ops commented

2026-07-04 17:51:23 +00:00

Author

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-lunch-money-k8s-21 on host KAI-DESKTOP-TOWER is carrying this issue (reserved 2026-07-04T17:51:17Z). 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-lunch-money-k8s-21` on host `KAI-DESKTOP-TOWER` is carrying this issue (reserved 2026-07-04T17:51:17Z). 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:03 +00:00

chore: scrub coily references for coily retirement

coilysiren closed this issue

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

coilysiren referenced this issue from a commit

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

Merge issue-21: scrub coily references (closes #21)

coilysiren commented

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

Owner

WARD-OUTCOME: done - scrubbed coily-tool refs (settings.json allowlist, dead lockdown-deny.sh, .coily/ dir, ward.yaml + AGENTS.md wording); pushed to main, closes #21.

Straightforward scrub, and the substrate repos made it easy: the .ward/ward.yaml bridge and catalog hooks were already pointing the right way, so I mostly followed the convention the substrate .claude/settings.json and ward.yaml already set (drop the coily allowlist entries, add Bash(ward:*) in alpha order, keep the header wording off "coily").

The one judgment call was separating the tool coily from the username/org coilysiren/coilyco - git grep -il coily catches both because "coily" is a substring, so I filtered those out by hand and left them intentionally. All remaining matches are identity refs (Docker Hub namespace, SSM param path, forge URLs, cross-ref links).

lockdown-deny.sh was already dead - its settings.json deny block got stripped back in e855b02 but the file itself was orphaned, still calling exec coily hook pre-tool-use, so I deleted it. pre-commit passed clean on the first run and the merge was linear. Fairly confident: no functional code touched, only config/allowlist/docs. No follow-ups worth filing.

WARD-OUTCOME: done - scrubbed coily-tool refs (settings.json allowlist, dead lockdown-deny.sh, .coily/ dir, ward.yaml + AGENTS.md wording); pushed to main, closes #21. Straightforward scrub, and the substrate repos made it easy: the .ward/ward.yaml bridge and catalog hooks were already pointing the right way, so I mostly followed the convention the substrate `.claude/settings.json` and ward.yaml already set (drop the coily allowlist entries, add `Bash(ward:*)` in alpha order, keep the header wording off "coily"). The one judgment call was separating the *tool* `coily` from the *username/org* `coilysiren`/`coilyco` - `git grep -il coily` catches both because "coily" is a substring, so I filtered those out by hand and left them intentionally. All remaining matches are identity refs (Docker Hub namespace, SSM param path, forge URLs, cross-ref links). `lockdown-deny.sh` was already dead - its settings.json deny block got stripped back in e855b02 but the file itself was orphaned, still calling `exec coily hook pre-tool-use`, so I deleted it. pre-commit passed clean on the first run and the merge was linear. Fairly confident: no functional code touched, only config/allowlist/docs. No follow-ups worth filing.

coilyco-ops added the

headless

label

2026-07-10 11:58:05 +00:00