Use Lodge Home Assistant token name

reference/home-assistant.md

@@ -4,7 +4,7 @@
 HA OS at `home.thelonglakelodge.com`, proxied via fritzlab sjc001 remote-proxy
 to the lodge LAN. Use the public HTTPS/WSS path; direct `172.24.24.50:8123` is
 unapproved IPv4 inventory, not an operational path. API token in `~/.env` as
-`HA_TOKEN` (long-lived admin token — core API + service calls + Supervisor:
+`LODGE_HA_TOKEN` (long-lived admin token — core API + service calls + Supervisor:
 WS `{"type":"supervisor/api","endpoint":...}` for JSON endpoints, REST
 `/api/hassio/addons/<slug>/logs` for text logs; `/api/error_log` is 404 —
 use WS `system_log/list`). No SSH (`:22` closed, no terminal addon).
@@ -13,7 +13,7 @@ No automatic Supervisor full-backup schedule. Local recovery backups include
 `post-matter-recommission-2026-07-15`.
 
 Local control via WebSocket: `wss://home.thelonglakelodge.com/api/websocket`,
-auth with `{"type":"auth","access_token":HA_TOKEN}`. Useful WS cmds:
+auth with `{"type":"auth","access_token":LODGE_HA_TOKEN}`. Useful WS cmds:
 `config_entries/get`, `config/device_registry/list`, `config/entity_registry/list`,
 `matter/node_diagnostics{device_id}`, `lovelace/config{url_path:null}` /
 `lovelace/config/save`. Addon control via REST service: