Sync committed .claude lockdown files to coily v2.43.0 render #164
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#164
Loading…
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?
Task
Committed
.claude/lockdown-deny.sh/.claude/settings.jsonare stale relative to the render produced by coily v2.43.0 (latest). The current binary emits a stronger deny list (blocksbash,sh,python,node,ruby,perl, PowerShell,terraform,xargs, etc.) plus a granular read-onlygitallow set.Sweeping the freshly-rendered files into the repo per the agentic-os "Coily-Managed Lockdown Files" policy (last-pushed wins) so the committed canonical boundary matches the latest coily.
Backlog consolidation on 2026-07-15: the agent is closing this P4 item as a reversible icebox entry. The work remains intentionally parked rather than completed. Kai can reopen it if she promotes it back into active direction.