chore: regenerate coily lockdown after forgejo/origin merge #20

Closed
opened 2026-05-27 07:05:58 +00:00 by coilysiren · 0 comments
Owner

Post-merge regen of .claude/lockdown-deny.sh and .claude/settings.json via coily lockdown --apply --replace to resolve the stash-pop conflict from the forgejo/origin merge.

Background-security-review flagged the resulting Bash(git:*) catch-all + narrowed deny list. That output is what current coily lockdown produces, not a hand-edit. Whether Bash(git:*) is intentional vs. drift in coily lockdown template is out of scope for this commit.

Post-merge regen of .claude/lockdown-deny.sh and .claude/settings.json via `coily lockdown --apply --replace` to resolve the stash-pop conflict from the forgejo/origin merge. Background-security-review flagged the resulting `Bash(git:*)` catch-all + narrowed deny list. That output is what current coily lockdown produces, not a hand-edit. Whether `Bash(git:*)` is intentional vs. drift in coily lockdown template is out of scope for this commit.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/ward#20
No description provided.