Track coily-managed .claude lockdown files #13

New issue

Closed

opened 2026-05-29 05:41:40 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-05-29 05:41:40 +00:00

Owner

The .claude/ dir (settings.json, lockdown-deny.sh) is regenerated by coily setup/coily lockdown but was untracked in atmosphere. Track those two managed files and ignore the machine-specific .claude/settings.local.json so the lockdown config is shared and self-heals across the fleet.

The `.claude/` dir (`settings.json`, `lockdown-deny.sh`) is regenerated by `coily setup`/`coily lockdown` but was untracked in atmosphere. Track those two managed files and ignore the machine-specific `.claude/settings.local.json` so the lockdown config is shared and self-heals across the fleet.

coilysiren commented

2026-05-30 05:43:15 +00:00

Author

Owner

Merged into #6 in the 2026-05-29 backlog burn-down. Track .claude lockdown files, same cluster as #6 Reopen if it should stand alone.

coilysiren closed this issue

2026-05-30 05:43:15 +00:00

coilysiren referenced this issue from a commit

2026-05-30 17:51:41 +00:00

chore: track coily-managed .claude lockdown files

coilysiren added the

label