diff --git a/restoration/source410/MUNGA_L4/L4GREND.CPP b/restoration/source410/MUNGA_L4/L4GREND.CPP
index e33ae5ee..f0ff284f 100644
--- a/restoration/source410/MUNGA_L4/L4GREND.CPP
+++ b/restoration/source410/MUNGA_L4/L4GREND.CPP
@@ -579,12 +579,20 @@ void
 //   * NON-REGRESSIVE: gauge A/B, three boots (unfixed x2, fixed x1) score
 //     identically on every head -- Mfd1 132/0, Mfd2 37/7, Mfd3 23/0 --
 //     against a ~6px across-boot noise floor.
-//   * NOT DIRECTLY OBSERVED CURED.  In all our A/B boots the heap tail
-//     happened to hold ZEROS, so the unfixed build already scored 0 extras
-//     and there was no visible artifact to remove.  That is the same luck
-//     the shipped binary has been enjoying.  The fix makes it guaranteed
-//     rather than lucky; confirming the operator's bar is gone needs a
-//     capture from a rig that was showing it.
+//   * OPERATOR-CONFIRMED CURED, 2026-07-30.  A full arena1 mission run on
+//     the pod rig (podrun.sh pod_render_norio, this build staged): "the
+//     artifact appears to be gone and the bleed from the control mode seems
+//     to be gone as well."  Both reported symptoms, one run, no fault.
+//
+//     The honest weight of that: it is ONE run of an INTERMITTENT,
+//     heap-content-dependent artifact, and a clean run is exactly what the
+//     UNFIXED build also produced on the gauge A/B rig.  So it is not
+//     logically airtight on its own.  What makes it convincing anyway is
+//     that the fix is deterministic by construction -- after it, no index
+//     in 64..255 can return anything but 0, whatever the heap holds -- and
+//     that the operator had been seeing the artifact repeatedly, across
+//     both this reconstruction and BT411.  Further clean runs strengthen
+//     it; a recurrence would mean a SECOND source, not a failed fix.
 //
 // A first "fixed" capture appeared to REGRESS the MFDs by ~2700px.  It was a
 // bad grab (caught mid-draw); the rebuild-and-rerun matched the unfixed