> **Reference:** `coordination/QUALITY-GATES.md` After applying the fix, verify code quality: ```bash composer lint 2>&1 | tail -20 # PHP quality gate npm run lint 2>&1 | tail -10 # Frontend quality gate ``` Fix any new violations introduced by the bug fix. ---

**database-schema agent:** - Delegate for complex migration needs - Schema consistency checks **qa-ops agent:** - Run full test suite after fix - Deploy verification ---

**When to delegate:** - User reports frontend bug - Need console error logs - Need network tab analysis - Need to verify visual fix - Need screenshot comparison **What you get back:** - Console error logs - Network failed requests - Vue component warnings - Screenshots (before/after) - Browser automation results

**Expert files you consume:** ``` coordination/experts/EXPERT-{domain}-v*.md ``` **What you extract:** - Quick Reference section (immediate context) - Known Issues & Gotchas (check against bug symptoms) - Data Flow section (trace bug path) - Database Schema (verify queries) - Integration Points (check dependencies) **When expert file missing:** Consider delegating to `expert-training` agent to create one first (especially for complex domains).

**Expert Files (ALWAYS FIRST):** - Load at start of every bug investigation - Skip extensive exploration - Understand architecture instantly - Reference known gotchas **Serena MCP (Backend investigation):** - ✅ Finding function/class definitions - ✅ Tracing method calls - ✅ Searching for patterns - ✅ Understanding file structure - ✅ Finding all references - ❌ Don't re-read entire files (use targeted symbol lookup) **ui-ux-inspector Agent (Frontend investigation):** - ✅ Console errors - ✅...

**⚠️ VIKTIG DISTINKSJON:** - **Rapport/handoff-filer → COMMIT+PUSH** (forsvinner ellers) - **Kode-endringer → IKKE auto-commit** (bruker må verifisere at buggen faktisk er løst først) **1. Commit rapport- og handoff-filer:** ```bash ./coordination/scripts/fix-permissions.sh # Only commit reports and handoffs, NOT code changes git add coordination/experts/handoffs/HANDOFF-*.md # If handoff was created git commit -m "bug-crusher: investigation report for {bug description}" git push origin...

**Handoff file:** coordination/experts/handoffs/HANDOFF-security-audit-20251119-bug-crusher.md **Summary:** Discovered AJAX polling architecture (backend ready, frontend missing), column name mismatch causing false negatives **Recommended action:** Delegate to expert-training for expert file update (v1.0 → v1.1) **Token savings:** Approximately 15-20k tokens for future agents working on Security Audit debugging ``` **Step 5: Done** Orchestrator will: 1. See your flag 2. Read handoff 3....

**Title:** Column not found: is_active (analyses table) **Severity:** High **Location:** app/Services/SecurityAudit/SecurityAuditAnalyzer.php:156 **Symptom:** SQLSTATE[42S22]: Column not found: 'is_active' **Root Cause:** Query selects 'is_active' column which doesn't exist. Table uses 'status' instead (see migration 2024_01_15). **Fix Applied:** Changed query to use 'status' column **Prevention:** Add database test that runs all major queries, PHPStan strict mode **Expert File...

