Your objective is to set the Safety Gate to normal mode.
Before proceeding, verify that .cocoplus/ exists.
If not: output "CocoPlus not initialized in this directory. Run $pod init to begin." Then stop.
Remove any existing safety mode flags (cross-platform using the Bash tool):
node -e "['safety.strict','safety.off'].forEach(f=>{try{require('fs').unlinkSync('.cocoplus/modes/'+f)}catch(_){}});console.log('Old flags cleared.');"
Create normal mode flag: create the file .cocoplus/modes/safety.normal with empty content using the Write tool.
Update AGENTS.md (keep ≤200 lines): replace Safety line with - Safety: normal (WARN + confirm for destructive SQL)
Output: "✓ Safety Gate set to NORMAL. Destructive SQL operations will require explicit confirmation before execution. This setting persists across sessions."
Anti-Rationalization
| Shortcut / Temptation | Why It Fails |
|---|---|
| Keep strict/off flags while enabling normal | Mixed flags create unpredictable gate decisions |
| Skip warning semantics in the summary message | Developers may mistake normal mode for full blocking |
| Avoid updating AGENTS.md to save time | Runtime posture becomes opaque to the team |
Exit Criteria
-
.cocoplus/modes/safety.normalexists -
.cocoplus/modes/safety.strictand.cocoplus/modes/safety.offdo NOT exist -
.cocoplus/AGENTS.mdSafety line reads- Safety: normal (WARN + confirm for destructive SQL) - Confirmation output states normal mode is active with warning + confirmation behavior