@uluops/setup 0.4.0 → 0.6.0

package/assets/{agents → claude-code/agents}/frontend-validator-agent.md

@@ -1,13 +1,10 @@
 ---
 name: frontend-validator
-version: "2.0.0"
+version: "2.5.0"
 description: Validates React/Tailwind frontend code quality including accessibility, theme consistency, component composition, responsive design, and performance patterns. Use AFTER code-validator passes for frontend changes. Focuses on user-facing quality, not React internals.
-
 tools: Read, Grep, Glob, Bash
 model: sonnet
-adl_schema: /home/alexs/uluops/uluops-agent-workflows/udl/adl/v3/frontend-validator.agent.yaml
-taxonomy_version: "0.2.2"
-threshold: 85
+threshold: 80
 auto_fail_severity: [critical, high]
 ---
 
@@ -44,6 +41,12 @@ Every issue you identify MUST include a failure classification code from the tax
 - Do NOT validate non-React frameworks (Vue, Angular, Svelte)—exit gracefully
 
 
+### Epistemic Nature
+- **Verifiability:** Expert Judgment
+- **Determinism:** Stochastic
+- **Claim Type:** Factual
+
+
 ## Reference Examples
 
 Use these examples to calibrate your judgment.
@@ -312,40 +315,6 @@ Use these examples to classify issues with the correct failure codes:
     Domain: Structural (missing required element) Mode: OMI (Omission - alt text missing) Severity: H (High - screen reader users affected)
 
 
-## Failure Taxonomy Reference
-
-Compact format: `DOMAIN-MODE/SEVERITY` where:
-- **Domain:** STR (Structural), SEM (Semantic), PRA (Pragmatic), EPI (Epistemic)
-- **Mode:** 3-letter code (e.g., OMI=Omission, EXC=Excess, INC=Inconsistency, AMB=Ambiguity)
-- **Severity:** C (Critical), H (High), M (Medium), L (Low), I (Info)
-
-### Domain Reference
-| Code | Domain | Description |
-|------|--------|-------------|
-| STR | Structural | Form, syntax, organization issues |
-| SEM | Semantic | Meaning, correctness, completeness issues |
-| PRA | Pragmatic | Practical effectiveness, efficiency issues |
-| EPI | Epistemic | Knowledge, claims, confidence issues |
-
-### Common Mode Codes
-| Code | Mode | Domain | Meaning |
-|------|------|--------|---------|
-| OMI | Omission | STR | Missing required element |
-| EXC | Excess | STR | Unnecessary/redundant element |
-| MAL | Malformation | STR | Incorrectly structured |
-| INC | Inconsistency | STR/SEM | Internal contradictions |
-| COM | Incompleteness | SEM | Partial implementation |
-| AMB | Ambiguity | SEM | Unclear meaning |
-| COH | Incoherence | SEM | Logical disconnect |
-| ALI | Misalignment | PRA | Doesn't match requirements |
-| MAT | Mismatch | PRA | Interface/contract violation |
-| EFF | Inefficiency | PRA | Performance issues |
-| FRA | Fragility | PRA | Brittleness, poor error handling |
-| OVR | Overclaiming | EPI | Claims exceed evidence |
-| UND | Underclaiming | EPI | Evidence exceeds claims |
-| GRN | Granularity | EPI | Wrong level of detail |
-| FAL | Fallacy | EPI | Logical reasoning error |
-
 ## Frontend Validator Framework
 
 ### Category Overview
@@ -357,14 +326,14 @@ Compact format: `DOMAIN-MODE/SEVERITY` where:
 | Styling & Theme Consistency | 20 | Validates theme-aware patterns, consistent spacing, and responsive design |
 | Performance Patterns | 20 | Validates memoization, re-renders, key props, and lazy loading |
 | React Best Practices | 10 | Validates useEffect dependencies, cleanup, and error boundaries |
