sinapse-ai 7.1.0 → 7.3.0

package/squads/claude-code-mastery/tasks/enterprise-config.md

@@ -0,0 +1,346 @@
+# Task: Enterprise Configuration
+
+**Task ID:** CCM-CONFIG-007
+**Version:** 1.0.0
+**Command:** `*enterprise-config`
+**Orchestrator:** Sigil (config-engineer)
+**Purpose:** Generate and deploy enterprise-grade Claude Code configuration using managed-settings.json for organizational policy enforcement, MDM integration, compliance rules, and standardized MCP server deployment across teams.
+
+---
+
+## Overview
+
+```
+  +------------------+     +------------------+     +------------------+
+  | 1. Set Up        | --> | 2. Configure     | --> | 3. Set Up        |
+  |    managed-      |     |    MDM/OS-Level  |     |    managed-      |
+  |    settings.json |     |    Policies      |     |    mcp.json      |
+  +------------------+     +------------------+     +------------------+
+       |                                                    |
+       v                                                    v
+  +------------------+     +------------------+
+  | 4. Configure     | --> | 5. Deploy        |
+  |    Compliance    |     |    Across        |
+  |    Rules         |     |    Organization  |
+  +------------------+     +------------------+
+```
+
+---
+
+## Inputs
+
+| Field | Type | Source | Required | Validation |
+|-------|------|--------|----------|------------|
+| org_name | string | User parameter | Yes | Organization identifier |
+| compliance | array | User parameter | No | Compliance frameworks: `soc2`, `hipaa`, `gdpr`, `pci`, `iso27001` |
+| platform_targets | array | User parameter | No | `macos`, `linux`, `windows`, `wsl2` (default: all) |
+| team_count | number | User parameter | No | Number of developers/teams using Claude Code |
+
+---
+
+## Preconditions
+
+- Administrative access to deploy managed settings files
+- Understanding of organizational security policies
+- MDM system access (for macOS plist or Windows registry deployment)
+- Knowledge of approved tools and MCP servers for the organization
+
+---
+
+## Execution Phases
+
+### Phase 1: Set Up managed-settings.json
+
+Create the managed settings file that cannot be overridden by user or project settings:
+
+**Deployment locations (one per platform):**
+
+| Platform | Path |
+|----------|------|
+| macOS | `/Library/Application Support/ClaudeCode/managed-settings.json` |
+| Linux/WSL | `/etc/claude-code/managed-settings.json` |
+| Windows | `C:\Program Files\ClaudeCode\managed-settings.json` |
+
+**Base template:**
+
+```json
+{
+  "permissions": {
+    "deny": [
+      "Read(./.env)",
+      "Read(./.env.*)",
+      "Read(./secrets/**)",
+      "Read(./**/*.pem)",
+      "Read(./**/*.key)",
+      "Bash(rm -rf /)",
+      "Bash(curl * | bash)",
+      "Bash(wget * | bash)"
+    ],
+    "defaultMode": "acceptEdits"
+  },
+  "disableBypassPermissionsMode": "disable",
+  "allowManagedPermissionRulesOnly": false,
+  "env": {
+    "CLAUDE_CODE_EFFORT_LEVEL": "high",
+    "CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": "80"
+  },
+  "companyAnnouncements": [
+    "{org_name}: Use Claude Code responsibly. Report issues to #ai-tools."
+  ]
+}
+```
+
+**Managed-only policy keys:**
+
+| Key | Type | Purpose | Recommendation |
+|-----|------|---------|----------------|
+| `disableBypassPermissionsMode` | `"disable"` | Prevent users from bypassing permissions | Always set in enterprise |
+| `allowManagedPermissionRulesOnly` | boolean | Only managed deny/allow rules apply | `true` for regulated environments |
+| `allowManagedHooksOnly` | boolean | Only managed hooks can execute | `true` for high-security |
+| `allowManagedMcpServersOnly` | boolean | Only managed MCP servers allowed | `true` for compliance |
+| `companyAnnouncements` | string[] | Messages shown to all users | Use for policies and reminders |
+
+### Phase 2: Configure MDM/OS-Level Policies
+
+For organizations using Mobile Device Management:
+
+**macOS (plist):**
+```xml
+<!-- com.anthropic.claudecode.plist -->
+<dict>
+  <key>disableBypassPermissionsMode</key>
+  <string>disable</string>
+  <key>permissions</key>
+  <dict>
+    <key>defaultMode</key>
+    <string>acceptEdits</string>
+    <key>deny</key>
+    <array>
+      <string>Read(./.env)</string>
+      <string>Read(./.env.*)</string>
+      <string>Read(./secrets/**)</string>
+    </array>
+  </dict>
+</dict>
+```
+
+**Windows (Registry):**
+```
+HKLM\SOFTWARE\Policies\ClaudeCode\
+  disableBypassPermissionsMode = "disable" (REG_SZ)
+  permissions\defaultMode = "acceptEdits" (REG_SZ)
+```
+
+**Linux (file-based):**
+Deploy `/etc/claude-code/managed-settings.json` via configuration management (Ansible, Chef, Puppet).
+
+Provide platform-specific deployment scripts or configuration snippets.
+
+### Phase 3: Set Up managed-mcp.json
+
+Create the managed MCP configuration for standard organizational tools:
+
+**Deployment locations:**
+
+| Platform | Path |
+|----------|------|
+| macOS | `/Library/Application Support/ClaudeCode/managed-mcp.json` |
+| Linux/WSL | `/etc/claude-code/managed-mcp.json` |
+| Windows | `C:\Program Files\ClaudeCode\managed-mcp.json` |
+
+**Template:**
+
+```json
+{
+  "mcpServers": {
+    "context7": {
+      "command": "npx",
+      "args": ["-y", "@context7/mcp-server"],
+      "env": {}
+    }
+  },
+  "allowedMcpServers": [
+    { "serverName": "context7" },
+    { "serverName": "playwright" }
+  ],
+  "deniedMcpServers": [
+    { "serverName": "filesystem" }
+  ]
+}
+```
+
+**Server allowlisting strategy:**
+
+| Strategy | Setting | Use Case |
+|----------|---------|----------|
+| Open (default) | No restrictions | Trusted teams, experimental |
+| Allowlist | `allowedMcpServers` array | Standard teams, moderate control |
+| Managed-only | `allowManagedMcpServersOnly: true` | Regulated environments |
+| Blocklist | `deniedMcpServers` array | Block specific known-risky servers |
+
+### Phase 4: Configure Compliance Rules
+
+For each compliance framework, add specific rules:
+
+**SOC2:**
+```json
+{
+  "permissions": {
+    "deny": [
+      "Read(./**/*.pem)", "Read(./**/*.key)",
+      "Bash(curl * | bash)", "Bash(wget * | bash)"
+    ]
+  },
+  "disableBypassPermissionsMode": "disable",
+  "sandbox": {
+    "network": { "allowManagedDomainsOnly": true }
+  }
+}
+```
+
+**HIPAA (healthcare data):**
+```json
+{
+  "permissions": {
+    "deny": [
+      "Read(./patient-data/**)", "Read(./phi/**)",
+      "WebFetch"
+    ],
+    "defaultMode": "askAlways"
+  },
+  "allowManagedPermissionRulesOnly": true,
+  "allowManagedMcpServersOnly": true
+}
+```
+
+**GDPR (personal data):**
+```json
+{
+  "permissions": {
+    "deny": [
+      "Read(./user-data/**)", "Read(./pii/**)",
+      "Read(./**/personal/**)"
+    ]
+  },
+  "companyAnnouncements": [
+    "GDPR: Do not paste personal data into Claude Code prompts."
+  ]
+}
+```
+
+**PCI-DSS (payment data):**
+```json
+{
+  "permissions": {
+    "deny": [
+      "Read(./payment/**)", "Read(./**/*card*)",
+      "Read(./**/*billing*)"
+    ],
+    "defaultMode": "askAlways"
+  },
+  "disableBypassPermissionsMode": "disable"
+}
+```
+
+Merge compliance rules with the base managed-settings.json.
+
+### Phase 5: Deploy Across Organization
+
+1. Generate deployment artifacts:
+   - `managed-settings.json` for each platform
+   - `managed-mcp.json` for each platform
+   - MDM profiles (plist for macOS, registry for Windows)
+   - Managed CLAUDE.md (optional, for org-wide instructions)
+2. Create deployment documentation:
+   - Installation instructions per platform
+   - Verification commands to confirm deployment
+   - Rollback procedure
+3. Provide verification checklist:
+
+```bash
+# Verify managed settings are loaded (run as user)
+# Claude Code will show managed policy indicators in the UI
+
+# Check managed file exists
+# macOS:
+ls -la "/Library/Application Support/ClaudeCode/managed-settings.json"
+# Linux:
+ls -la /etc/claude-code/managed-settings.json
+# Windows:
+dir "C:\Program Files\ClaudeCode\managed-settings.json"
+```
+
+---
+
+## Output Format
+
+```markdown
+## Enterprise Configuration Package
+
+**Organization:** {org_name}
+**Compliance:** {frameworks}
+**Platforms:** {targets}
+**Teams:** {team_count}
+
+### Generated Files
+
+| File | Platform | Purpose | Deploy To |
+|------|----------|---------|-----------|
+| managed-settings.json | {platform} | Policy enforcement | {path} |
+| managed-mcp.json | {platform} | Standard MCP servers | {path} |
+| CLAUDE.md | All | Org-wide instructions | {path} |
+| {mcp-profile} | macOS | MDM deployment | Jamf/Intune |
+
+### Policy Summary
+
+| Policy | Setting | Effect |
+|--------|---------|--------|
+| Bypass disabled | disableBypassPermissionsMode: disable | Users cannot skip permissions |
+| Managed rules only | allowManagedPermissionRulesOnly: {val} | {effect} |
+| Managed MCP only | allowManagedMcpServersOnly: {val} | {effect} |
+| Network restriction | allowManagedDomainsOnly: {val} | {effect} |
+
+### Deny Rules ({count} total)
+
+{Numbered list of all deny rules with categories}
+
+### Approved MCP Servers
+
+| Server | Purpose | Status |
+|--------|---------|--------|
+| {name} | {purpose} | Allowed/Managed |
+
+### Deployment Instructions
+
+{Platform-specific deployment steps}
+
+### Verification
+
+{Commands to verify deployment on each platform}
+
+### Rollback
+
+{Steps to remove managed settings if needed}
+```
+
+---
+
+## Veto Conditions
+
+- **NEVER** generate enterprise configuration without `disableBypassPermissionsMode: "disable"`. This is the foundational enterprise security control.
+- **NEVER** include real API keys, tokens, or credentials in managed configuration files. Use environment variable references.
+- **NEVER** set `allowManagedPermissionRulesOnly: true` without also including comprehensive deny rules. This would leave the system unprotected.
+- **NEVER** deploy managed-settings.json without providing a rollback procedure. Configuration errors at the managed level affect all users.
+- **NEVER** omit compliance-specific rules when a compliance framework is specified. Partial compliance is worse than documented non-compliance.
+
+---
+
+## Completion Criteria
+
+- [ ] managed-settings.json generated with deny-first rules and enterprise policy keys
+- [ ] MDM/OS-level deployment method documented for target platforms
+- [ ] managed-mcp.json generated with approved server list
+- [ ] Compliance rules integrated for all specified frameworks
+- [ ] Deployment instructions created per platform
+- [ ] Verification commands provided
+- [ ] Rollback procedure documented

