chore: dissolve skill, content migrated to docs.fritzlab.net lodge/

Per decisions/2026-07-20-one-canon-knowledge-architecture; canon landed
via docs#142 (a0e98f75). Reference files deleted per the sites-household
deletions manifest; SKILL.md and README.md are now tombstones. Repo is
retained SOLELY to host .gitea/workflows/backup-ha.yaml (live nightly
Lodge HA backup using this repo's Actions secrets) until the operator
relocates it; that workflow is untouched.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

.gitea/workflows/backup-ha.yaml

@@ -0,0 +1,50 @@
+name: backup-lodge-ha
+# Nightly export of the lodge HA config (scripts/automations/dashboards/helpers)
+# into dfritz/home-assistant lodge/. Secrets: HA_TOKEN (lodge HA long-lived
+# token), GIT_TOKEN (ops PAT with write:repository). Lives in this repo because
+# ops has admin here; move to dfritz/home-assistant if its owner adds the
+# HA_TOKEN secret there.
+on:
+  schedule:
+    - cron: '37 9 * * *'   # 04:37 America/Chicago during CDT (03:37 CST)
+  workflow_dispatch: {}
+  push:
+    branches: [main]
+    paths: ['.gitea/workflows/backup-ha.yaml']
+
+jobs:
+  backup:
+    runs-on: fritzlab
+    timeout-minutes: 15
+    steps:
+      - name: clone mirror repo
+        run: git clone "https://ops:${{ secrets.GIT_TOKEN }}@code.fritzlab.net/dfritz/home-assistant.git" mirror
+
+      - name: install python deps
+        run: pip install --break-system-packages --quiet websockets pyyaml
+
+      - name: export lodge HA config
+        working-directory: mirror
+        env:
+          HA_TOKEN: ${{ secrets.HA_TOKEN }}
+        run: |
+          rm -rf lodge/scripts lodge/automations lodge/dashboards
+          python3 lodge/export.py
+
+      - name: commit and push if changed
+        working-directory: mirror
+        run: |
+          git config user.name "lodge-ha-backup"
+          git config user.email "ops@fritzlab.net"
+          git add lodge/
+          if git diff --cached --quiet; then echo "no changes"; exit 0; fi
+          git commit -m "lodge: automated HA config export"
+          git push
+
+      - name: notify on failure
+        if: failure()
+        uses: https://code.fritzlab.net/action/notify-email@v1
+        with:
+          status: failure
+          summary: "Lodge HA config backup failed"
+          auto-log: 'true'

README.md

@@ -1,3 +1,10 @@
-# thelonglakelodge
+# thelonglakelodge — dissolved
 
-The Long Lake Lodge skill repo
+This skill repo was dissolved per the 2026-07-20 one-canon knowledge
+architecture decision. The Long Lake Lodge knowledge lives at
+https://docs.fritzlab.net/lodge/ — update the docs site, not this repo.
+
+**This repo is retained SOLELY to host `.gitea/workflows/backup-ha.yaml`**, a
+live nightly Home Assistant config backup that uses this repo's Actions
+secrets (HA_TOKEN, GIT_TOKEN). Do not archive or delete the repo, and do not
+touch that workflow, until the operator relocates it.

SKILL.md

@@ -1,52 +1,31 @@
 ---
 name: thelonglakelodge
 description: >
-  Activate this skill for any work related to The Long Lake Lodge short-term rental.
+  DISSOLVED. Do not use. The Long Lake Lodge knowledge lives in the
-  TRIGGER when: user mentions the lodge, Long Lake Lodge, Siren, Polk Burnett, Siren Telecom,
+  canonical docs site: https://docs.fritzlab.net/lodge/
-  utilities, rental, reservations, Airbnb, VRBO, garbage, electricity, thelonglakelodge.com.
+user-invocable: false
-user-invocable: true
 ---
 
-<quick-context>
+# thelonglakelodge — dissolved
-- Address: 7251 County Road B, Siren, WI 54872
-- Names: The Lodge, Long Lake Lodge
-- Public site: thelonglakelodge.com — hosted via fritzlab sjc001 (see fritzlab skill)
-- Home Assistant: home.thelonglakelodge.com — proxied via sjc001 remote-proxy to 172.24.24.50
-</quick-context>
 
-<safety>
+This skill was dissolved per the one-canon knowledge architecture decision
-- Utility and access info is tenant-facing — verify accuracy before updating.
+(decisions/2026-07-20-one-canon-knowledge-architecture on docs.fritzlab.net).
-</safety>
+All content migrated to the canon in docs#142 (a0e98f75):
 
-<style>
+- https://docs.fritzlab.net/lodge/ — landing page
-- Keep references low token count, organized with XML tags.
+- reference/home-assistant.md → lodge/home-assistant.md
-- State what IS, not what happened.
+- reference/locks.md → lodge/locks.md
-- MUST keep this skill up to date. Knowledge lives HERE, not in memory.
+- reference/utilities.md → lodge/utilities.md
-</style>
+- reference/website.md → lodge/website.md
+- reference/boat.md → household/boat.md (shared boat page)
 
-<references>
+Do not add knowledge here. Update https://docs.fritzlab.net instead.
-  <reference file="reference/utilities.md"
-    summary="Lodge utilities: electricity and gas (Polk Burnett), garbage, internet (Siren Telecom)"
-    categories=["utilities"]
-    keywords=["garbage", "electricity", "gas", "water", "WiFi", "utilities", "Polk Burnett", "Siren Telecom", "internet"] />
-</references>
 
-<references>
+## Why this repo still exists
-  <reference file="reference/boat.md"
-    categories=["water"]
-    keywords=["boat", "dock, "launch"] />
-</references>
 
-<references>
+This repo is retained SOLELY to host `.gitea/workflows/backup-ha.yaml` — a
-  <reference file="reference/home-assistant.md"
+live nightly Home Assistant config backup (lodge HA → dfritz/home-assistant)
-    summary="Home Assistant: access/WS API, dual Nest integration (cloud + Matter), 2026-06-15 Matter fabric loss + recommission steps, main Lovelace dashboard"
+that depends on this repo's Actions secrets (HA_TOKEN, GIT_TOKEN). Do not
-    categories=["home-automation"]
+archive or delete this repo, and do not touch that workflow, until the
-    keywords=["home assistant", "HA", "home.thelonglakelodge.com", "matter", "nest", "thermostat", "climate", "dashboard", "lovelace", "HVAC", "in floor heating", "environmentals", "core_matter_server", "172.24.24.50"] />
+operator relocates it (target: dfritz/home-assistant, once its owner adds
-</references>
+the HA_TOKEN secret there — see the note in the workflow header).
-
-<references>
-  <reference file="reference/website.md"
-    summary="Lodge website: Latchkey managed-website service (latchkey-sites bucket, sites anycast edge, auto-TLS), Manage-files editing, /welcome PDF stub"
-    categories=["website"]
-    keywords=["website", "thelonglakelodge.com", "welcome packet", "PDF", "welcome.pdf", "/welcome", "Latchkey", "managed-website", "Manage files", "custom_domains", "cd-tll0001"] />
-</references>

reference/boat.md

@@ -1,15 +0,0 @@
----
-name: boat
-description: Boat and Dock Information
----
-
-There is not a boat provided
-
-<dock>
-The dock has room to dock a boat
-</dock>
-
-<public-launch>
-Public DNR launch located at 23754 Long Lake Road (just around the corner from the lodge). 
-It is not a paved launch, it's gravel. 
-</public-launch>

reference/home-assistant.md

@@ -1,87 +0,0 @@
-# Home Assistant
-
-<overview>
-HA OS at `home.thelonglakelodge.com`, proxied via fritzlab sjc001 remote-proxy
-to `172.24.24.50:8123` (also directly reachable on the lab network). Supervisor
-Observer on `:4357` (read-only health, no auth). API token in `~/.env` as
-`HA_TOKEN` (long-lived user token — has core API + service calls, but NOT the
-`/api/hassio/*` Supervisor proxy → 401). No SSH (`:22` closed, no terminal addon).
-No automatic backups configured (`backup/info` → 0 backups).
-
-Local control via WebSocket: `wss://home.thelonglakelodge.com/api/websocket`,
-auth with `{"type":"auth","access_token":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:
-`POST /api/services/hassio/addon_restart {"addon":"core_matter_server"}`.
-</overview>
-
-<thermostats>
-## Nest thermostats are integrated TWICE
-
-The 8 Nest thermostats appear via two independent paths:
-- **Cloud (Google Nest)** — `nest` integration, entities `climate.*_google_nest`
-  (+ `climate.lodge_basement` = Basement Living Room) and per-zone
-  `sensor.*_temperature` / `sensor.*_humidity`. Reliable; cloud-dependent.
-- **Matter (local)** — `matter` integration via the `core_matter_server` addon,
-  entities `climate.*_nest`. Local control, but see incident below.
-
-8 zones: Office, Kitchen, Bunkhouse Kitchen (forced-air "HVAC"); Eat-in Kitchen,
-Primary Bathroom, Basement Living Room, Basement Bedroom, Tub Room (in-floor heat).
-Matter fabric id `1E5211CA4C7B5275`, node ids 1–5,7,8,9 (temp sensors are bridged
-endpoint-101 sub-devices of their thermostat node).
-
-`script.set_away_temperatures` (HVAC 55–78 / in-floor 55) and
-`script.set_occupied_temperatures` (HVAC 68–76 / in-floor 67) set all zones,
-targeting by **label**: `hvac` (3 forced-air) and `in_floor_heat` (5 in-floor),
-both applied to the cloud `*_google_nest` devices (resolved in-script via
-`label_devices(..) | map('device_entities') | ... | select('match','climate')`
-since the labels are on devices, not entities). Commands are **serialized one
-zone at a time with an 8 s delay** — firing all 8 at once trips the Google Nest
-SDM per-user `ExecuteDeviceCommand` rate limit (429 RESOURCE_EXHAUSTED). (Matter copies carry parallel
-`matter_hvac` / `matter_in_floor_heat` labels — used by the scripts before the
-2026-06-15 repoint to cloud.) `google_nest` labels all 8 cloud devices.
-</thermostats>
-
-<matter-outage>
-## Matter fabric loss (2026-06-15)
-
-At 2026-06-15 13:53 UTC an HA Core/Supervisor restart (Supervisor → 2026.06.1)
-left the `core_matter_server` addon (v8.5.0) with an **empty fabric** — all 11
-Matter devices report `node_not_found`, all 59 `climate.*_nest` etc. entities
-`unavailable`. Integration reconnects fine (config entry `loaded`); the server
-simply has zero nodes. Addon restart + config-entry reload do NOT restore them
-(storage lost, not transient), and there is no backup to restore from.
-
-Cloud Nest is unaffected → thermostat control intact via `*_google_nest`.
-
-Recovery = re-commission each thermostat on-site (non-destructive, no factory
-reset needed — Nest supports Matter multi-admin):
-1. On lodge WiFi, Google Home app (lodge account) → tap thermostat → Settings →
-   "Linked Matter apps & services" → "Link apps & services" → generate a Matter
-   setup code (11-digit / QR). Code is single-use, ~5 min TTL.
-2. HA → Settings → Devices & Services → Matter → Add device → enter the code.
-   Wait ~1–2 min; node appears (bridged temp sensor comes with it).
-3. Repeat per thermostat (one code at a time). Rename to match.
-4. Delete the stale unavailable Matter devices afterward.
-Then re-point dashboard climate tiles back to `climate.*_nest` if local control
-is wanted (see dashboard note).
-</matter-outage>
-
-<dashboard>
-## Main Lovelace (`lovelace` / "Overview", storage mode)
-
-Views: `main` (single grid card, columns:1, headed sections: locks/lights,
-Helpful Scripts, Water Sensors, then climate as three 2-col thermostat-card
-grids — **Lodge HVAC** (office, kitchen), **In-Floor Heat** (5 in-floor zones),
-**Bunkhouse** (bunkhouse kitchen)),
-`Environmentals` (history page), and `Lock Management`. Edit via
-`lovelace/config` / `lovelace/config/save` (WS).
-
-HVAC climate tiles point at the **cloud** `*_google_nest` entities (repointed
-off the dead Matter `*_nest` during the 2026-06-15 outage). The `Environmentals`
-page is three per-category vertical-stacks (Lodge HVAC / In-Floor Heat /
-Bunkhouse), each with Temperature, Humidity, and Heating/Cooling history-graphs
-(72h) scoped to that category's entities.
-If Matter is re-commissioned and local control is preferred, repoint these back.
-</dashboard>

reference/utilities.md

@@ -1,23 +0,0 @@
----
-name: utilities
-description: Lodge Utilities Information
----
-
-<electricity
-provider="Polk Burnett",
-
-/>
-
-<gas
-provider="Polk Burnett",
-
-/>
-
-<garbage
-
-/>
-
-<Internet Service Provider
-provider='Siren Telecom'
-
-/>

reference/website.md

@@ -1,51 +0,0 @@
-# Lodge website
-
-<overview>
-Static site at `thelonglakelodge.com` (+ `www`, a CNAME to the apex). Hosted
-by Latchkey's managed-website service ("Websites" in the app): the files
-live in the `latchkey-sites` Garage bucket under the `thelonglakelodge.com/`
-key prefix, and the Latchkey `sites` edge serves them over its anycast IPs
-with automatic Let's Encrypt TLS. No Traefik, no per-site bucket Ingress.
-Registered in `custom_domains` (org "Fritz Family", id `cd-tll0001`).
-</overview>
-
-<editing>
-## Update the site
-
-In the Latchkey app: **Websites → thelonglakelodge.com → Manage files** —
-upload (replaces by path), list, delete. Files publish immediately. The
-old git repo `~/code/git/code.fritzlab.net/websites/thelonglakelodge.com`
-+ `action/site-publish` flow is retired; edits go through the app now (or
-the API: `POST /v1/custom-domains/cd-tll0001/files`).
-
-DNS: apex A/AAAA → the sites anycast set (142.202.202.22 / .203.22 /
-23.145.176.22 + 2602:817:3000:ed6e::{202,203,176}:22); `www` CNAMEs the
-apex. Managed in `dns/authoritative/zone-templates/thelonglakelodge.com.j2`.
-</editing>
-
-<welcome-packet>
-## Welcome packet PDF (`/welcome`)
-
-`/welcome` and `/welcome.pdf` both serve the guest packet. The `/welcome`
-shortcut is the empty stub object carrying `x-amz-website-redirect-location:
-/welcome.pdf`; the managed-sites server follows that metadata internally
-(one hop) and streams the PDF — no browser-visible redirect.
-
-Update the PDF by re-uploading `welcome.pdf` via Websites → Manage files
-(or `POST /v1/custom-domains/cd-tll0001/files`). To recreate the `/welcome`
-stub if lost:
-
-```sh
-aws --profile sjc001 s3api put-object --bucket latchkey-sites \
-  --key thelonglakelodge.com/welcome --content-type text/html \
-  --website-redirect-location /welcome.pdf --body /dev/null
-```
-</welcome-packet>
-
-<policy-sync>
-## Guest-facing policy lives in two places
-
-Check-out time, quiet hours, occupancy, and local-contact details are stated
-both in the welcome PDF and in the quick-ref cards on `house-rules.html`.
-When updating any of these values, update BOTH or they will drift.
-</policy-sync>