pub fn peak_memory_report() -> Option<String>Expand description
The end-of-run memory report — emitted ONLY when a memory-budget Fatal
fired during the run (user directive 2026-08-03: alert when needed, stay
quiet on clean runs). None otherwise, or when no peak is measurable.
It reports the kernel-tracked peak and says the document needs MORE — never a specific sufficient figure, because none is knowable from a truncated run: the fuse clamped the peak at 75% of the ceiling, and the streaming spill watermark itself derives from the ceiling, so the true requirement can only be found by rerunning higher. A document’s need scales with macro expansion and math density, not source bytes (the 131 MB math-dense witness needs ~23 GB resident just to stream through core), so this measured figure is the only honest lower bound there is.