docs: record HA deployment details + access method in DECISIONS

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

DECISIONS.md

@@ -21,6 +21,12 @@ Format: `YYYY-MM-DD: <decision> — <why>`
 - **2026-06-07: yfinance installed on steel141** via `pip --user --break-system-packages`
   (PEP 668). It was missing after the CT 166 → steel141 migration — the original
   "not firing" had two causes: no cron ever installed + this missing dependency.
+- **2026-06-07: HA side deployed on VM HA `192.168.0.146`** (`/config/scripts.yaml`
+  + `script.print_daily_briefing` in `configuration.yaml` `google_assistant.entity_config`;
+  backups in `/config/.backup/`). MQTT-discovery button entity id is
+  `button.pos_briefing_print_daily_briefing` (HA prefixes the device name). Access:
+  `ssh seth@192.168.0.146` (key auth), `bash -lc "ha core check|restart"`, services via
+  `$SUPERVISOR_TOKEN` → `http://supervisor/core/api/`. See `docs/ha-setup.md`.
 - **2026-06-07: paho-mqtt v1 callbacks (`CallbackAPIVersion.VERSION1`).** paho 2.1.0
   is installed for `claude`; matches the working lgtv bridge. One-time deprecation
   warning at startup is harmless.