Scrub retired coily CLI refs from infrastructure #476

New issue

Closed

opened 2026-07-08 10:03:50 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-08 10:03:50 +00:00

Member

Goal

Scrub retired coily CLI references from infrastructure where they are no longer intentional, while preserving explicitly documented kai-server coily-retention paths until their successors exist.

Context

A director hard-search for retired command/config spellings across mounted repos found infrastructure-specific leftovers. Global tracker: coilysiren/inbox#156.

Search pattern:

coily ops|coily exec|coily pkg|coily ansible|\bcoily\s+(ops|exec|pkg|ansible|agent|audit|setup|lint|test|vet|build|run|git)|\.coily|coily\.yaml|COILY_ROOT|coily-trailer

High-signal infrastructure hits from the mounted sample:

scripts/provision-coilyco-ops-bot.sh uses coily ops aws ssm get-parameter and put-parameter.
scripts/coilysiren-tangled-knot-autodeploy.sh uses coily pkg nix build.
scripts/generate-caddy-shortcuts.py still treats coily.yaml as a first-class shortcut source. Decide whether that remains a migration fallback or should be ward-only now.
Docs mention old coily setup surfaces in places that may mislead fresh agents.

Intentional-retention candidates, do not delete blindly:

scripts/coily-update.sh and systemd/coily-update.service are documented in docs/systemd-units.md as kai-server coily-retention while gaming still needs coily.
systemd/coily-audit-dashboard.service is documented as retained because coily audit has no ward successor.

Desired end state

Runtime scripts no longer depend on retired coily ops / coily pkg where ward ops, ward pkg, or a direct lower-layer command is the intended successor.
Any retained coily paths are explicitly documented as intentional retention with a linked successor/retirement issue.
Infrastructure docs no longer imply generic host setup or agents should use coily for current operator surfaces.
git grep -n for the retired-command pattern returns only intentional/historical references, each easy to justify.

Validation

Run the repo's ward/pre-commit validation.
Include the final grep summary in the closing comment.

## Goal Scrub retired `coily` CLI references from infrastructure where they are no longer intentional, while preserving explicitly documented kai-server coily-retention paths until their successors exist. ## Context A director hard-search for retired command/config spellings across mounted repos found infrastructure-specific leftovers. Global tracker: coilysiren/inbox#156. Search pattern: ```text coily ops|coily exec|coily pkg|coily ansible|\bcoily\s+(ops|exec|pkg|ansible|agent|audit|setup|lint|test|vet|build|run|git)|\.coily|coily\.yaml|COILY_ROOT|coily-trailer ``` High-signal infrastructure hits from the mounted sample: * `scripts/provision-coilyco-ops-bot.sh` uses `coily ops aws ssm get-parameter` and `put-parameter`. * `scripts/coilysiren-tangled-knot-autodeploy.sh` uses `coily pkg nix build`. * `scripts/generate-caddy-shortcuts.py` still treats `coily.yaml` as a first-class shortcut source. Decide whether that remains a migration fallback or should be ward-only now. * Docs mention old coily setup surfaces in places that may mislead fresh agents. Intentional-retention candidates, do not delete blindly: * `scripts/coily-update.sh` and `systemd/coily-update.service` are documented in `docs/systemd-units.md` as kai-server coily-retention while gaming still needs coily. * `systemd/coily-audit-dashboard.service` is documented as retained because `coily audit` has no ward successor. ## Desired end state * Runtime scripts no longer depend on retired `coily ops` / `coily pkg` where `ward ops`, `ward pkg`, or a direct lower-layer command is the intended successor. * Any retained `coily` paths are explicitly documented as intentional retention with a linked successor/retirement issue. * Infrastructure docs no longer imply generic host setup or agents should use `coily` for current operator surfaces. * `git grep -n` for the retired-command pattern returns only intentional/historical references, each easy to justify. ## Validation * Run the repo's ward/pre-commit validation. * Include the final grep summary in the closing comment.

coilyco-ops added the

headless

label

2026-07-08 10:04:02 +00:00

coilyco-ops commented

2026-07-08 10:04:17 +00:00

Author

Member

🔒 Reserved by ward agent --harness codex — container engineer-codex-infrastructure-476 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-08T10:04:15Z). 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).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/infrastructure#476 · branch issue-476 · harness codex · workflow direct-main
Run: engineer-codex-infrastructure-476 · ward v0.444.0 · dispatched 2026-07-08T10:04:15Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Issue body as seeded:

## Goal

Scrub retired `coily` CLI references from infrastructure where they are no longer intentional, while preserving explicitly documented kai-server coily-retention paths until their successors exist.

## Context

A director hard-search for retired command/config spellings across mounted repos found infrastructure-specific leftovers. Global tracker: coilysiren/inbox#156.

Search pattern:

` ` `text
coily ops|coily exec|coily pkg|coily ansible|\bcoily\s+(ops|exec|pkg|ansible|agent|audit|setup|lint|test|vet|build|run|git)|\.coily|coily\.yaml|COILY_ROOT|coily-trailer
` ` `

