hook-diagnostics

# Hook Diagnostics Diagnose hook integration issues between Claude Code and the Agent Monitor. ## Input The user provides: **$ARGUMENTS** This may be: - "full" or empty (default: run all diagnostics) - "install" to check hook installation only - "connectivity" to check dashboard connectivity only - "events" to check event delivery only ## Procedure Run diagnostic checks in this order: ### 1. Hook Installation Check Verify hooks are installed in Claude Code settings: ```bash # Check if hooks exist in Claude Code settings cat ~/.claude/settings.json | jq '.hooks // empty' ``` Verify: - All 7 expected hook types are registered: `PreToolUse`, `PostToolUse`, `Stop`, `SubagentStop`, `Notification`, `SessionStart`, `SessionEnd` - Hook commands point to the correct handler script path - Handler script exists and is readable at the configured path ### 2. Dashboard Connectivity Test that the dashboard API is reachable: ```bash curl -sf http://localhost:4820/api/health ``` Verify: - Dashboard responds with 200 OK - Response includes expected health fields - WebSocket endpoint is accessible ### 3. Hook Handler Validation Check the hook handler script: ```bash # Verify handler exists and is executable ls -la <handler-path> # Syntax check node --check <handler-path> ``` ### 4. Event Delivery Test Send a test event and verify it arrives: ```bash echo '{"hook_type":"test","session_id":"diag-test","data":{}}' | \ curl -sf -X POST http://localhost:4820/api/hooks/event \ -H ...