gauntlet-help

Diagnose gauntlet stop-hook failures by analyzing runtime artifacts like .gauntlet/config.yml, .gauntlet/.debug.log, and review JSON files. This process uncovers root causes by examining console logs and CLI outputs to pinpoint exactly what triggered the failure.

A gauntlet gate dispatch may stall in a CI wait state due to adapter health issues or configuration errors. Examine .gauntlet/config.yml, .debug.log, and check_*.log runtime artifacts to find the root cause and resolve the blockage.

Troubleshooting recurring gauntlet stop-hook issues requires console.*.log, check_*.log, review_*.json, and .gauntlet/.debug.log runtime artifacts. These files provide the structured evidence needed to diagnose and resolve repetitive failures.

Evidence-based diagnosis differentiates confirmed findings from inferences by explicitly citing sources from gauntlet runtime artifacts and CLI outputs. This distinction clarifies which root causes are verified facts and which are logical deductions for remediation.

Yes, you can check adapter health during gate failures by analyzing gauntlet logs and runtime artifacts. Examining .gauntlet/config.yml and .debug.log reveals adapter status and helps identify whether the adapter caused the failure.

The best way to find the root cause of a gauntlet CI wait scenario is by analyzing review_*.json, console.*.log, and .gauntlet/.debug.log. This evidence-based approach traces the failure back to its source for actionable remediation.