Correct world-frame offset metadata: locked-in value is (0.230, 0.000, 0.175) m for 2026-05-19 (previous commit message mis-stated 0.225 due to a hardcoded string; actual data was 0.230).

Apply world-frame offset (dx, dy, dz) = (0.225, 0.0, 0.175) m to all 5 episodes of 2026-05-19 so all 32 episodes share one OptiTrack world frame. Per-episode _contact_meta.world_frame_offset_applied documents the bake. Segments, previews, tasks.json, segments.json refreshed.

Apply world-frame offset (dx, dy, dz) = (0.225, 0.0, 0.175) m to all 5 episodes of 2026-05-19 so all 32 episodes share one OptiTrack world frame. Per-episode _contact_meta.world_frame_offset_applied documents the bake. Segments, previews, tasks.json, segments.json refreshed.

Apply world-frame offset (dx, dy, dz) = (0.225, 0.0, 0.175) m to all 5 episodes of 2026-05-19 so all 32 episodes share one OptiTrack world frame. Per-episode _contact_meta.world_frame_offset_applied documents the bake. Segments, previews, tasks.json, segments.json refreshed.

Publish 2026-05-19 session + introduce multi-cam schema (view_left/middle/right). 5 episodes + segments; bad_frames + tasks + README + schema doc updated. Multi-cam rollout for 2026-05-10/11 still in progress (legacy mode1_v1/mode2_v1 paths remain valid until that wave finishes).

Add mode2_v1 schema — 73 pre-sliced clean segments from 27 source episodes (104.7 min, bad intervals excluded by construction). New ReactSegmentDataset + demo. No bad_frames.json filtering needed at the dataloader; data is constructively clean. mode1_v1 stays for backward compatibility. See segments.json + new README section.

Audit batch 1: post-trim numbers in docs/figures.md (#3); tasks.json 2026-05-11 note + trim_offsets lookup (#5, #8); bad_frames.json trim_offsets header (#8); dataloader default which_sensors='both' (#10); new freeze_intervals.json with per-event diagnostic signals (#12)

Drop 2026-03-23 right-only pilot (outdated); recompute totals across 27 bimanual recordings

Lead with robot-arm-free / human-hand collection — README hero + 'What's different' section, tasks.json gets operator/embodiment fields, recording.md explains setup, F7 adds Operator column

Reframe dataset as dynamics / world-model interaction data (not policy demos); document 2026-03-23 as right-sensor-only pilot; add active_sensors per-date in tasks.json; lead with hours and contact frames instead of episode count

Drop 2026-05-11/episode_{000,002} (no-contact test recordings)

Add tasks.json registry; README per-task configs and task-first schema