/install

Install the required permissions for the Code Archaeology documentation pipeline.

Step 1: Detect Current State

Check if permissions are already installed by looking for Write(/.code-archaeology/**) in the permissions.allow array:

1. Read ~/.claude/settings.json (global, user-wide)
2. Read .claude/settings.local.json in the current project directory (local, project-only)

Report findings to the user:

• "Global permissions (~/.claude/settings.json): installed / not installed"
• "Local permissions (.claude/settings.local.json): installed / not installed"

Step 2: Ask Installation Scope

Use AskUserQuestion to present the choice:

Question: "Where would you like to install Code Archaeology permissions?"

Options:

1. Global (Recommended) — Install into ~/.claude/settings.json so Code Archaeology works in all projects without per-project setup
2. Local — Install into this project's .claude/settings.local.json only (current project)
3. Both — Install in both global and local locations

If permissions are already installed in the chosen location, inform the user they are already configured and ask if they want to re-apply (update) or skip.

Step 3: Run Installation

Execute the installation script with the chosen scope:

bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/ensure-permissions.sh --scope <global|local|both>

Step 4: Verify & Report

Read the modified settings file(s) to confirm Write(/.code-archaeology/**) is present in the permissions.allow array.

Report:

• Which file(s) were modified
• Number of allow/deny rules configured
• What the permissions enable (git commands, file reading, writing to .code-archaeology/)

If global was chosen, note that the plugin's SessionStart hook will still ensure local permissions on each session as a fallback.