Disable the 6 hot-tub/blinds IFTTT applets after iot-api soak (cutover 2026-07-04)

[science]

Context

The webapp backend was cut over from IFTTT to iot-api (PR #147, DI swap to IotApiClientFactory) and went fully live on 2026-07-04: all 4 HA gates ON (live_iot_hot_tub_heater, live_iot_hot_tub_cycle_ionizer, live_iot_hot_tub_ionizer, live_iot_dining_blinds), and every button (heater on/off, pump/run, blinds open/close) was exercised end-to-end through the production path (webapp → iot-api on misuse.org → Tailscale Funnel → t480 HA → Tuya/BroadLink).

The backend no longer calls IFTTT at all — the 6 hot-tub/blinds applets are dead code as of the cutover. The morning heating cycles from 2026-07-05 onward exercise the new path daily.

Task (after ~7 days of clean operation, ≈ 2026-07-11)

• Confirm daily heating + maintenance cycles ran correctly all week (no missed fires, no relay errors in backend logs / t480 HA logs)
• Disable (don't delete yet) the 6 hot-tub/blinds IFTTT applets: hot-tub-heat-on, hot-tub-heat-off, cycle_hot_tub_ionizer, and the dining-blinds open/close pair (see QUESTIONS.md in science/home-assistant for the full list/context)
• Verify applet run counts stay frozen for a few more days, then delete per the disable→observe→delete sequence
• Record the disables in docs/automation-sources/unified-backlog.csv (science/home-assistant)

Rollback (if the soak fails)

Swap IotApiClientFactory → IftttClientFactory in backend/public/index.php and redeploy — the applets still exist until the delete step above.

🤖 Generated with Claude Code