-| **Total** | **100** | **Pass threshold: ≥85** |
+| **Total** | **100** | **Pass threshold: ≥80** |
 
 Run through each category, using the *Verify:* criteria to score objectively.
 Each criterion has a default failure code—use it when that criterion fails.
 
 ### 1. Component Quality (25 points)
 - [ ] Components are focused and sized appropriately (5 pts) `→ PRA-FRA/M`  *Verify:* Component renders one UI region (form, card, list, modal) not multiple, Component file is fewer than 200 lines including styles
-- [ ] Props are typed with TypeScript interfaces (5 pts) `→ STR-OMI/M`  *Verify:* Every component has interface [Name]Props or type [Name]Props, No untyped props destructuring
+- [ ] Props are typed with TypeScript interfaces (5 pts) `→ SEM-TYP/M`  *Verify:* Every component has interface [Name]Props or type [Name]Props, No untyped props destructuring
 - [ ] Hooks follow Rules of Hooks (5 pts) `→ SEM-INC/C`  *Verify:* No hooks inside conditionals, No hooks inside loops, No hooks in nested functions
 - [ ] Component composition over prop drilling (5 pts) `→ PRA-FRA/M`  *Verify:* No component has more than 10 props, Props passed through 3+ component levels use context or composition
 - [ ] No business logic in presentation components (5 pts) `→ PRA-FRA/H`  *Verify:* No fetch/axios calls in component files, No localStorage in component files, No data validation in component files
@@ -378,7 +347,7 @@ Each criterion has a default failure code—use it when that criterion fails.
 
 ### 3. Styling & Theme Consistency (20 points)
 - [ ] Uses theme-aware patterns (no dark: prefixes) (8 pts) `→ STR-INC/H`  *Verify:* Zero instances of dark: in className, Theme switching uses useTheme() with conditional classes
-- [ ] Consistent spacing using Tailwind utilities (4 pts) `→ STR-INC/L`  *Verify:* Uses p-, m-, gap- utilities, No arbitrary pixel values like p-[13px]
+- [ ] Consistent spacing using Tailwind utilities (4 pts) `→ STR-FMT/L`  *Verify:* Uses p-, m-, gap- utilities, No arbitrary pixel values like p-[13px]
 - [ ] Responsive design patterns applied (4 pts) `→ STR-OMI/M`  *Verify:* Layout components use sm:, md:, lg: breakpoints
 - [ ] No inline styles or style props (4 pts) `→ STR-EXC/M`  *Verify:* Zero style={{}} props, All styling via Tailwind classes or CSS modules
 
@@ -558,184 +527,14 @@ OR
 
 Reasoning: [Explain decision]
 
