safety-off

Your objective is to disable the Safety Gate.

Before proceeding, verify that .cocoplus/ exists. If not: output "CocoPlus not initialized in this directory. Run $pod init to begin." Then stop.

Warn the developer: "WARNING: Disabling the Safety Gate allows all SQL operations — including DROP TABLE, TRUNCATE, and DELETE without WHERE — to execute without any interception. Only do this if you are certain you are working in a non-production environment with no real data. Continue? (yes/no)"

If no: restore safety.normal and output "Safety Gate left at normal mode." Then stop.

Remove any existing safety mode flags (cross-platform using the Bash tool):

node -e "['safety.strict','safety.normal'].forEach(f=>{try{require('fs').unlinkSync('.cocoplus/modes/'+f)}catch(_){}});console.log('Old flags cleared.');"

Create off flag: create the file .cocoplus/modes/safety.off with empty content using the Write tool.

Update AGENTS.md: replace Safety line with - Safety: OFF (no protection — all SQL allowed)

Output: "⚠ Safety Gate disabled. No SQL operations will be intercepted. Run $safety normal or $safety strict to re-enable protection."

Anti-Rationalization

Shortcut / Temptation	Why It Fails
Disable safety without explicit confirmation	High-risk change can occur accidentally
Keep normal/strict flag while enabling off	Conflicting mode flags invalidate safety expectations
Hide risk wording in output	Developers may run destructive SQL without realizing protection is off

Exit Criteria

• Developer receives the explicit risk warning and confirmation prompt before disabling protection
• .cocoplus/modes/safety.off exists only after confirmation
• .cocoplus/modes/safety.strict and .cocoplus/modes/safety.normal do NOT exist when off mode is active
• .cocoplus/AGENTS.md Safety line reads - Safety: OFF (no protection — all SQL allowed)