Per Andrey (2026-07-05): today's problems came from jumping over the standalone
certification of conditionSceneToGpu (single caller inside the pose test, never
image-tested by itself). Test and debug the ingest+render chain FIRST, only then
return to the pose test.

NEW class cuas/rt/CuasRender (the start of the dedicated renderer per the spec
in imagej-elphel-internal handoffs/2026-07-05_cuas_rt_dataflow_and_grids.md par.6:
virtual uniform grid always, raw center DSI disparity, jp4+CuasConditioning
pixels, QuadCLT borrow-only, static methods):
- renderSceneVirtual(): tasks at pose (ALL valid-disparity tiles) -> convert
  (erase=1, NaN outside tasks) -> 16 per-sensor renders + consolidated (NaN-aware
  weighted average) merged render. No correlation.
- testRenderSequence(): per scene raw /jp4/ -> conditionSceneToGpu -> render at
  BORROWED stored pose + stored ERS rates (the exact sources the oracle DBG
  renders use) -> saves <center>-CUAS-RT-RENDER.tiff hyperstack
  [t: s00..s15, merged][z: scenes], slice-by-slice comparable to
  -CUAS-INDIVIDUAL-CUAS-DBG / -CUAS-MERGED-CUAS-DBG.

New checkbox "CUAS RT render test (ingest+render)" (curt.rend_test), takes
precedence over the pose test in the curt_en branch.

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