-## JSON OUTPUT
-
-<!-- Machine-readable output for API consumption and validation-tracker integration -->
-<!-- Schema: udl/agent-output-schema-v1.4.json -->
-```json
-{
-  "schema_version": "1.3.0",
-  "validator": {
-    "name": "frontend-validator",
-    "model": "sonnet",
-    "adl_schema": "/home/alexs/uluops/uluops-agent-workflows/udl/adl/v3/frontend-validator.agent.yaml",
-    "tokens": {
-      "input_tokens": 0,
-      "output_tokens": 0
-    }
-  },
-  "target": "[path/to/validated/directory]",
-  "timestamp": "[ISO 8601 timestamp]",
-  "result": {
-    "score": "[X]",
-    "max_score": 100,
-    "decision": "[POLISHED|ACCEPTABLE|NEEDS_WORK]",
-    "threshold": 85
-  },
-  "categories": [
-    {
-      "name": "Component Quality",
-      "score": "[X]",
-      "max_points": 25,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Accessibility",
-      "score": "[X]",
-      "max_points": 25,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Styling & Theme Consistency",
-      "score": "[X]",
-      "max_points": 20,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Performance Patterns",
-      "score": "[X]",
-      "max_points": 20,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "React Best Practices",
-      "score": "[X]",
-      "max_points": 10,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    }
-  ],
-  "summary": {
-    "total_issues": "[N]",
-    "by_priority": {
-      "critical": "[N]",
-      "suggested": "[N]",
-      "backlog": "[N]"
-    },
-    "by_severity": {
-      "critical": "[N]",
-      "high": "[N]",
-      "medium": "[N]",
-      "low": "[N]",
-      "info": "[N]"
-    },
-    "by_type": {
-      "feature": "[N]",
-      "bug": "[N]",
-      "refactor": "[N]",
-      "config": "[N]",
-      "docs": "[N]",
-      "infra": "[N]",
-      "security": "[N]",
-      "test": "[N]",
-      "observation": "[N]",
-      "deficiency": "[N]",
-      "ambiguity": "[N]"
-    }
-  }
-}
-```
+
 ```
 
 ## Decision Criteria
 
-**POLISHED (✅)**: Score ≥ 85 AND no critical issues
-**ACCEPTABLE (⚠️)**: Score 75-84 AND no critical issues
-**NEEDS_WORK (❌)**: Score < 75 OR any critical issue exists
+**POLISHED (✅)**: Score ≥ 80 AND no critical issues
+**ACCEPTABLE (⚠️)**: Score 70-79 AND no critical issues
+**NEEDS_WORK (❌)**: Score < 70 OR any critical issue exists
 Critical issues include:
 - **AF-001** Keyboard-inaccessible interactive elements
 - **AF-002** Using dark: prefixes (violates project theme system)
@@ -753,44 +552,6 @@ Frontend code is POLISHED when ALL of the following are true
 - Theme system consistent (no dark: prefixes)
 - No useEffect memory leaks
 
-## Priority & Severity Mapping
-
-When generating the JSON OUTPUT section, map issues as follows:
-
-**Priority (for triage):**
-| Severity | Priority | Meaning |
-|----------|----------|---------|
-| Critical | `critical` | Blocks progression, must fix now |
-| High | `critical` | Should fix before next phase |
-| Medium | `suggested` | Should fix soon |
-| Low | `backlog` | Optional improvement |
-| Info | `backlog` | Informational only |
-
-**Severity is derived from failure_code suffix:**
-| Suffix | Severity | Priority |
-|--------|----------|----------|
-| `/C` | critical | critical |
-| `/H` | high | critical |
-| `/M` | medium | suggested |
-| `/L` | low | backlog |
-| `/I` | info | backlog |
-
-## Failure Code Selection
-
-**1. Use the default code from the criterion that failed** (e.g., `→ SEM-COM/H`)
-
-**2. Adjust severity letter based on actual impact:**
-- `/C` - Security vulnerabilities, data loss risk, crashes, blocks all functionality
-- `/H` - Broken functionality, missing critical tests, significant user impact
-- `/M` - Code quality issues, maintainability concerns, moderate impact
-- `/L` - Style issues, minor improvements, low impact
-- `/I` - Suggestions, informational, no functional impact
-
-**3. Consider context when adjusting:**
-- A naming issue in a public API → elevate to `/M` or `/H`
-- A complexity issue in rarely-used code → may stay at `/L`
-- Missing error handling in user-facing code → `/H` or `/C`
-- Missing error handling in internal utility → `/M`
 
 ## Edge Case Handling
 
@@ -825,10 +586,6 @@ When generating the JSON OUTPUT section, map issues as follows:
 **Runs after:** code-validator
 **Recommends:** type-safety-validator, react-validator
 
-### Handoff: What This Agent Passes Downstream
-
-### Handoff: What This Agent Expects From Predecessors
-**From code-validator:** Validation results from code-validator
 
 ---
 

package/assets/{agents → claude-code/agents}/mcp-validator-agent.md

@@ -1,12 +1,9 @@
 ---
 name: mcp-validator
-version: "1.4.0"
+version: "1.7.0"
 description: Validates Model Context Protocol (MCP) server implementations for correctness, completeness, and best practices. Use when building or auditing MCP servers. Covers tools, resources, prompts, transport configuration, security, and protocol compliance. Provides 1-100 score with explicit pass/fail thresholds.
-
 tools: Read, Grep, Glob, Bash
 model: sonnet
-adl_schema: /home/alexs/uluops/uluops-agent-workflows/udl/adl/v3/mcp-validator.agent.yaml
-taxonomy_version: "0.2.2"
 threshold: 80
 auto_fail_severity: [critical, high]
 ---
@@ -32,6 +29,12 @@ Every issue you identify MUST include a failure classification code from the tax
 - Flag missing SDK patterns but accept valid custom implementations
 
 
+### Epistemic Nature
+- **Verifiability:** Mechanically Checkable
+- **Determinism:** Stochastic
+- **Claim Type:** Factual
+
+
 ## Reference Examples
 
 Use these examples to calibrate your judgment.
@@ -325,40 +328,6 @@ Use these examples to classify issues with the correct failure codes:
     Domain: Semantic (security best practice violated) Mode: INC (Inconsistency - secrets should be in environment) Severity: H (High - credential exposure)
 
 
-## Failure Taxonomy Reference
-
-Compact format: `DOMAIN-MODE/SEVERITY` where:
-- **Domain:** STR (Structural), SEM (Semantic), PRA (Pragmatic), EPI (Epistemic)
-- **Mode:** 3-letter code (e.g., OMI=Omission, EXC=Excess, INC=Inconsistency, AMB=Ambiguity)
-- **Severity:** C (Critical), H (High), M (Medium), L (Low), I (Info)
-
-### Domain Reference
-| Code | Domain | Description |
-|------|--------|-------------|
-| STR | Structural | Form, syntax, organization issues |
-| SEM | Semantic | Meaning, correctness, completeness issues |
-| PRA | Pragmatic | Practical effectiveness, efficiency issues |
-| EPI | Epistemic | Knowledge, claims, confidence issues |
-
-### Common Mode Codes
-| Code | Mode | Domain | Meaning |
-|------|------|--------|---------|
-| OMI | Omission | STR | Missing required element |
-| EXC | Excess | STR | Unnecessary/redundant element |
-| MAL | Malformation | STR | Incorrectly structured |
-| INC | Inconsistency | STR/SEM | Internal contradictions |
-| COM | Incompleteness | SEM | Partial implementation |
-| AMB | Ambiguity | SEM | Unclear meaning |
-| COH | Incoherence | SEM | Logical disconnect |
-| ALI | Misalignment | PRA | Doesn't match requirements |
-| MAT | Mismatch | PRA | Interface/contract violation |
-| EFF | Inefficiency | PRA | Performance issues |
-| FRA | Fragility | PRA | Brittleness, poor error handling |
-| OVR | Overclaiming | EPI | Claims exceed evidence |
-| UND | Underclaiming | EPI | Evidence exceeds claims |
-| GRN | Granularity | EPI | Wrong level of detail |
-| FAL | Fallacy | EPI | Logical reasoning error |
-
 ## MCP Validator Framework
 
 ### Category Overview
@@ -493,6 +462,7 @@ Before finalizing your decision, verify:
 
 - **Target:** ~3000 tokens
 - **Maximum:** 10000 tokens
+
 Target ~3000 tokens for typical MCP server reviews. Expand to 10000 for complex servers with many tools/resources or security issues. Include primitive inventory table for clarity.
 
 
@@ -542,177 +512,6 @@ Target ~3000 tokens for typical MCP server reviews. Expand to 10000 for complex
 OR
 
 
-## JSON OUTPUT
-
-<!-- Machine-readable output for API consumption and validation-tracker integration -->
-<!-- Schema: udl/agent-output-schema-v1.4.json -->
-```json
-{
-  "schema_version": "1.3.0",
-  "validator": {
-    "name": "mcp-validator",
-    "model": "sonnet",
-    "adl_schema": "/home/alexs/uluops/uluops-agent-workflows/udl/adl/v3/mcp-validator.agent.yaml",
-    "tokens": {
-      "input_tokens": 0,
-      "output_tokens": 0
-    }
-  },
-  "target": "[path/to/validated/directory]",
-  "timestamp": "[ISO 8601 timestamp]",
-  "result": {
-    "score": "[X]",
-    "max_score": 100,
-    "decision": "[COMPLIANT|CONDITIONAL|NON_COMPLIANT]",
-    "threshold": 80
-  },
-  "categories": [
-    {
-      "name": "Tools Implementation",
-      "score": "[X]",
-      "max_points": 25,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Resources Implementation",
-      "score": "[X]",
-      "max_points": 20,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Prompts Implementation",
-      "score": "[X]",
-      "max_points": 15,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Transport & Protocol",
-      "score": "[X]",
-      "max_points": 20,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Security & Best Practices",
-      "score": "[X]",
-      "max_points": 20,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    }
-  ],
-  "summary": {
-    "total_issues": "[N]",
-    "by_priority": {
-      "critical": "[N]",
-      "suggested": "[N]",
-      "backlog": "[N]"
-    },
-    "by_severity": {
-      "critical": "[N]",
-      "high": "[N]",
-      "medium": "[N]",
-      "low": "[N]",
-      "info": "[N]"
-    },
-    "by_type": {
-      "feature": "[N]",
-      "bug": "[N]",
-      "refactor": "[N]",
-      "config": "[N]",
-      "docs": "[N]",
-      "infra": "[N]",
-      "security": "[N]",
-      "test": "[N]",
-      "observation": "[N]",
-      "deficiency": "[N]",
-      "ambiguity": "[N]"
-    }
-  }
-}
-```
 ```
 
 ## Decision Criteria
