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>

docs/benchmark/README.md

@@ -20,11 +20,17 @@ speed, so a fixed wall-clock limit was flaky.
 
 Before the protocol, in the same process, the spec times the frozen engine
 (`src/app/services/frozen-engine/leave-planner.core.frozen.mjs`, the engine at
-a871f8f) on the `two years` scenario, best of three, and prints
-`calibration\tfrozen two years best of 3\t<ms>`. Each scenario's budget is its
-multiplier times that calibration; the mean `planningMs` of its two measured
-repetitions must not exceed it. A scenario without a multiplier fails too.
-`#286` tightens the multipliers once the speed target is met.
+a871f8f) on the `two years` scenario, best of three, and prints the result.
+Each scenario's budget is its multiplier times that calibration; the mean
+`planningMs` of its two measured repetitions must not exceed it. A scenario
+without a multiplier fails too. `#286` tightens the multipliers once the speed
+target is met.
+
+The job log shows a Markdown table with one row per scenario, printed as soon
+as that scenario finishes. Each row gives both measured planning times, their
+mean, the budget, the ratio to the calibration, the multiplier, the outcome,
+placements, determinism and `ok`, `OVER` or `no budget`. The complete
+tab-separated report follows the table.
 
 | Scenario                    | Mean planning (s) | Ratio to calibration | Multiplier |
 | --------------------------- | ----------------- | -------------------- | ---------- |