High-signal infrastructure hits from the mounted sample:

* `scripts/provision-coilyco-ops-bot.sh` uses `coily ops aws ssm get-parameter` and `put-parameter`.
* `scripts/coilysiren-tangled-knot-autodeploy.sh` uses `coily pkg nix build`.
* `scripts/generate-caddy-shortcuts.py` still treats `coily.yaml` as a first-class shortcut source. Decide whether that remains a migration fallback or should be ward-only now.
* Docs mention old coily setup surfaces in places that may mislead fresh agents.

Intentional-retention candidates, do not delete blindly:

* `scripts/coily-update.sh` and `systemd/coily-update.service` are documented in `docs/systemd-units.md` as kai-server coily-retention while gaming still needs coily.
* `systemd/coily-audit-dashboard.service` is documented as retained because `coily audit` has no ward successor.

## Desired end state

* Runtime scripts no longer depend on retired `coily ops` / `coily pkg` where `ward ops`, `ward pkg`, or a direct lower-layer command is the intended successor.
* Any retained `coily` paths are explicitly documented as intentional retention with a linked successor/retirement issue.
* Infrastructure docs no longer imply generic host setup or agents should use `coily` for current operator surfaces.
* `git grep -n` for the retired-command pattern returns only intentional/historical references, each easy to justify.

## Validation

* Run the repo's ward/pre-comm

… (truncated to 2000 chars; full body is on this issue)

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.444.0).

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-infrastructure-476` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-08T10:04:15Z). 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). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/infrastructure#476` · branch `issue-476` · harness `codex` · workflow `direct-main` - **Run:** `engineer-codex-infrastructure-476` · ward `v0.444.0` · dispatched `2026-07-08T10:04:15Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). **Issue body as seeded:** ``` ## Goal Scrub retired `coily` CLI references from infrastructure where they are no longer intentional, while preserving explicitly documented kai-server coily-retention paths until their successors exist. ## Context A director hard-search for retired command/config spellings across mounted repos found infrastructure-specific leftovers. Global tracker: coilysiren/inbox#156. Search pattern: ` ` `text coily ops|coily exec|coily pkg|coily ansible|\bcoily\s+(ops|exec|pkg|ansible|agent|audit|setup|lint|test|vet|build|run|git)|\.coily|coily\.yaml|COILY_ROOT|coily-trailer ` ` ` High-signal infrastructure hits from the mounted sample: * `scripts/provision-coilyco-ops-bot.sh` uses `coily ops aws ssm get-parameter` and `put-parameter`. * `scripts/coilysiren-tangled-knot-autodeploy.sh` uses `coily pkg nix build`. * `scripts/generate-caddy-shortcuts.py` still treats `coily.yaml` as a first-class shortcut source. Decide whether that remains a migration fallback or should be ward-only now. * Docs mention old coily setup surfaces in places that may mislead fresh agents. Intentional-retention candidates, do not delete blindly: * `scripts/coily-update.sh` and `systemd/coily-update.service` are documented in `docs/systemd-units.md` as kai-server coily-retention while gaming still needs coily. * `systemd/coily-audit-dashboard.service` is documented as retained because `coily audit` has no ward successor. ## Desired end state * Runtime scripts no longer depend on retired `coily ops` / `coily pkg` where `ward ops`, `ward pkg`, or a direct lower-layer command is the intended successor. * Any retained `coily` paths are explicitly documented as intentional retention with a linked successor/retirement issue. * Infrastructure docs no longer imply generic host setup or agents should use `coily` for current operator surfaces. * `git grep -n` for the retired-command pattern returns only intentional/historical references, each easy to justify. ## Validation * Run the repo's ward/pre-comm ``` … (truncated to 2000 chars; full body is on this issue) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.444.0). </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-08 10:12:39 +00:00

scrub retired coily refs from infrastructure

coilyco-ops closed this issue

2026-07-08 10:12:39 +00:00

coilyco-ops commented

2026-07-08 10:13:28 +00:00

Author

Member

WARD-OUTCOME: done - scrubbed retired coily CLI refs from infrastructure

The cleanup was straightforward once the runtime refs were separated from the intentional retention paths. The only surprise was the review gate being advisory-only here because no heterogeneous reviewer family was available. Final grep: no coily ops or coily pkg runtime calls remain; the exact-pattern hits are the retained coily-install / coily-update / coily-audit paths, the coily.yaml migration fallback in generate-caddy-shortcuts.py, and a few historical deploy notes.

WARD-OUTCOME: done - scrubbed retired coily CLI refs from infrastructure The cleanup was straightforward once the runtime refs were separated from the intentional retention paths. The only surprise was the review gate being advisory-only here because no heterogeneous reviewer family was available. Final grep: no `coily ops` or `coily pkg` runtime calls remain; the exact-pattern hits are the retained coily-install / coily-update / coily-audit paths, the `coily.yaml` migration fallback in `generate-caddy-shortcuts.py`, and a few historical deploy notes.