Problem
AgentConfig.hallucinationGuard.checks is only consulted by HallucinationGuard.validate(). The executor never calls that method — it calls validateFilePath() and validateCode() (packages/core/src/executor/executor.ts), and both bypass enabledChecks entirely (packages/hallucination-guard/src/guard.ts).
Impact
- The guard cannot be disabled through the documented configuration surface.
- Any ablation/benchmark that toggles
enabledChecks silently measures nothing. This invalidated the guard arm of the SDD ablation benchmark (benchmarks/results/2026-07-12-sdd-ablation.md).
Fix
Have validateFilePath() / validateCode() honor enabledChecks (skip the corresponding check when disabled), so the guard is genuinely configurable and ablatable. Add a test that a fully-disabled guard performs no checks on the executor path.
Found by the frozen 30-task ablation benchmark.
Problem
AgentConfig.hallucinationGuard.checksis only consulted byHallucinationGuard.validate(). The executor never calls that method — it callsvalidateFilePath()andvalidateCode()(packages/core/src/executor/executor.ts), and both bypassenabledChecksentirely (packages/hallucination-guard/src/guard.ts).Impact
enabledCheckssilently measures nothing. This invalidated the guard arm of the SDD ablation benchmark (benchmarks/results/2026-07-12-sdd-ablation.md).Fix
Have
validateFilePath()/validateCode()honorenabledChecks(skip the corresponding check when disabled), so the guard is genuinely configurable and ablatable. Add a test that a fully-disabled guard performs no checks on the executor path.Found by the frozen 30-task ablation benchmark.