IR, TV power sync, and the Unfolded Circle remote

• 15 learned IR sequences ported off the old ZHA setup (zha.issue_zigbee_cluster scripts) into named HA scripts publishing Z2M ir_code_to_send — HA 2026.4's native Infrared platform doesn't reach MQTT blasters yet.
• TV power sync: remote.living_room_tv (Android TV Remote integration) as intent + smart-plug power draw >40W as physical truth → IR power toggle only when they disagree. Threshold helpers start unknown after restart — the condition fails safe (a one-time miss per restart).
• Gaming chain: a container polls bluez BY NAME (Stratus+ MACs rotate) → retained MQTT → controllers-on = receiver to SAT/CATV + TV on; all-off (30s) = receiver to BD/DVD, then TV off.
• Unfolded Circle Remote 3: adopted via the Pi's stolen PSK first, then a fresh-flash claim. Its HA driver URL lives on the REMOTE (/api/auth/external/hass token registry) — pointed at wss://ha.fmm.house.
• UC IR learner limitation (bug-report material): it normalizes captures to a single frame; TVs in standby need contiguous multi-frame bursts. The emitter API happily SENDS full multi-frame PRONTO (we decoded the Tuya blob → µs timings → PRONTO and proved it), but the custom-codes store rejects it. Workaround: power button = HA script entity (TS1201 fires the real burst).
• The HA-side UC integration hard-hung HA's event loop at boot (100% CPU, logs frozen) — disabled; the remote's own driver doesn't need it.