BT410 5.3.87: OPERATOR-CONFIRMED -- both artifacts gone on a live mission

Full arena1 mission on the pod rig (podrun.sh pod_render_norio, 5.3.83-86
staged), run clean to steady state with no fault.  Operator: "the artifact
appears to be gone and the bleed from the control mode seems to be gone as
well."

Both reported symptoms -- the yellow-orange bar on the colour head and the
bleed into the MFDs -- from the one uninitialised read, closed by the one
zero-fill.

WEIGHT OF THE EVIDENCE, stated plainly rather than banked as a win:

  This is ONE run of an INTERMITTENT, heap-content-dependent artifact.  A
  clean run is exactly what the UNFIXED build also produced on the gauge A/B
  rig, three boots running, which is the whole reason the fix could not be
  verified there.  So the observation is not logically airtight on its own.

  What makes it convincing anyway is the shape of the fix rather than the
  count of runs: after it, no index in 64..255 can return anything but zero,
  whatever the heap holds.  The behaviour is deterministic by construction,
  where before it was a lottery.  Combined with the operator having seen the
  artifact repeatedly across BOTH this reconstruction and BT411, one clean
  run on the rig that was showing it is meaningful.

  Further clean runs strengthen it.  A recurrence would mean a SECOND source
  -- most likely whatever blits the *CRIT/*HEAT silhouettes, still
  unidentified, still carrying 1500-2500px of index 231 apiece -- and NOT a
  failed fix.  That distinction is worth keeping straight if it ever comes
  back.

Still open and unchanged by this: the 354px runtime-generated cluster, and
which widget blits the 231-bearing avatar art.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

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