Mods need allow permissions to iterate on them, could be added to docs

Summary

After building a mod with mod builder, I want to iterate on it.

But, the mods dir requires allow permissions.

That's fine but would be nice to add that to the docs so know for to do.

⚠ Sensitive file — path is inside .commandcode/ (Command Code settings). Never touched without approval.

Do you want to create .commandcode/mods/erd/commands.ts?

❯ 1. Yes
  2. No, tell Command Code what to do differently

Expected Behavior

Add to docs something like:

{
  "permissions": {
    "allow": [
      "Edit(.commandcode/mods/**)",
    ]
  }
}

so editing mods can flow smoothly.

Actual Behavior

1. asked to approve edits to any mod

Steps to reproduce the issue

1. use mod-builder to build a mod
2. then iterate on it to make changes

Command Code Version

1.5.0

Operating System

macOS

Terminal/IDE

ghostty

Shell

zsh

Additional context

No response

No documentation file is named in the issue. Start by locating the documentation for mod-builder output and permission configuration, then add guidance for allowing edits to .commandcode/mods/**. Done means the documented configuration explains how to avoid repeated approval prompts when iterating on generated mods.