Uncommitted coily-regenerated lockdown drift on kai-server checkout #19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-22T09:33:50Z - https://github.com/coilysiren/infrastructure/issues/253
While pulling the repo on kai-server, its checkout showed uncommitted changes to
.claude/lockdown-deny.shand.claude/settings.json, both coily-regenerated:lockdown-deny.sh:exec agent-guard hook pre-tool-use->exec coily hook pre-tool-use(the coily#248 hook migration).settings.json:+ "Bash(coily ops gcloud:*)"in the allow list.These are auto-generated by
coily setup/coily lockdown --apply. The working tree on kai-server matches current coily output; the committed copies are stale. Likely the same drift exists in every catalog repo with a committed.claude/lockdown-deny.sh.Decide and apply repo-wide: either commit the regenerated lockdown across repos, or stop committing the generated files (gitignore + regenerate via
coily setup). Right now they drift silently on every coily lockdown-output change.Merged into #164 in the 2026-05-29 backlog burn-down. lockdown drift instance, same as sync task #164 Reopen if it should stand alone.