Per Andrey's debug approach (same as used on the oracle): render the actual
scene-vs-virtual-center correlations in the pixel domain and save them as a
scene sequence. Observability only - NO processing changes, the roll-bias
symptom is preserved.

- curt.pose_corr_save (checkbox "Pose test save 2D correlations"): save
  -POSE-RT-CORR2D.tiff - z=scenes (aligned with -POSE-RT-HYPER incl. NaN
  slices for failed/coasted scenes), tile grid of 16x16-pix cells, last LMA
  cycle per scene, ImageDtt.corr_partial_dbg convention as CuasMotion CORR2D.
  Lean engine only (the oracle does not expose its correlation tiles).
- curt.pose_full (checkbox "Pose test ALL tiles (ignore calibration)"):
  temporarily drop the 150-tile filter and use all strength-selected (~1074)
  tiles; -POSE-RT-TILE-CALIB is neither read NOR written so a debug run
  never pollutes the persistent tile calibration.
- leanMeasure/leanFitScene: optional corr_pd_out holder (last-cycle PD tiles).

Context: lean run v013-LEAN-01 confirmed the v*tau signature on az/tilt
(implied tau = 8.4/8.0 ms = mb_tau) but showed a constant +0.52 mrad roll
bias; peaks ~50% wider than oracle on common tiles (suspect: consolidation
averages /16 while oracle sums pairs -> effective fat-zero 16x larger).
These debug outputs are for inspecting exactly that before changing the
processing.

Verified: mvn -DskipTests clean package OK.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>