Overlap-ring design ratified 07/17 (handoffs/2026-07-17_pose_d5_overlap_ring_design.md):
- TP_MAX_IMG_SETS=4 ring; set 0 = the setup allocation, others lazy clones
  (same pitch asserted); images_h/gpu_images always alias the ACTIVE set so
  every consumer (conditioning, granular convert, pose_mchain_fill snapshot)
  follows the ring with zero call-site changes.
- tp_proc_img_set_select / _active / _ready_record; tp_proc_exec_conditioning_async
  = float two-map kernel on the bayer copy stream, ready event after it (ONE
  event = uploaded+conditioned); bayer_fence extended to cover the active set.
- test_img_set_ring_jna (case img_ring): sync-set0 vs async-set1 conditioning
  bit-exact + both set-independence directions; run_cases.sh ALL PASS;
  compute-sanitizer memcheck 0 errors.
Co-authored-by: Claude Opus 4.8 <claude-opus-4-8@anthropic.com>
Co-authored-by: Claude Fable 5 <claude-fable-5@anthropic.com>