How the hidden-set evaluation invokes whest run

We reproduced this memory growth on the in-process and flopscope-server evaluation paths in flopscope 0.12.3, with standalone reproductions and measurements in `BudgetAccumulator.record()` keeps every closed context's raw op log for the life of the process, so memory grows with each scored MLP · Issue #321 · AIcrowd/flopscope · GitHub. Each closed BudgetContext appends its diagnostic_ops list to the BudgetAccumulator. Across five 1024x16 MLPs, 504aldo’s V16b retains 18,970 OpRecord entries and adds 1.95 MiB heap per MLP, while a 50,000-op estimator adds 19–25 MiB per MLP. A one-line record() change gated by retain_op_log drops retained heap across eight 15,000-op contexts from 44.905 MiB to 0.045 MiB with identical flops_used; with the module test fixture enabling retain_op_log, the scan-oracle checks pass and the full 10,702-test suite passes.