wiringlisted

# Wiring Verification When building infrastructure components, ensure they're actually invoked in the execution path. ## Pattern Every module needs a clear entry point. Dead code is worse than no code - it creates maintenance burden and false confidence. ## The Four-Step Wiring Check Before marking infrastructure "done", verify: 1. **Entry Point Exists**: How does user action trigger this code? 2. **Call Graph Traced**: Can you follow the path from entry to execution? 3. **Integration Tested**: Does an end-to-end test exercise this path? 4. **No Dead Code**: Is every built component actually reachable? ## DO ### Verify Entry Points ```bash # Hook registered? grep -r "orchestration" .claude/settings.json # Skill activated? grep -r "skill-name" .claude/skill-rules.json # Script executable? ls -la scripts/orchestrate.py # Module imported? grep -r "from orchestration_layer import" . ``` ### Trace Call Graphs ```python # Entry point (hook) .claude/hooks/pre-tool-use.sh ↓ # Shell wrapper calls TypeScript npx tsx pre-tool-use.ts ↓ # TypeScript calls Python script spawn('scripts/orchestrate.py') ↓ # Script imports module from orchestration_layer import dispatch ↓ # Module executes dispatch(agent_type, task) ``` ### Test End-to-End ```bash # Don't just unit test the module pytest tests/unit/orchestration_layer_test.py # NOT ENOUGH # Test the full invocation path echo '{"tool": "Task"}' | .claude/hooks/pre-tool-use.sh # VERIFY THIS WORKS ``` ### Document Wir