LUME Reconciliation + Execution Playbook — Mac1 Canonical, Mac4 Patch Source

# LUME Reconciliation + Execution Playbook — Mac1 Canonical, Mac4 Patch Source **Written: 2026-05-02 evening. Mohamed offline. Single source of truth for every active pane.** **Source session: 3a30cf44-adb2-4160-a40d-2258245acd0d (compacted at 191%)** This file replaces all prior playbooks. It supersedes the earlier Mac4-as-author plan after verified state showed (a) Mac4 `lume-commerce` is not a clean standalone Git repo, (b) Mac1 has 13 staged files + 134 passed/6 skipped Python tests, (c) `LumeSonyMotionBridge.cs` does NOT decode Sony or emit LUMM — it only reacts to skeletons already received by `LumeMocopiReceiver` on :9702. The real missing bridge is upstream. 1. **Mac1 is the only committable LUME source of truth.** Mac1's `Assets/Scripts/` is canonical and has 13 staged files awaiting commit. Mac4 `lume-commerce` is not a clean Git repo — do NOT commit or `git mv` from Mac4. Mac4 is a **patch source**, not a Git author. 2. **The real Sony bridge is upstream, not in Unity.** Add `software/demo/sony_to_lumm_bridge.py` (or extend Mac1's `sensor-relay.js`) that consumes parsed Sony frames and emits actual LUMM datagrams to `<unity-host>:9702`. `LumeSonyMotionBridge` stays as the visual motion reactor only — it does not pack, decode, or emit anything. 3. **Mac4 visual/perf work is valuable but must be ported into Mac1 by hand.** Pull Mac4's `Assets/Lume/` into a temporary import folder on Mac1, port selected files into canonical paths, preserve Mac1 `.meta` for existing components, bring Mac4 `.meta` only for genuinely new assets.