ruling: phase0-comrak-002 (mimalloc) ACCEPTED, scoped to the comrak CLI workload

Human ruling on the needs-human-review allocator swap (+4.6%, CI
[+3.3%,+5.8%]): accepted as a real win for the measured comrak CLI
single-stream markdown-render workload, explicitly not a blanket
mimalloc mandate. Ledger row stays needs-human-review (append-only);
the ruling is documented in results/rulings/phase0-comrak-002.md and
reflected in the case study.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EcKPWQ3MQD4NdEHwar96u2

results/phase3/02-build-flags-and-allocators.md

@@ -39,6 +39,14 @@ every workload, fragmentation pattern, and concurrency scenario the
 target will meet in production. The pipeline measured a real win and
 then **refused to auto-ship it**, tagging it for a human ruling instead.
 
+**Human ruling (`results/rulings/phase0-comrak-002.md`): ACCEPTED,
+scoped to the comrak CLI single-stream markdown-render workload** — a
+real win for the measured use, deliberately *not* a blanket "always use
+mimalloc" mandate. The tier forced the judgment; the judgment is bounded
+and written down. The ledger row stays `needs-human-review` (append-only
+records what the pipeline decided); the ruling is the human layer on
+top.
+
 ## What the pair demonstrates
 
 The cheap classes are not lesser — class 1 produced this project's