gauntlet-status

To summarize gauntlet session results, run a status script that reads session logs and gate outcomes, automatically aggregating them into a concise report with counts, statuses, and log references for fast triage.

To identify failed gates in a gauntlet run, the status summary specifically isolates and lists failed gates alongside their corresponding logs, enabling fast triage and actionable insights in your development workflow.

Yes, you can compare current and previous gauntlet sessions by reading previous logs stored in the log directory, allowing you to track session health and gate outcome changes over time.

The best way to view gauntlet gate outcomes and session health in one view is to run a status script that surfaces a concise snapshot of the most recent gauntlet session, aggregating session results for quick assessment.

No dependencies are required to read gauntlet session logs and generate a status report; the execution and parsing requirements for the status script, logs, and failure details are satisfied within the existing environment.