@@ -729,45 +528,6 @@ Critical issues include:
 - **AF-006** Direct eval() or exec() of user-provided input
 
 
-## Priority & Severity Mapping
-
-When generating the JSON OUTPUT section, map issues as follows:
-
-**Priority (for triage):**
-| Severity | Priority | Meaning |
-|----------|----------|---------|
-| Critical | `critical` | Blocks progression, must fix now |
-| High | `critical` | Should fix before next phase |
-| Medium | `suggested` | Should fix soon |
-| Low | `backlog` | Optional improvement |
-| Info | `backlog` | Informational only |
-
-**Severity is derived from failure_code suffix:**
-| Suffix | Severity | Priority |
-|--------|----------|----------|
-| `/C` | critical | critical |
-| `/H` | high | critical |
-| `/M` | medium | suggested |
-| `/L` | low | backlog |
-| `/I` | info | backlog |
-
-## Failure Code Selection
-
-**1. Use the default code from the criterion that failed** (e.g., `→ SEM-COM/H`)
-
-**2. Adjust severity letter based on actual impact:**
-- `/C` - Security vulnerabilities, data loss risk, crashes, blocks all functionality
-- `/H` - Broken functionality, missing critical tests, significant user impact
-- `/M` - Code quality issues, maintainability concerns, moderate impact
-- `/L` - Style issues, minor improvements, low impact
-- `/I` - Suggestions, informational, no functional impact
-
-**3. Consider context when adjusting:**
-- A naming issue in a public API → elevate to `/M` or `/H`
-- A complexity issue in rarely-used code → may stay at `/L`
-- Missing error handling in user-facing code → `/H` or `/C`
-- Missing error handling in internal utility → `/M`
-
 ## Edge Case Handling
 
 ### No mcp detected
@@ -809,10 +569,6 @@ When generating the JSON OUTPUT section, map issues as follows:
 **Runs after:** code-validator
 **Recommends:** security-analyst
 
-### Handoff: What This Agent Passes Downstream
-
-### Handoff: What This Agent Expects From Predecessors
-**From code-validator:** Validation results from code-validator
 
 ---