2 Commits

Include renames

Author	SHA1	Message	Date
nessarandClaude Opus 5.5	3bbe989eca	test(benchmark): print a readable summary table ... Print the calibration and a Markdown table with one aligned row per scenario as soon as it finishes: both planning times, mean, budget, ratio, multiplier, outcome, placements, determinism and budget status. Write directly to stdout so Vitest adds no per-line headers. The complete TSV report still follows the table. Refs #281, #285 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-17 02:09:54 +02:00
nessarandClaude Opus 5.5	acdb19352a	ci(benchmark): gate scenario speed relative to the runner ... Before the protocol, time the frozen engine on the two-year scenario, best of three, and fail any scenario whose mean planning time exceeds its multiplier times that calibration. Multipliers come from development-machine ratios with about 1.5x headroom until #286 tightens them. The 300-second timeout stays only as a hang guard. The benchmark keeps running on push and pull_request events because the push run gates image publication. This replaces the absolute 300-second acceptance protocol named in #78. Refs #285 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-17 00:45:28 +02:00