#334 Sherlock Phase 4: Dynamic Verifier Injection

PHASE 4: Dynamic Injection (Orchestration) CONTEXT: Sherlock suggests 'Topology-Driven Verifier Placement'. We can analyze the DAG to find 'vulnerable' nodes (high fan-in) or 'critical' nodes (DB writes). PROS: - Safety by default. Developers don't need to remember to add verifiers. CONS: - Compiler complexity. ARCHITECTURE: - Create VerifierInjector pass in WorkflowInterpreter (similar to logging injector). - Automatically wrap critical tasks in ReflexiveLoop based on policy. REQUIREMENTS: - DOCUMENTATION: Update docs/HIGHWAY_WORKFLOW_ENGINE_BOOK.md after implementation. - TESTING: Add comprehensive tests. Use ollama and deepseek-v3.1:671b-cloud model for testing (in tools/llm provider). - REGRESSION: No regression allowed. All @tests/integration/test_atomicity_baseline.py tests must pass.