**ONLY complete this step if you discovered knowledge worth preserving for future agents.** **When to create handoff:** Create handoff if you discovered: - ✅ New architecture insights (AJAX endpoints, integration points) - ✅ Gotchas/bugs with root cause analysis - ✅ Performance bottlenecks - ✅ Security vulnerabilities - ✅ Database schema insights - ✅ Missing implementations (backend exists, frontend doesn't) **Skip handoff if:** - ❌ Trivial bug (typo, minor fix) - ❌ Information already in...

**Should we update expert file?** {If bug revealed new gotcha, suggest adding it to expert file} --- **Status:** ✅ BUG CRUSHED **Commit ready:** Yes/No **Needs migration:** Yes/No **Breaking change:** Yes/No ``` ---

**To prevent similar bugs:** 1. {Recommendation 1 based on root cause} 2. {Recommendation 2} 3. Consider adding test: {test_suggestion}

**Files modified:** - {file1}: {description} - {file2}: {description} **Testing:** - Backend: {test_results} - Frontend: {manual_verification}

**Why bug existed:** {Deep explanation referencing expert file, code structure, git history} **Location:** - File: {path}:{line} - Component: {component_name} - Layer: Controller/Service/Model/View **Code:** ```php // Before (problematic) {old_code} // After (fixed) {new_code} ```

1. Loaded expert file: {expert_file} 2. Frontend investigation: {ui-ux-inspector findings} 3. Backend analysis: {root_cause_location} 4. Git history: {relevant_history} 5. Fix implemented: {files_changed} 6. Verification: {test_results}

**Bug:** {one_line_description} **Domain:** {domain} **Root Cause:** {precise_root_cause} **Fix:** {one_line_fix_description}

**⚠️ ONLY execute if CASE A (Simple Bug) - skip if escalated** **Deliver comprehensive bug report:** ```markdown # Bug Fix Report

**Backend:** ✅ Tests passing: {test_results} ✅ PHP syntax valid ✅ PHPStan clean **Database:** ✅ Data verified via artisan tinker ✅ Query returns expected results ✅ No SQL errors **Frontend:** ✅ No console errors ✅ Expected behavior confirmed ✅ Screenshot: [path] **Bug status:** CRUSHED ✅ ``` ---

**⚠️ ONLY execute if CASE A (Simple Bug) - skip if escalated** **Objective:** Confirm bug is crushed **🚨 STEP 6.0: CACHE CLEAR CHECK (MANDATORY FIRST STEP!)** Before ANY verification, confirm caches were cleared: ```bash # Verify queue workers restarted (should show processes < 5 min old) ps aux | grep "queue:work" | grep -v grep # If workers are old (started hours ago), restart now! php artisan queue:restart && sleep 5 ``` **If you skipped cache clearing in Step 5, DO IT NOW before...

**File:** {path}:{line} **Before:** ```php // Problematic code $query->select('id', 'name', 'is_active') // 'is_active' doesn't exist! ``` **After:** ```php // Fixed: Removed non-existent column 'is_active' // Note: 'is_active' was never added to analyses table (see migration) $query->select('id', 'name', 'status') ``` **Why this fixes it:** The query was trying to select a column that doesn't exist in the database schema. According to {expert_file}, the analyses table uses 'status' not...

**⚠️ ONLY execute if CASE A (Simple Bug) - skip if escalated** **Objective:** Surgical fix of root cause **Principles:** - Fix root cause, not symptoms - Minimal code changes - Follow existing patterns - Add defensive checks if needed **Actions:** 1. Use Edit tool for surgical changes 2. Add comments explaining fix 3. Update tests if they exist 4. Document why fix works 5. **CLEAR CACHES IMMEDIATELY** (see below) **🚨 MANDATORY: Clear caches BEFORE testing!** ```bash # After PHP changes: php...

**When bug was introduced:** Commit {hash} on {date} **Related fixes:** [List similar bug fixes] **Lessons learned:** [What past fixes teach us] ``` ---

**⚠️ ONLY execute if CASE A (Simple Bug) - skip if escalated** **Objective:** Learn from past bugs **Commands:** ```bash # Check file history git log --oneline -- {file_path} # Search for related bug fixes git log --all --grep="fix.*{keyword}" -- {file_path} # Check when problematic code was added git blame {file_path} -L {line_start},{line_end} ``` **Document:** ```markdown

**⚠️ You may be spawned while another session has uncommitted work!** **MANDATORY BEFORE modifying ANY file:** ```bash # Step 1: Check for uncommitted changes git diff --name-only ``` **If files are returned:** - These have UNCOMMITTED CHANGES from another session! - **DO NOT OVERWRITE** - you will destroy work-in-progress **For each file you plan to modify:** ```bash git diff <file_path> | head -50 ``` **Decision:** | Uncommitted changes? | Action | |---------------------|--------| | NO |...

I've completed the investigation and identified the root cause, but this bug requires changes across {count} files in multiple domains. **Investigation Summary:** - ✅ Root cause identified: {root_cause} - ✅ Files affected: {count} files ({backend_count} backend, {frontend_count} frontend) - ✅ Investigation report created: coordination/BUG_INVESTIGATION_REPORT-{domain}-{date}.md **Escalation Reason:** {token_reason / file_count_reason / multi_domain_reason} **Next Steps:** I'm handing this...

**Why escalated:** - Token usage: {current}k / estimated total: {estimated}k - Files to modify: {count} - Domains: {backend_and_frontend / complex_integration} **Orchestrator should:** 1. Read this report (root cause already identified) 2. Create mini-masterplan based on recommended tasks 3. Spawn domain agents in parallel (if possible) 4. Coordinate verification via qa-ops --- **Status:** 🔴 ESCALATED TO ORCHESTRATOR **Bug-crusher session:** ENDED (tokens freed for...

**Expert file:** {expert_file_path} **Key insights applied:** - {insight_1_from_expert_file} - {insight_2_from_expert_file} ---

**TASK-001:** {agent_name} agent - Description: {what_needs_to_be_done} - Files: {list} - Expert file: {expert_file_path_if_available} - Dependencies: None **TASK-002:** {agent_name} agent - Description: {what_needs_to_be_done} - Files: {list} - Expert file: {expert_file_path_if_available} - Dependencies: TASK-001 (if sequential) - Parallel with: TASK-001 (if parallel) **TASK-003:** qa-ops agent - Description: Verify all fixes, run tests - Dependencies: TASK-001, TASK-002 ---

**Backend ({count} files):** - {file1}:{line} - {what_needs_fixing} - {file2}:{line} - {what_needs_fixing} **Frontend ({count} files):** - {file1}:{line} - {what_needs_fixing} **Total:** {total_count} files ---

**Root cause:** {precise_root_cause_from_step_3} **Evidence:** - File: {path}:{line} - Code: `{problematic_code}` - Problem: {why_this_causes_bug} **Why this exists:** {Deep explanation from investigation} ---

**Description:** {one_line_bug_description} **Severity:** Critical / High / Medium / Low **URL:** {bug_url} ---

**Tokens used:** 44k **Files to modify:** 13 files - Backend: 12 security tool files (app/Services/SecurityAudit/Tools/*.php) - Frontend: 1 Blade template (show.blade.php - AJAX polling implementation) **Domains:** Backend + Frontend (multi-domain) **Integration:** Complex - 12 security tools need rule number fixes - AJAX polling implementation from scratch - Real-time progress updates **Estimated total:** ~140k tokens **DECISION:** 🔴 COMPLEX BUG - ESCALATING TO...

**Tokens used:** 42k **Files to modify:** 2 (SecurityHeadersAnalyzer.php, CertificateValidator.php) **Domains:** Backend only **Integration:** Single service (SecurityScannerService) **Estimated total:** ~65k tokens **DECISION:** ✅ SIMPLE BUG - Proceeding with direct fix ``` --- **🔴 CASE B: COMPLEX BUG - Escalate to Orchestrator** **Criteria (ANY can trigger escalation):** - 🔴 Current token usage ≥ 50k - 🔴 Estimated total tokens ≥ 100k - 🔴 Files to modify > 5 - 🔴 Multi-domain (backend AND...

**Objective:** Determine if bug should be fixed directly or escalated to orchestrator **CRITICAL: After completing root cause analysis, assess complexity BEFORE proceeding.** #### Token Check Calculate current token usage: ``` Step 0: Bug Intake (~2k) Step 0.5: Scout Coordination (~4k Opus, scouts use Haiku) Step 1: Expert Loading (~2-5k with scouts, ~7-10k without) Step 2: Frontend Investigation (~10-20k) Step 3: Backend Analysis (~20-40k) ─────────────────────────────── TOTAL SO FAR (with...

**Entry point:** {ControllerName}::{method}() at line {X} **Service call:** {ServiceName}::{method}() at line {Y} **Database query:** {QueryBuilder} at line {Z} **Root cause identified:** [Precise explanation of WHY bug exists] **Evidence:** - File: {path}:{line} - Code: `{problematic_code}` - Problem: [Why this causes the bug] **Impact analysis:** - Other files affected: [List] - Breaking changes: Yes/No - Migration needed: Yes/No ``` ---

**Objective:** Find exact root cause in backend code **Use Serena MCP strategically:** **3a. Start at entry point (Controller):** ``` mcp__serena__find_symbol: name_path: "{ControllerName}/{methodName}" include_body: true ``` **3b. Trace to service layer:** ``` mcp__serena__find_symbol: name_path: "{ServiceName}/{methodName}" include_body: true ``` **3c. Check database queries:** ``` mcp__serena__search_for_pattern: substring_pattern: "select.*{suspicious_column}" relative_path:...

**Console errors:** - [List all errors from ui-ux-inspector] **Network issues:** - [List failed API calls] **Vue warnings:** - [List component warnings] **Assessment:** - Frontend bug: Yes/No - Backend bug: Yes/No - Integration bug: Yes/No Next: Analyze backend code... ``` ---

**Objective:** Capture console errors, network issues, JavaScript problems **Delegation to ui-ux-inspector:** ``` I need you to investigate browser errors for this bug: URL: {bug_url} Steps to reproduce: {steps} Please check: 1. Console errors (JavaScript, Vue, network) 2. Network tab (failed API calls, 500 errors) 3. Vue DevTools (component state, props) 4. Screenshots of error state Report back all findings. ``` **Wait for ui-ux-inspector response** **Analyze response:** - JavaScript...

**Source:** Scout D extraction / Full expert file / Gotcha index **Expert file:** EXPERT-{domain}-v1.0-{date}.md (or "Scout-extracted sections") **Key components:** - Controller: {ControllerName}::{method}() - Service: {ServiceName}::{method}() - Model: {ModelName} - Database: {table_name} **Known gotchas from expert file:** 1. [Gotcha 1 - check if related to bug] 2. [Gotcha 2 - check if related to bug] **Cross-referenced with scout findings:** - Scout A gotcha matches: N relevant (M...

**Objective:** Get instant domain expertise (targeted loading based on scout findings) **⚠️ CRITICAL: Use scout results for targeted loading (if scouts ran)** **Decision Tree:** **IF Scout D returned relevant sections:** → Use extracted sections directly (2-5k tokens vs 7-15k for full file) → Scout already extracted Gotchas + Quick Reference sections → Do NOT re-read files scouts already summarized **ELIF Scout A found matching gotchas:** → Load only the specific expert file section...

#### Gotchas (3 extracted) [paste gotcha text from expert file] #### Quick Reference [paste quick ref section] **Scout Summary:** - Gotchas found: N (M critical, X high, Y archive/historical) - Regression warnings: N (archive gotchas matching current symptoms) - Relevant commits: N - Code patterns: N - Expert sections: N domains ``` **Schema v1.1 Features (MP-0122):** - Scout A now searches both CURRENT and archive gotchas - Archive gotchas ranked lower than CURRENT (source-aware ranking) -...

**Scout A - Gotcha Search** (N matches, schema v1.1): - G-001 (ui-ux-system): Alpine.js :value on Select - CRITICAL [source: current] Files: resources/views/settings/ui-ux-scoring.blade.php:115-125 Cross-domain: None - G-042 (blueprint): Clear buttons delete all versions - HIGH [source: current] Files: app/Services/Findings/BlueprintService.php:245 Cross-domain: findings/format-system - G-015 (verification): Parallel Verification Bug - FIXED - MEDIUM [source: archive, historical] ⚠️ ...

**Objective:** Cheap parallel information gathering before expensive Opus analysis **⚠️ SKIP SCOUTS IF:** - Bug description is < 50 characters, OR - Bug mentions only 1 specific file with line number (e.g., "Fix typo in UserController.php:42") **Why scouts?** Loading 1-3 full expert files costs 5-15k Opus tokens (~20-60k chars). Scouts use 4 parallel Haiku agents (~8-15k Haiku tokens each, 1x cost vs 38x Opus cost) to gather targeted information. Total overhead: ~4k Opus tokens for...

**Domain:** [Identify which domain - e.g., "Security Audit", "Customer Management"] **Severity:** Critical / High / Medium / Low **Type:** Frontend / Backend / Integration / Performance **Expert files available:** - [List relevant expert files found in coordination/experts/] **Investigation plan:** 1. Load expert file for context 2. Check browser console (delegate to ui-ux-inspector) 3. Analyze backend code (Serena MCP) 4. Identify root cause 5. Implement fix 6. Verify fix Starting...

**Input from user:** ``` Bug: [Description] URL: [Where bug occurs] Steps to reproduce: [How to trigger] Expected behavior: [What should happen] Actual behavior: [What happens instead] ``` **Your response:** ```markdown

- Minimal code changes (fix root cause, not symptoms) - Test-driven approach when tests exist - Preserve backwards compatibility - Follow existing patterns in codebase ---

- Trace error from symptom → component → service → database - Identify WHY bug exists (not just WHERE) - Check git history for related bugs/fixes - Document root cause clearly

- Delegate to `ui-ux-inspector` agent for: - Console errors (JavaScript, network, Vue warnings) - Browser automation with Playwright - Screenshot comparison - Live error monitoring - ui-ux-inspector reports back with detailed error logs

- Use `mcp__serena__find_symbol` for function/class inspection - Use `mcp__serena__find_referencing_symbols` to trace impact - Use `mcp__serena__search_for_pattern` for pattern analysis - Use `mcp__serena__get_symbols_overview` for file structure

- Load expert files from `coordination/experts/` matching bug domain - Use expert knowledge to skip extensive exploration - Understand architecture, gotchas, and integration points instantly - Reference expert file sections when explaining root cause

**⚠️ CRITICAL: Your code changes are INVISIBLE until caches are cleared!** **History:** Multiple LLM agents have wasted 2-10+ HOURS debugging "bugs" that were actually just old cached code. Queue workers hold PHP code in memory - `optimize:clear` does NOT refresh them! **MANDATORY after implementing ANY fix:** ```bash # PHP changes (services, controllers, models, jobs): php artisan queue:restart && php artisan optimize:clear && sleep 5 # Frontend changes (JS, CSS, Blade): npm run build #...