package/squads/claude-code-mastery/tasks/hook-designer.md

@@ -0,0 +1,272 @@
+# Task: Design Custom Hooks
+
+**Task ID:** CCM-PI-006
+**Version:** 1.0.0
+**Command:** `*hook-designer`
+**Agent:** Conduit (project-integrator)
+**Purpose:** Design custom Claude Code hooks for a project by identifying automation needs, choosing appropriate hook types and events, designing hook logic, and producing implementation-ready specifications.
+
+---
+
+## Overview
+
+```
+  Automation Needs
+       |
+       v
+  +---------------------+
+  | 1. Identify Hook     |
+  |    Needs             |
+  +---------------------+
+       |
+       v
+  +---------------------+
+  | 2. Choose Hook Type  |
+  |    & Category        |
+  +---------------------+
+       |
+       v
+  +---------------------+
+  | 3. Select Events     |
+  +---------------------+
+       |
+       v
+  +---------------------+
+  | 4. Design Hook Logic |
+  +---------------------+
+       |
+       v
+  +---------------------+
+  | 5. Implement & Test  |
+  +---------------------+
+       |
+       v
+  +---------------------+
+  | 6. Integration       |
+  |    Verification      |
+  +---------------------+
+```
+
+---
+
+## Inputs
+
+| Field | Type | Source | Required | Validation |
+|-------|------|--------|----------|------------|
+| hook_purpose | string | User | Yes | Description of what the hook should automate |
+| trigger_event | string | User | No | Specific event if known (e.g., "PreToolUse", "Stop") |
+| project_path | string | User or cwd | Yes | Project directory for context |
+
+---
+
+## Preconditions
+
+- Claude Code installed and functional
+- Understanding of the project's workflow and pain points
+- `.claude/` directory exists (or will be created)
+
+---
+
+## Execution Phases
+
+### Phase 1: Identify Hook Needs
+
+Analyze the requested automation against hook capabilities:
+
+1. **Categorize the need**:
+   - Security: blocking dangerous commands, validating inputs
+   - Automation: auto-formatting, auto-logging, state management
+   - Quality: linting on save, test on commit, review on complete
+   - Observability: timing, token tracking, cost monitoring
+   - Context management: compaction, memory updates, state persistence
+
+2. **Validate hook-suitability**: some needs are better served by:
+   - Skills/commands (user-triggered, not event-triggered)
+   - Rules (static instructions, not runtime logic)
+   - CI/CD (post-merge, not during session)
+
+If the need is not hook-suitable, recommend the appropriate alternative.
+
+### Phase 2: Choose Hook Type and Category
+
+Claude Code hooks operate in two transport modes:
+
+| Transport | Language | Best For | Constraint |
+|-----------|----------|----------|------------|
+| command | Any (bash, node, python) | File operations, API calls, complex logic | Must exit within timeout |
+| prompt | N/A (returns text) | Injecting context into conversation | Output added to assistant context |
+
+**Hook categories by event:**
+
+| Event | When Fires | Common Uses |
+|-------|-----------|-------------|
+| PreToolUse | Before any tool call | Block dangerous commands, validate inputs |
+| PostToolUse | After tool completes | Log results, capture metrics, trigger follow-ups |
+| Stop | Session ends normally | Save state, generate summary, update memory |
+| SubagentStop | Subagent completes | Collect results, merge outputs |
+| PreCompact | Before context compaction | Preserve critical state |
+| Notification | User receives notification | Custom notification routing |
+| UserPromptSubmit | User sends message | Input preprocessing, routing |
+
+Select the appropriate event based on when the automation should trigger.
+
+### Phase 3: Select Appropriate Events
+
+For the identified need, determine:
+
+1. **Primary event**: the main trigger for the hook
+2. **Guard conditions**: when the hook should fire vs skip
+   - Tool name filter (for PreToolUse/PostToolUse)
+   - Session state checks
+   - File pattern matching
+3. **Timeout**: maximum execution time (default 10s for command hooks)
+4. **Error behavior**: what happens if the hook fails
+   - `continue`: session proceeds (recommended for non-critical hooks)
+   - `stop`: session halts (use only for security-critical hooks)
+
+### Phase 4: Design Hook Logic
+
+Design the hook implementation:
+
+1. **Input contract**: what data the hook receives from Claude Code
+   ```json
+   {
+     "tool_name": "Bash",
+     "tool_input": { "command": "rm -rf /tmp/test" },
+     "session_id": "abc123"
+   }
+   ```
+
+2. **Processing logic**: what the hook does with the input
+   - Parse input data
+   - Apply business logic (validation, transformation, logging)
+   - Produce output (block/allow, log entry, context injection)
+
+3. **Output contract**: what the hook returns
+   - For PreToolUse: `{ "decision": "allow" }` or `{ "decision": "block", "reason": "..." }`
+   - For prompt hooks: plain text to inject into conversation
+   - For command hooks: exit code 0 (success) or non-zero (failure)
+
+4. **Performance requirements**:
+   - Hook must complete within timeout
+   - No blocking I/O without timeouts
+   - Graceful degradation on failure
+
+5. **State management** (if needed):
+   - Where to store state (file, environment variable)
+   - State format (JSON, YAML)
+   - Concurrency considerations
+
+### Phase 5: Implement and Test
+
+Create the hook implementation:
+
+1. **Write the hook script** following the designed logic
+   - Use the language best suited to the task (Node.js for JSON, Bash for simple commands)
+   - Include error handling and timeout protection
+   - Add inline comments explaining the logic
+
+2. **Register the hook** in settings.json:
+   ```json
+   {
+     "hooks": {
+       "{EventName}": [
+         {
+           "type": "command",
+           "command": "node .claude/hooks/{hook-name}.js",
+           "timeout": 10000
+         }
+       ]
+     }
+   }
+   ```
+
+3. **Test the hook**:
+   - Manual trigger with sample input
+   - Edge cases: missing fields, malformed input, timeout simulation
+   - Verify exit code and output format
+
+### Phase 6: Integration Verification
+
+Verify the hook works within the full Claude Code session:
+
+1. Start a Claude Code session
+2. Trigger the event that fires the hook
+3. Verify the hook executed (check logs, output, or behavior)
+4. Confirm no interference with other hooks or normal workflow
+5. Check performance: hook completes well within timeout
+
+---
+
+## Output Format
+
+```markdown
+## Hook Design Specification
+
+**Purpose:** {hook_purpose}
+**Event:** {event_name}
+**Type:** {command|prompt}
+**Language:** {node|bash|python}
+
+### Design
+
+**Trigger:** {when the hook fires}
+**Guard:** {conditions to skip execution}
+**Timeout:** {N}ms
+
+### Input/Output Contract
+
+**Input:**
+```json
+{input_schema}
+```
+
+**Output:**
+```json
+{output_schema}
+```
+
+### Implementation
+
+**File:** `.claude/hooks/{hook-name}.js`
+**Registration:**
+```json
+{settings_json_snippet}
+```
+
+### Test Plan
+
+| Scenario | Input | Expected Output |
+|----------|-------|-----------------|
+| Normal case | {input} | {output} |
+| Edge case | {input} | {output} |
+| Error case | {input} | {output} |
+
+### Performance
+
+- Expected execution time: {N}ms
+- Timeout configured: {N}ms
+- Failure mode: {continue|stop}
+```
+
+---
+
+## Veto Conditions
+
+- **NEVER** design hooks that block all tool use without escape hatch
+- **NEVER** design hooks that send data to external services without user consent
+- **NEVER** set hook timeout above 30 seconds (causes session lag)
+- **NEVER** use `stop` error behavior for non-security hooks
+- **NEVER** design hooks that modify source code -- hooks observe and gate, they do not author
+
+---
+
+## Completion Criteria
+
+- [ ] Hook need identified and validated as hook-suitable
+- [ ] Hook type and event selected with rationale
+- [ ] Input/output contract defined
+- [ ] Hook logic designed with error handling
+- [ ] Implementation created and registered in settings.json
+- [ ] Test plan documented with at least 3 scenarios
+- [ ] Integration verified in a real session