@uluops/setup 0.4.0 → 0.6.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 UluOps
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -10,13 +10,15 @@ Zero-friction installer for [UluOps](https://uluops.ai) agentic harnesses. One c
 npx @uluops/setup
 ```
 
+> **⚠️ Windows Users:** Native Windows is not yet supported. Please use **WSL2 (Ubuntu)** and run the setup inside your WSL environment.
+
 ## Supported harnesses
 
 | Harness | Status | Alias | Config |
 |---------|--------|-------|--------|
 | Claude Code | Fully supported (default) | `claude` | `~/.claude.json` |
 | OpenCode | Fully supported | `oc` | `~/.config/opencode/opencode.json` |
-| Gemini CLI | Agents + Commands | `gemini` | `~/.gemini/settings.json` |
+| Gemini CLI | Fully supported | `gemini` | `~/.gemini/settings.json` |
 | Codex | Coming soon | — | `~/.codex/config.toml` |
 
 ```bash
@@ -43,13 +45,16 @@ npx @uluops/setup --harness gemini-cli
 
 > Paths shown are for Claude Code (default). Gemini CLI installs agents as `.md` and commands as `.toml` to `~/.gemini/`. OpenCode installs agents to `~/.config/opencode/agents/`. Agent definitions and commands are transformed to the target harness format at install time from a single source.
 
-The installer runs five steps in sequence:
+The installer runs these steps in sequence:
 
 1. **Authenticate** — Validates your API key (or creates an account with `--signup`)
 2. **MCP config** — Writes tracker and registry server entries to the harness config
 3. **Definitions** — Copies pre-rendered agent definition files
-4. **Metrics hook** — Configures a post-agent hook for automatic run capture (Claude Code only)
-5. **Health check** — Verifies both API endpoints are reachable
+4. **Metrics hook** — Configures a post-agent hook for automatic run capture (Claude Code and Gemini CLI)
+5. **`ulu` CLI** *(optional)* — Offers to install `@uluops/cli` globally. Interactive runs are prompted (default Y); non-interactive runs skip unless `--with-cli` is passed. `--no-cli` always skips. The install is best-effort: if `npm install -g` fails (permissions, nvm prefix, etc.) the rest of setup still completes and a manual install command is printed.
+6. **Health check** — Verifies both API endpoints are reachable
+
+> When this setup installs the CLI, the install is recorded in the manifest so `--uninstall` removes it symmetrically. If the CLI was already on your PATH before running setup, it is left alone on uninstall.
 
 ## Usage
 
@@ -67,16 +72,7 @@ npx @uluops/setup --signup
 
 You'll be prompted for email and password. Account + API key are created automatically.
 
-**Restart your harness after setup to load agents.**
-
-### API key resolution
-
-The installer checks these sources in order:
-
-1. `--api-key <key>` flag
-2. `ULUOPS_API_KEY` environment variable
-3. `~/.uluops/credentials.json` (existing CLI auth)
-4. Interactive prompt
+> **🛑 IMPORTANT:** You must restart your harness (e.g., restart Claude Code) after setup to load the new agents and commands.
 
 ### Options
 
@@ -90,6 +86,8 @@ npx @uluops/setup [options]
   --scope <mode>       MCP config scope: "global" or "local" (default: global)
   --local-defs         Save definitions to ./uluops/ for review
   --shell              Write API key export to shell profile
+  --with-cli           Install @uluops/cli globally (skip prompt)
+  --no-cli             Skip @uluops/cli install (skip prompt)
   --skip-validation    Accept API key without server verification
   --list               Show available agents and workflows without installing
   --verify             Check installation health: manifest, files, MCP config, API connectivity (no changes)
@@ -98,6 +96,42 @@ npx @uluops/setup [options]
   -y, --yes            Skip confirmations
 ```
 
+### Advanced Commands
+
+#### Preview available agents (`--list`)
+Displays all agents and workflows included in the current version of the setup tool.
+
+```text
+  ⟨u⟩ ulu·ops v0.6.0 — available agents and workflows
+
+  WORKFLOWS
+  /workflows:post-implementation   Iterative validation after coding
+  /workflows:pre-implementation    Design validation before implementation
+  /workflows:prompt-audit          Strategic prompt quality audit
+
+  AGENTS (run individually)                          MODEL
+  /agents:code-validator           Validate cod...  sonnet
+  /agents:type-safety              Deep TypeScr...  sonnet
+  /agents:security-analyst         Comprehensiv...  sonnet
+  /agents:test-architect           Validate tes...  sonnet
+  ...
+```
+
+#### Check installation health (`--verify`)
+Validates your current installation against the local manifest and checks API connectivity.
+
+```text
+  ⟨u⟩ ulu·ops Installation Check v0.6.0
+
+  ✓ Manifest found (~/.uluops/manifest.json)
+  ✓ All 23 agents present in ~/.claude/agents/
+  ✓ MCP servers configured in ~/.claude.json
+  ✓ API connectivity: Tracker (Online)
+  ✓ API connectivity: Registry (Online)
+
+  All checks passed.
+```
+
 ### Examples
 
 ```bash
@@ -119,31 +153,13 @@ npx @uluops/setup --dry-run --api-key ulr_abc123
 # Persist API key in shell profile (~/.zshrc, ~/.bashrc, etc.)
 npx @uluops/setup --shell
 
-# Preview what's included without installing
-npx @uluops/setup --list
-
-# Check existing installation (manifest + file presence + API connectivity)
-npx @uluops/setup --verify
+# Install the ulu CLI globally alongside harness setup
+npx @uluops/setup --with-cli
 
-# Clean removal
-npx @uluops/setup --uninstall
+# Skip the CLI prompt entirely (interactive runs default to asking)
+npx @uluops/setup --no-cli
 ```
 
-## What's included
-
-### Agents & Workflows
-
-Setup installs the starter set of agent and workflow slash commands. Run `npx @uluops/setup --list` to see what's included.
-
-> Browse more agents, workflows, and pipelines at [registry.uluops.ai](https://registry.uluops.ai). Pipelines are available via the registry API and MCP tools — they are not installed locally.
-
-### MCP servers
-
-Both servers use `npx -y` so there's no global install required:
-
-- **uluops-tracker** — Validation run tracking, issue management, analytics
-- **uluops-registry** — Agent definition registry, versioning, rendering
-
 ## How updates work
 
 Re-running `npx @uluops/setup` is safe and idempotent:
@@ -155,27 +171,28 @@ Re-running `npx @uluops/setup` is safe and idempotent:
 
 Setup manages four surfaces: agent files, command files, MCP config entries, and the metrics hook. A manifest at `~/.uluops/manifest.json` tracks what was installed so `--uninstall` can cleanly reverse all changes. The manifest supports multiple harnesses — each gets its own installation state.
 
+## Troubleshooting
+
+- **Agents not appearing:** Ensure you have restarted your harness (Claude Code, etc.) after running setup. For Claude Code, simply exit and restart the CLI.
+- **MCP errors:** If the harness fails to start the MCP servers, ensure `npx` is available in your PATH. You can check your config at `~/.claude.json` or `~/.config/opencode/opencode.json`.
+- **API key rejected:** Verify your key at [app.uluops.ai](https://app.uluops.ai). If you are behind a corporate proxy, you may need to set `HTTPS_PROXY`.
+- **`@uluops/cli` install warning:** If setup warns it could not install the CLI globally (EACCES, nvm prefix mismatch, network), the rest of setup still completes. Run `npm install -g @uluops/cli` yourself when convenient — once it's on your PATH, every subsequent `npx @uluops/setup` will see it and skip the install step.
+- **Windows issues:** Remember that native Windows is not supported; you must run the installer and your harness within **WSL2**.
+
 ## Uninstall
 
 ```
 npx @uluops/setup --uninstall
 ```
 
-Removes only UluOps-managed files: agents, commands, MCP config entries, and shell profile export (if `--shell` was used). Your custom agents and other MCP servers are preserved. Uninstall iterates all harnesses recorded in the manifest.
+Removes only UluOps-managed files: agents, commands, MCP config entries, shell profile export (if `--shell` was used), and the global `@uluops/cli` package (only if this setup installed it — a CLI you installed yourself is left alone). Your custom agents and other MCP servers are preserved. Uninstall iterates all harnesses recorded in the manifest.
 
 ## Requirements
 
-- Node.js >= 20
-- At least one supported harness installed (Claude Code or OpenCode)
-- UluOps API key ([get one here](https://app.uluops.ai/settings/api-keys))
+- **Node.js:** >= 20.0.0
+- **Platform:** Linux, macOS, or WSL2 (native Windows not supported)
+- **Harness:** Claude Code, OpenCode, or Gemini CLI
+- **Auth:** UluOps API key ([get one here](https://app.uluops.ai/settings/api-keys))
 
-> **Global install:** If you install globally with `npm i -g @uluops/setup`, the binary is `uluops-setup`.
-
-## Platform support
-
-| Platform | Status |
-|----------|--------|
-| Linux | Supported |
-| macOS | Supported |
-| WSL2 | Supported |
-| Windows (native) | Not yet supported |
+---
+**Global install:** If you prefer, install once with `npm i -g @uluops/setup` then run `uluops-setup`.

package/assets/auto-tracker-save.mjs

@@ -0,0 +1,142 @@
+#!/usr/bin/env node
+
+/**
+ * Auto-Tracker-Save Hook for Gemini CLI & Claude Code
+ * 
+ * Event: AfterTool (Gemini CLI) / SubagentStop (Claude Code)
+ * 
+ * This hook parses the output of an agent run and automatically
+ * queues a save_run call to the UluOps Tracker.
+ */
+
+import { readFileSync } from 'node:fs';
+import { join } from 'node:path';
+
+function main() {
+  let input;
+  try {
+    input = JSON.parse(readFileSync(0, 'utf8'));
+  } catch (err) {
+    process.stderr.write('Failed to parse hook input: ' + err.message + '\n');
+    process.exit(1);
+  }
+
+  const { tool_name, tool_response, metadata, cwd } = input;
+
+  // Handle both Gemini CLI's invoke_agent and Claude Code's agent execution
+  // (In Claude Code, tool_name might be the specific agent tool if it's rendered as one)
+  const isAgentTool = tool_name === 'invoke_agent' || tool_name.startsWith('uluops-');
+  
+  if (!isAgentTool) {
+    process.stdout.write(JSON.stringify({ decision: 'allow' }));
+    return;
+  }
+
+  const content = tool_response?.llmContent || tool_response?.content || '';
+  if (!content) {
+    process.stdout.write(JSON.stringify({ decision: 'allow' }));
+    return;
+  }
+
+  // --- Parsing Logic ---
+  
+  // 1. Extract Agent Name
+  let agentName = input.tool_input?.agent_name || tool_name.replace(/^uluops-/, '');
+  if (agentName === 'invoke_agent') agentName = 'unknown-agent';
+
+  // 2. Extract Verdict and Score
+  // Broaden pattern to catch various agent output styles
+  const decisionMatch = content.match(/\*\*Verdict:\s*([A-Z_]+)/i) || 
+                        content.match(/\*\*Decision:\s*([A-Z_]+)/i) ||
+                        content.match(/Verdict:\s*([A-Z_]+)/i) ||
+                        content.match(/Decision:\s*([A-Z_]+)/i);
+  
+  const scoreMatch = content.match(/\(Score:\s*(\d+)\/100\)/i) ||
+                     content.match(/Score:\s*(\d+)/i);
+  
+  const decision = decisionMatch ? decisionMatch[1].toUpperCase() : 'PASS';
+  const score = scoreMatch ? parseInt(scoreMatch[1], 10) : 100;
+
+  // 3. Extract Summary
+  const summaryMatch = content.match(/### Executive Summary\n\n(.*?)(?:\n\n|###|$)/s) ||
+                       content.match(/Summary\n\n(.*?)(?:\n\n|###|$)/s) ||
+                       content.match(/## .*?\n\n(.*?)(?:\n\n|###|$)/s);
+  const summary = summaryMatch ? summaryMatch[1].trim().substring(0, 500) : `Auto-saved run for ${agentName}`;
+
+  // 4. Extract Recommendations & Failure Codes
+  const recommendations = [];
+  // Resilient pattern for list items containing a failure code
+  const lines = content.split('\n');
+  for (const line of lines) {
+    const codeMatch = line.match(/`([A-Z]{3}-[A-Z]{3}\/[CHMLI])`/);
+    if (codeMatch) {
+      const code = codeMatch[1];
+      // Try to extract title: everything before the first '(' or '`' or '-'
+      let title = line.replace(/^\s*[\*\-]\s*/, '') // remove bullet
+                      .split(/[`\(\-]/)[0] // take everything before first separator
+                      .trim();
+      
+      if (!title) title = `Issue ${code}`;
+
+      // Try to extract priority
+      const priorityMatch = line.match(/\((Priority: )?(critical|high|suggested|backlog)\)/i);
+      const priority = priorityMatch ? priorityMatch[2].toLowerCase() : 'suggested';
+
+      recommendations.push({
+        agent: agentName,
+        title: title.substring(0, 100),
+        priority,
+        failure_code: code,
+        description: 'Extracted via auto-save hook'
+      });
+    }
+  }
+
+  // 5. Project Name Detection
+  let project = 'default-project';
+  if (cwd) {
+    const parts = cwd.split('/');
+    // If we're in a sub-repo (like uluops packages), use the last two parts
+    if (parts.length > 2 && (parts[parts.length-2].startsWith('-') || parts[parts.length-2] === 'packages')) {
+      project = parts[parts.length-1];
+    } else {
+      project = parts.pop();
+    }
+  }
+
+  // --- Build Tail Call ---
+
+  const saveRunArgs = {
+    project,
+    workflow_type: 'auto-save',
+    agents: [{
+      name: agentName,
+      model: metadata?.model || 'gemini-1.5-pro',
+      decision,
+      score: score,
+      summary,
+      tokens: {
+        input_tokens: metadata?.input_tokens || 0,
+        output_tokens: metadata?.output_tokens || 0,
+        cache_creation_tokens: metadata?.cache_creation_tokens || 0,
+        cache_read_tokens: metadata?.cache_read_tokens || 0
+      }
+    }],
+    recommendations
+  };
+
+  const output = {
+    decision: 'allow',
+    systemMessage: `[hook] Auto-saving ${agentName} results to tracker (Project: ${project})...`,
+    hookSpecificOutput: {
+      tailToolCallRequest: {
+        name: 'mcp_uluops-tracker_save_run',
+        args: saveRunArgs
+      }
+    }
+  };
+
+  process.stdout.write(JSON.stringify(output));
+}
+
+main();

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

@@ -1,12 +1,9 @@
 ---
 name: api-contract-validator
-version: "2.0.0"
+version: "2.3.0"
 description: Validates API contract consistency between documentation, types, and implementation. Catches contract drift, breaking changes, and documentation staleness. Required for APIs consumed by external clients or other services. Prevents integration failures.
-
 tools: Read, Grep, Glob, Bash
 model: sonnet
-adl_schema: /home/alexs/uluops/uluops-agent-workflows/udl/adl/v3/api-contract-validator.agent.yaml
-taxonomy_version: "0.2.2"
 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 auto-fail GraphQL APIs—adapt validation to schema.graphql
 
 
+### Epistemic Nature
+- **Verifiability:** Expert Judgment
+- **Determinism:** Stochastic
+- **Claim Type:** Factual
+
+
 ## Reference Examples
 
 Use these examples to calibrate your judgment.
@@ -299,40 +302,6 @@ Use these examples to classify issues with the correct failure codes:
     Domain: Semantic (data exposure) Mode: INC (Inconsistency - internal data in public response) Severity: C (Critical - security concern, auto-fail)
 
 
-## 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 |
-
 ## API Contract Validator Framework
 
 ### Category Overview
@@ -463,6 +432,7 @@ Before finalizing your decision, verify:
 
 - **Target:** ~3500 tokens
 - **Maximum:** 8000 tokens
+
 Target ~3500 tokens for typical reviews. Include endpoint inventory table for all endpoints. Show exact schema diffs for contract drift. Expand for large APIs with many endpoints.
 
 
@@ -547,154 +517,7 @@ 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": "api-contract-validator",
-    "model": "sonnet",
-    "adl_schema": "/home/alexs/uluops/uluops-agent-workflows/udl/adl/v3/api-contract-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": "[PASS|FAIL]",
-    "threshold": 80
-  },
-  "categories": [
-    {
-      "name": "Endpoint Completeness",
-      "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": "Request Contract",
-      "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": "Response Contract",
-      "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": "Breaking Change Safety",
-      "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]"
-            }
-          ]
-        }
-      ]
-    }
-  ],
-  "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]"
-    }
-  }
-}
-```
+
 ```
 
 ## Output Examples
@@ -860,44 +683,6 @@ API contracts are aligned when ALL of the following are true
 - No breaking changes without versioning or deprecation
 - No auto-fail conditions triggered
 
-## 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
 
@@ -938,10 +723,6 @@ When generating the JSON OUTPUT section, map issues as follows:
 **Runs after:** code-validator
 **Recommends:** type-safety-validator
 
-### Handoff: What This Agent Passes Downstream
-
-### Handoff: What This Agent Expects From Predecessors
-**From code-validator:** Validation results from code-validator
 
 ---