LUME Rehearsal Capture Overwhelming Update

Date: 2026-05-28 Primary live host: Mac4 Primary storage target: K11 Reference project root on Mac4: `[home]/dev/lume-commerce-live/viz/lume-pcloud` Document destination on Mac1: `[home]/Desktop/lume-commerce/viz/lume-pcloud/Docs/LUME_REHEARSAL_CAPTURE_OVERWHELMING_UPDATE_2026-05-28.md` The companion document converts this Tier 0 capture lane into the shared K11/Mac4/Mac5 rehearsal-bundle architecture and explains how K11 Pose Coach fits into the same storage/training path. The rehearsal-capture stack has crossed from concept into a working Tier 0 capture lane. The critical achievement is not that every sensor is perfect yet. The critical achievement is that LUME now has a boring, survivable, inspectable recording path that can record a long physical rehearsal, preserve labels, survive interruption, write explicit session metadata, and route the completed bundle to K11 with remote checksum verification. This matters because every more advanced choreography layer depends on clean session evidence. The machine can now collect a body session without requiring Unity, MotionMix, mocopi, Web Lab, iPhones, or any DJ command path to be alive. The reason `tmux` is explicit in the route is important. Direct Codex-launched ffmpeg could list the physical cameras but got zero frames from them. The same ffmpeg capture launched inside `tmux` successfully captured an Insta360 frame and then full MP4 test sessions. macOS Camera privacy already grants access to `Terminal` and `tmux`, so the production route intentionally uses `tmux` as the camera-permission context. This is not a hack around recording quality. It is an operating-system permission boundary being made explicit and stable. K11 is now a storage target, not a live dependency. The current stack does not live-write the only copy directly over the network, because that would make the rehearsal vulnerable to Wi-Fi, Tailscale, SSH, sleep, and transient Windows file-system stalls. The chosen route records locally first, then immediately verifies K11 upload after the take. This is the correct reliability posture for a weighted freestyle session: capture first, transport second, analyze third.