Andrey's discriminator for the fold-vs-kernel-interaction question: with
rend_test + new 'RT render LoG isolation (identity krnl)' ON, saves
-CUAS-RT-RENDER-ID (identity kernels: q0=1, q1..3=0, CltExtra=0 - aberration
correction AND fractional offsets skipped), -ID-LOG-ORACLE (pixel LoG of -ID),
and -LOG-ONLY (pure-LoG kernels, CuasLogFold.uniformKernels(log_td)).
If -LOG-ONLY vs -ID-LOG-ORACLE residual persists, the fold/L0 is wrong; if it
collapses to the wrap floor, the aberration-kernel interaction is responsible.
Refactor: pixel-LoG application extracted to applyPixelLog(); log_test and
log_ident share the kernel fetch/restore (finally).

Evidence so far (offline, this evening's run): per-sensor high-bin tilt varies
s07 +1.3% .. s01 +2.4% with identical scene content => kernel-dependent;
per-quadrant deviation maps identical (no single-coefficient signature);
kx=0 column regionally incoherent (row-structure channel, separate issue).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>