Scrub coily references as part of coily retirement #116

New issue

Closed

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

coilyco-ops commented

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

src/, tests/, .agents/
.claude/lockdown-deny.sh still exec coily hook pre-tool-use
.coily/ config dir

Note: Lockdown still routes through coily here. Regenerate to ward hook pre-tool-use (a ward setup / CI step) before relying on the guard on a coily-free host.

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 - `src/`, `tests/`, `.agents/` - `.claude/lockdown-deny.sh` still `exec coily hook pre-tool-use` - `.coily/` config dir **Note:** Lockdown still routes through coily here. Regenerate to `ward hook pre-tool-use` (a `ward setup` / CI step) before relying on the guard on a coily-free host. ## 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 commented

2026-07-02 02:24:48 +00:00

Author

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-repo-recall-116 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-02T02:24:45Z). 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 --driver claude` — container `engineer-claude-repo-recall-116` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-02T02:24:45Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-07-02 02:38:56 +00:00

chore: scrub coily references for coily retirement

coilysiren closed this issue

2026-07-02 02:38:56 +00:00

coilysiren commented

2026-07-02 02:39:42 +00:00

Owner

WARD-OUTCOME: done - scrubbed the coily tool surface to ward/ward-kdl (allowlist, audit dir default ~~/.coily→~~/.ward, docs, fixtures) and dropped the stale .coily/ dir.

The scrub itself was mostly mechanical, but the interesting part was triage: git grep coily also matches coilysiren, coilyco-*, and forgejo.coilysiren.me, so most hits were org/user/host names that must stay. The real target was the narrow set of coily-the-tool references. Three historical mentions survive on purpose and are justified in the commit: two captured GitHub API fixtures (frozen commit/PR bodies with coily:// audit trailers) and the real milestone titled "coily to ward consolidation".

The one genuinely functional change was the cli-guard audit-dir default moving from ~/.coily/audit to ~/.ward/audit, confirmed against ward's own audit doc (~/.ward/audit/<slug>.jsonl). Everything else was strings, comments, and allowlist entries.

What fought back was the environment, not the code: no Rust toolchain was preinstalled (installed rustup to run fmt/clippy/tests), the smoke-test linker got OOM-killed until I dropped debuginfo, and the pinned trufflehog hook's self-updater couldn't overwrite its root-owned binary until I dropped a writable copy earlier in PATH. All 85 lib + 13 smoke + 5 mcp tests pass, clippy is clean, secret scan is clean.

Confidence is high. Rough edge worth a possible follow-up: this repo still ships the closes-issue and conventional-commit commit-msg hooks (agentic-os v0.16.0) that global doctrine says were retired from the suite — a hook-block bump could bring it in line.

WARD-OUTCOME: done - scrubbed the coily tool surface to ward/ward-kdl (allowlist, audit dir default ~/.coily→~/.ward, docs, fixtures) and dropped the stale .coily/ dir. The scrub itself was mostly mechanical, but the interesting part was triage: `git grep coily` also matches `coilysiren`, `coilyco-*`, and `forgejo.coilysiren.me`, so most hits were org/user/host names that must stay. The real target was the narrow set of `coily`-the-tool references. Three historical mentions survive on purpose and are justified in the commit: two captured GitHub API fixtures (frozen commit/PR bodies with `coily://` audit trailers) and the real milestone titled "coily to ward consolidation". The one genuinely functional change was the cli-guard audit-dir default moving from `~/.coily/audit` to `~/.ward/audit`, confirmed against ward's own audit doc (`~/.ward/audit/<slug>.jsonl`). Everything else was strings, comments, and allowlist entries. What fought back was the environment, not the code: no Rust toolchain was preinstalled (installed rustup to run fmt/clippy/tests), the smoke-test linker got OOM-killed until I dropped debuginfo, and the pinned trufflehog hook's self-updater couldn't overwrite its root-owned binary until I dropped a writable copy earlier in PATH. All 85 lib + 13 smoke + 5 mcp tests pass, clippy is clean, secret scan is clean. Confidence is high. Rough edge worth a possible follow-up: this repo still ships the `closes-issue` and `conventional-commit` commit-msg hooks (agentic-os v0.16.0) that global doctrine says were retired from the suite — a hook-block bump could bring it in line.

Commenting is not possible because the repository is archived.