coilyco-flight-deck/agentic-os

Fork 0

Scrub coily references as part of coily retirement #256

New issue

Closed

opened 2026-06-18 09:17:53 +00:00 by coilyco-ops · 3 comments

coilyco-ops commented

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

.agents/ skills (~53), agentic_os/ validators (~18), docs/, warp/, scripts/
.claude/lockdown-deny.sh still exec coily hook pre-tool-use
.ward/ward.yaml / settings allowlist entries (Bash(coily:*), coily ops ...)

Note: The git-credential helper subset is already tracked in #255 . This issue covers the rest: regenerate the lockdown to ward hook pre-tool-use (a ward setup / CI step), the settings allowlist, the warp/ and agentic_os/ refs, and AGENTS/skill 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 - `.agents/` skills (~53), `agentic_os/` validators (~18), `docs/`, `warp/`, `scripts/` - `.claude/lockdown-deny.sh` still `exec coily hook pre-tool-use` - `.ward/ward.yaml` / settings allowlist entries (`Bash(coily:*)`, `coily ops ...`) **Note:** The git-credential helper subset is already tracked in https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/issues/255 . This issue covers the rest: regenerate the lockdown to `ward hook pre-tool-use` (a `ward setup` / CI step), the settings allowlist, the warp/ and agentic_os/ refs, and AGENTS/skill 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

interactive

labels

2026-06-24 06:13:04 +00:00

coilysiren referenced this issue from a commit

2026-06-24 06:47:21 +00:00

feat(ward-ops): eager-context pointer + committed describe dump for ward-kdl

coilyco-ops added

headless

and removed

interactive

labels

2026-06-25 09:09:24 +00:00

coilyco-ops commented

2026-06-25 09:51:10 +00:00

Author

Member

🔁 backlog-loop dispatch - this issue was auto-dispatched by the supervised backlog loop.

When you finish, your final issue comment must start with exactly one of:

WARD-OUTCOME: done - landed/merged, nothing more needed.
WARD-OUTCOME: blocked - <the specific decision or information you need from a human>
WARD-OUTCOME: failed - <why, briefly>

Put your candid retrospective on the line(s) below it. The supervising loop reads this
line to decide whether to close you out, ask a human to unblock you, or retry. If you
are blocked, be concrete about the single thing you need - that is what gets answered.

🔁 **backlog-loop dispatch** - this issue was auto-dispatched by the supervised backlog loop. When you finish, your **final issue comment** must start with exactly one of: - `WARD-OUTCOME: done` - landed/merged, nothing more needed. - `WARD-OUTCOME: blocked - <the specific decision or information you need from a human>` - `WARD-OUTCOME: failed - <why, briefly>` Put your candid retrospective on the line(s) below it. The supervising loop reads this line to decide whether to close you out, ask a human to unblock you, or retry. If you are blocked, be concrete about the single thing you need - that is what gets answered.

coilyco-ops commented

2026-06-25 09:51:13 +00:00

Author

Member

🔒 Reserved by ward agent --driver claude — container ward-agentic-os-issue-256-claude-88c45640 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-06-25T09:51:12Z). 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 `ward-agentic-os-issue-256-claude-88c45640` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-06-25T09:51:12Z). 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-06-25 09:56:53 +00:00

docs(release): drop retired coily from the fleet-consumer example

coilysiren closed this issue

2026-06-25 09:56:53 +00:00

coilysiren commented

2026-06-25 09:57:17 +00:00

Owner

WARD-OUTCOME: done

Honest retrospective: this one was mostly archaeology, not surgery. I went in expecting the surface the issue describes (lockdown hook, ward.yaml allowlist, Bash(coily:), warp/, agentic_os/) and found it already cut over by sibling work that landed after this issue was filed - c8fd757 removed the coily tool dependency and 1ab2b55 rerouted scout hydration through ward-kdl. So the real job was distinguishing the retired coily CLI from the org/host names that share the substring (coilyco-, coilysiren, forgejo.coilysiren.me) and from the coily*/* filesystem globs over the repo family. A case-insensitive git grep -il coily still returns ~162 files, but a \bcoily\b pass that strips the org names leaves only justified hits: repo-family globs (shell/common.sh, kai-gish), the coily* owner-gate value in ward-kdl's restrict rule, and explicit "retired/deprecated/old" historical notes.

What actually fought back: almost nothing, which is itself the surprise - the one genuine straggler was docs/release.md listing coily as a current consumer of the shipped composite actions, so I swapped it for ward-kdl. Confidence is high; pre-commit is green and the residual is all defensible. Rough edge worth noting: the issue's "where coily refs live" section had already gone stale against main by the time I picked it up, so a chunk of the work was confirming a negative rather than changing code. No follow-ups needed.

WARD-OUTCOME: done Honest retrospective: this one was mostly archaeology, not surgery. I went in expecting the surface the issue describes (lockdown hook, ward.yaml allowlist, Bash(coily:*), warp/, agentic_os/) and found it already cut over by sibling work that landed after this issue was filed - c8fd757 removed the coily tool dependency and 1ab2b55 rerouted scout hydration through ward-kdl. So the real job was distinguishing the retired `coily` CLI from the org/host names that share the substring (coilyco-*, coilysiren, forgejo.coilysiren.me) and from the `coily*/*` filesystem globs over the repo family. A case-insensitive `git grep -il coily` still returns ~162 files, but a `\bcoily\b` pass that strips the org names leaves only justified hits: repo-family globs (shell/common.sh, kai-gish), the `coily*` owner-gate value in ward-kdl's restrict rule, and explicit "retired/deprecated/old" historical notes. What actually fought back: almost nothing, which is itself the surprise - the one genuine straggler was docs/release.md listing coily as a *current* consumer of the shipped composite actions, so I swapped it for ward-kdl. Confidence is high; pre-commit is green and the residual is all defensible. Rough edge worth noting: the issue's "where coily refs live" section had already gone stale against main by the time I picked it up, so a chunk of the work was confirming a negative rather than changing code. No follow-ups needed.