coily deprecation: converge gate + remaining cleanup #351

New issue

Open

opened 2026-06-17 06:16:08 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-17 06:16:08 +00:00

Owner

Follow-up to the coily deprecation (steps 1-3 landed across coily, homebrew-tap, scoop-bucket, infrastructure).

What landed

coily removed from homebrew_taps + homebrew_installed_packages on linux + mac, added to homebrew_installed_packages_absent (converge uninstalls fleet-wide).
lockdown ansible role deleted + unwired from sync.yml (it shelled out to coily lockdown).
coily Homebrew formulae disable!d (per-repo + central tap), release.yml deleted, scoop manifest dropped.

GATE before converging the _absent uninstall

Do NOT run the homebrew converge until:

The .coily -> .ward command-router migration is complete in every repo that still has a .coily/coily.yaml, OR lockdown is fully neutralized so bare tools work. Otherwise: coily gone + deny rules still active = dev breaks fleet-wide.
Per-repo lockdown deny files (.claude/lockdown-deny.sh + .claude/settings.json) are neutralized. These are permission-boundary files - a human/CI operation, never an agent commit (per AGENTS rule). Removing the lockdown role stops regenerating them but leaves existing files enforcing the boundary.

Step 4 (after fleet has converged coily to absent on every host)

Archive coilyco-bridge/coily (read-only, keep history + disable! message reachable; do not hard-delete).
Remove the coily formula from the central coilyco-bridge/homebrew-tap (or archive alongside).

Verify

brew list | grep coily empty on each host post-converge.
No remaining checkout or script hard-requires the coily binary.

Follow-up to the coily deprecation (steps 1-3 landed across coily, homebrew-tap, scoop-bucket, infrastructure). ## What landed - coily removed from homebrew_taps + homebrew_installed_packages on linux + mac, added to homebrew_installed_packages_absent (converge uninstalls fleet-wide). - lockdown ansible role deleted + unwired from sync.yml (it shelled out to `coily lockdown`). - coily Homebrew formulae disable!d (per-repo + central tap), release.yml deleted, scoop manifest dropped. ## GATE before converging the _absent uninstall Do NOT run the homebrew converge until: 1. The .coily -> .ward command-router migration is complete in every repo that still has a .coily/coily.yaml, OR lockdown is fully neutralized so bare tools work. Otherwise: coily gone + deny rules still active = dev breaks fleet-wide. 2. Per-repo lockdown deny files (.claude/lockdown-deny.sh + .claude/settings.json) are neutralized. These are permission-boundary files - a human/CI operation, never an agent commit (per AGENTS rule). Removing the lockdown role stops *regenerating* them but leaves existing files enforcing the boundary. ## Step 4 (after fleet has converged coily to absent on every host) - Archive coilyco-bridge/coily (read-only, keep history + disable! message reachable; do not hard-delete). - Remove the coily formula from the central coilyco-bridge/homebrew-tap (or archive alongside). ## Verify - `brew list | grep coily` empty on each host post-converge. - No remaining checkout or script hard-requires the coily binary.

coilysiren added the

label

2026-06-17 09:23:34 +00:00

coilysiren referenced this issue from a commit

2026-06-17 21:27:40 +00:00

fix(ansible): drop disabled coily formula from homebrew present-list

coilysiren added

interactive

and removed

labels

2026-06-18 06:21:51 +00:00