From 2df1bce5ea2deac921addef998617dbe18b848cc Mon Sep 17 00:00:00 2001 From: Tony0410 <47945770+Tony0410@users.noreply.github.com> Date: Sun, 25 Oct 2026 03:40:26 +0800 Subject: [PATCH] wiki maintenance 2026-10-25: skills-index regen (302 skills/69 cats), freshness audit 0 stale, tailscale node table + CT201 route corrections - skills-index.md regenerated from live skill tree: 302 skills / 69 categories (4 skills moved to .archive/ since 10-24), 45 archived - freshness-20261025.txt: 0 stale, 101 fresh, 4 no-date of 105 pages - infrastructure/tailscale.md: node table rebuilt from live tailscale status --json (springroll-browser was missing; omarchybook + openmausbot now offline; all offline ages refreshed; homeassistant exit-node wording corrected) + CT201 serve routes corrected (443 AND 8443; /steel only on :443) - systems/homepage-dashboard.md: same CT201 route + false Traefik claim corrected - reports/communities-wa-social-media-audit-2026.md: re-verified against live WA source - incidents/2026-08-26-work-outlook-basic-auth-disabled.md: re-probed, still open - log.md: appended stocktake entry --- ...-08-26-work-outlook-basic-auth-disabled.md | 17 ++- infrastructure/tailscale.md | 119 ++++++++++-------- log.md | 65 ++++++++++ raw/stocktake/freshness-20261025.txt | 118 +++++++++++++++++ .../communities-wa-social-media-audit-2026.md | 23 +++- systems/homepage-dashboard.md | 20 ++- systems/skills-index.md | 18 ++- 7 files changed, 306 insertions(+), 74 deletions(-) create mode 100644 raw/stocktake/freshness-20261025.txt diff --git a/incidents/2026-08-26-work-outlook-basic-auth-disabled.md b/incidents/2026-08-26-work-outlook-basic-auth-disabled.md index a3a1fb8..2c60129 100644 --- a/incidents/2026-08-26-work-outlook-basic-auth-disabled.md +++ b/incidents/2026-08-26-work-outlook-basic-auth-disabled.md @@ -3,8 +3,8 @@ title: Work Outlook Mailbox — Basic Auth Disabled (Himalaya) type: incident status: open created: 2026-10-03 -updated: 2026-10-03 -verified_on: 2026-10-03 +updated: 2026-10-25 +verified_on: 2026-10-25 confidence: high tags: [email, himalaya, office365, oauth2, auth, incident] sources: [live-himalaya-debug, live-tcp-probe, cron-session-20260826_180700_a94098] @@ -12,11 +12,22 @@ sources: [live-himalaya-debug, live-tcp-probe, cron-session-20260826_180700_a940 # Work Outlook Mailbox — Basic Auth Disabled (Himalaya) -**Window:** first detected 2026-08-26; re-verified 2026-10-03 (still open) +**Window:** first detected 2026-08-26; re-verified 2026-10-03 and again 2026-10-25 (still open) **Status:** Open — blocked pending an OAuth2 path **Impact:** The agent cannot read or send from the `work` mailbox. Every work-email request is unanswerable until this is fixed. +**Re-verified 2026-10-25 (stocktake):** the failure is unchanged and still reproduces exactly. +`himalaya envelope list -a work -s 1` still returns: +``` +Error: + 0: cannot build IMAP client + 1: login not supported +``` +No remediation has landed since 2026-10-03 — the account still authenticates by password +against a tenant that advertises only `XOAuth2`. Fix Option 1 (OAuth2) remains the only +viable path and still requires Anthony's sign-in. + ## Symptoms ``` diff --git a/infrastructure/tailscale.md b/infrastructure/tailscale.md index c6e5d3d..c9f9d05 100644 --- a/infrastructure/tailscale.md +++ b/infrastructure/tailscale.md @@ -3,8 +3,8 @@ title: Tailscale type: infrastructure status: active created: 2026-07-26 -updated: 2026-10-21 -verified_on: 2026-10-21 +updated: 2026-10-25 +verified_on: 2026-10-25 confidence: high tags: [tailscale, vpn, networking, infrastructure] --- @@ -19,66 +19,68 @@ WireGuard-based mesh VPN connecting all homelab hosts and providing HTTPS access - **Primary node:** CT460 (`hermes.kangaroo-eel.ts.net`, `100.118.5.51`) - **Runtipi node:** CT201 (`runtipi.kangaroo-eel.ts.net`) -## Tailscale Node Inventory (verified 2026-10-21) -Full node list from `tailscale status` — **51 non-funnel nodes** (50 live IPv4 peers + `hermes` itself). Offline peers are listed with their last-seen age. +## Tailscale Node Inventory (verified 2026-10-25) +Full node list from `tailscale status` — **52 non-funnel nodes** (51 live IPv4 peers + `hermes` itself). Offline peers are listed with their last-seen age. Re-verified 2026-10-16: the 2026-10-11 table had drifted (15 nodes missing, several states wrong). Re-verified 2026-10-16: `omarchymac` (100.84.180.69) added; `mattermost` state, offline ages and the omni/omarchymac rows refreshed from `tailscale status`. Re-verified 2026-10-19 00:2x: three live peers had never been listed — `guest-vps` (100.117.14.84, online), `openmausbot` (100.91.214.91, online) and `openmausbot-vm` (100.77.107.30, online) — added; `mattermost` offline age 26d → **29d**. Re-verified 2026-10-21 03:0x: the 2026-10-19 table had drifted again — **`octop` (100.92.163.122), `springroll` (100.100.153.125), `openmausbot` and `openmausbot-vm` were missing from the table body** (only mentioned in prose), `omarchymac` had gone offline (online → idle/offline 3d), and every offline age was stale. Table rebuilt from `tailscale status --json`, keyed on DNS name rather than `HostName` (the JSON `HostName` for `freshrss` is `ct260`, and both `omniroute` nodes share the hostname `omniroute`). Container states cross-checked against live `pct list` on `pve` (100.96.100.82) and `m93p` (100.104.51.98): CT255 (mattermost) stopped, CT601 (omni) stopped, CT299 (sftpgo) running, CT600 (omniroute) running. +Re-verified 2026-10-25 03:1x (stocktake): table rebuilt again from `tailscale status --json` — **`springroll-browser` (100.109.221.91) was missing entirely** and has been added. **`omarchybook` (100.107.9.100) and `openmausbot` (100.91.214.91) have both gone offline** (online → idle/offline 3d) and `openmausbot` is no longer a live peer despite its m93p LXC (CT1264) still running `tailscale` — the node itself has stopped connecting. Every offline age was refreshed (e.g. `mattermost` 31d → **35d**, `omni` 64d → **68d**, `elementsynapse` 91d → **95d**, `ubuntu-server-xfce` 60d → **64d**, `omarchymac` 3d → **7d**). `m93p` (100.104.51.98) now reads **idle/offline 13m ago** — the peer record is stale, but the host is plainly reachable (both `pct list` probes and the SSH session to CT201/CT460 during this audit succeeded), so treat it as a Tailscale-side liveness artefact, not a hypervisor outage. `homeassistant` still advertises `ExitNodeOption: true` but `ExitNode: false` — it **offers** exit-node capability; it is not currently serving as one (the old "active; offers exit node" wording overstated the live state). Container states cross-checked again against live `pct list` on both hypervisors, and each peer's container identity confirmed by running `tailscale ip -4` **inside** the candidate LXC on both hosts — the authoritative mapping, since peer names and LXC names do not always match. | Node | IP | State | |---|---|---| | hermes | 100.118.5.51 | **self** | -| agentzero | 100.106.54.94 | online | -| anthonys-imac | 100.112.123.124 | idle/offline 27d | +| agentzero | 100.106.54.94 | online — CT475 (pve) | +| anthonys-imac | 100.112.123.124 | idle/offline 31d | | anthonys-ipad | 100.111.198.120 | online | | anthonys-iphone | 100.100.116.67 | online | | anthonys-mac-mini | 100.74.17.15 | online | -| cachyos | 100.124.208.15 | idle/offline 47d | -| clawtest | 100.122.189.81 | online | -| cliproxyapi | 100.83.112.94 | online | -| cloudreve | 100.111.187.7 | idle/offline 88d | -| conduit | 100.81.79.87 | idle/offline 44d | -| docker | 100.96.150.69 | online | -| docker-01 | 100.121.12.31 | online | -| elementsynapse | 100.75.250.37 | idle/offline 91d | -| freellmapi | 100.127.208.75 | online | -| freshrss | 100.83.60.93 | online | -| freshrss-new | 100.110.180.115 | idle/offline 64d | -| gitea | 100.82.100.128 | online | +| cachyos | 100.124.208.15 | idle/offline 51d | +| clawtest | 100.122.189.81 | online — CT333 (pve) | +| cliproxyapi | 100.83.112.94 | online — CT103 (pve) | +| cloudreve | 100.111.187.7 | idle/offline 92d — CT209 stopped | +| conduit | 100.81.79.87 | idle/offline 48d | +| docker | 100.96.150.69 | online — CT200 (pve) | +| docker-01 | 100.121.12.31 | online — CT1001 (m93p) | +| elementsynapse | 100.75.250.37 | idle/offline 95d — CT555 stopped | +| freellmapi | 100.127.208.75 | online — CT1006 (m93p) | +| freshrss | 100.83.60.93 | online — CT1260 (m93p) | +| freshrss-new | 100.110.180.115 | idle/offline 68d | +| gitea | 100.82.100.128 | online — CT221 (m93p) | | guest-vps | 100.117.14.84 | online | -| hermesagent | 100.98.205.112 | online | -| homeassistant | 100.68.139.5 | active; offers exit node | -| litellm | 100.79.29.64 | online | -| m93p | 100.104.51.98 | online | -| mailflow | 100.115.60.92 | online | -| mattermost | 100.98.116.14 | idle/offline 31d — CT255 stopped (re-verified live 2026-10-21) | -| n8n | 100.84.124.30 | online | -| nextcloud | 100.90.102.19 | online | -| ntfy | 100.67.153.116 | active | +| hermesagent | 100.98.205.112 | online — CT450 (pve) | +| homeassistant | 100.68.139.5 | online | +| litellm | 100.79.29.64 | online — CT500 (m93p) | +| m93p | 100.104.51.98 | idle/offline 13m ago | +| mailflow | 100.115.60.92 | online — CT1262 (m93p) | +| mattermost | 100.98.116.14 | idle/offline 35d — CT255 stopped | +| n8n | 100.84.124.30 | online — CT215 (pve) | +| nextcloud | 100.90.102.19 | online — CT270 (pve) | +| ntfy | 100.67.153.116 | online — CT1241 (m93p) | | octop | 100.92.163.122 | online | -| ollama | 100.108.44.119 | online | +| ollama | 100.108.44.119 | online — CT205 (pve) | | omarchy | 100.73.227.103 | online | -| omarchybook | 100.107.9.100 | online | -| omarchymac | 100.84.180.69 | idle/offline 3d | -| omni | 100.93.204.4 | idle/offline 64d — CT601 stopped (re-verified live 2026-10-21) | -| omniroute | 100.88.81.19 | online — CT600 (live OmniRoute; re-verified 2026-10-21) | -| omniroute-1 | 100.78.63.20 | active — CT101 on m93p (re-verified 2026-10-21) | -| openmausbot | 100.91.214.91 | online | +| omarchybook | 100.107.9.100 | idle/offline 3d | +| omarchymac | 100.84.180.69 | idle/offline 7d | +| omni | 100.93.204.4 | idle/offline 68d — CT601 stopped | +| omniroute | 100.88.81.19 | online — CT600 (pve), live OmniRoute | +| omniroute-1 | 100.78.63.20 | online — CT101 (m93p) | +| openmausbot | 100.91.214.91 | idle/offline 3d | | openmausbot-vm | 100.77.107.30 | online | -| openweb | 100.69.230.13 | online | -| paseo | 100.72.188.93 | online | +| openweb | 100.69.230.13 | online — CT245 (m93p) | +| paseo | 100.72.188.93 | online — CT1261 (m93p) | | pve | 100.96.100.82 | online | -| qwenpaw | 100.110.72.126 | online | -| rclone | 100.107.116.17 | online | -| runtipi | 100.96.244.39 | online | -| rustdesk | 100.95.227.57 | online | -| sftpgo | 100.88.223.70 | active — CT299 (re-verified live 2026-10-21) | -| social-dashboard | 100.70.183.37 | online | +| qwenpaw | 100.110.72.126 | online — CT465 (pve) | +| rclone | 100.107.116.17 | online — CT104 (m93p) | +| runtipi | 100.96.244.39 | online — CT201 (pve) | +| rustdesk | 100.95.227.57 | online — CT1008 (m93p) | +| sftpgo | 100.88.223.70 | online — CT299 (pve) | +| social-dashboard | 100.70.183.37 | online — CT1263 (m93p) | | springroll | 100.100.153.125 | online | -| ubuntu-server-xfce | 100.101.26.104 | idle/offline 60d | -| vaultwarden | 100.123.225.90 | online | -| webserver | 100.82.40.23 | online | +| springroll-browser | 100.109.221.91 | online | +| ubuntu-server-xfce | 100.101.26.104 | idle/offline 64d | +| vaultwarden | 100.123.225.90 | online — CT102 (m93p) | +| webserver | 100.82.40.23 | online — CT207 (pve) | > Note: `tailscale status` also lists 23 `funnel-ingress-node` peers with IPv6-only addresses — these are Tailscale's Funnel infrastructure, not homelab hosts, and are deliberately excluded above. > @@ -100,7 +102,7 @@ Re-verified 2026-10-21 03:0x: the 2026-10-19 table had drifted again — **`octo | `/agent-estate` | `http://127.0.0.1:8769` | Role dashboard — target is the bare host root, **not** `/agent-estate-role-dashboard.html` (corrected 2026-10-11) | | `/evening-grid.html` | `http://127.0.0.1:9099/evening-grid.html` | Evening grid | -Verified against `tailscale serve status` on 2026-10-11. +Verified against `tailscale serve status` on 2026-10-25 — the CT460 route table above matched live exactly (12 paths, no drift). ## CT460 Funnel and 9443 Routes | Port | Target | Notes | @@ -109,11 +111,20 @@ Verified against `tailscale serve status` on 2026-10-11. | `:9443` (tailnet only) `/` | `http://127.0.0.1:5173` | Vite dev server on port 5173 exposed via a **tailnet-only** Serve on port 9443 — was missing from this page, added 2026-10-11 | ## CT201 Serve Routes -| Path | Target | Notes | -|---|---|---| -| `:8443` | `http://localhost:8082` | Homepage dashboard | -| `/steel` | `http://127.0.0.1:5173` | Steel Browser UI | -| `/steel-api` | `http://127.0.0.1:3000` | Steel Browser API (path prefix not stripped — use direct IP for API calls) | +Verified live on 2026-10-25 via `pct exec 201 -- tailscale serve status` on `pve` (100.96.100.82). The previous version of this table was wrong in two ways and has been corrected. + +| Host / Port | Path | Target | Notes | +|---|---|---|---| +| `runtipi.kangaroo-eel.ts.net:8443` (tailnet only) | `/` | `http://127.0.0.1:8085` | Homepage asset proxy front door — **currently 502** (upstream 8082 has no listener) | +| `runtipi.kangaroo-eel.ts.net:8443` (tailnet only) | `/mgr` | `http://127.0.0.1:8084` | `homepage-manager` container — **200** | +| `runtipi.kangaroo-eel.ts.net:443` (tailnet only) | `/` | `http://127.0.0.1:8085` | Same asset proxy — **currently 502** | +| `runtipi.kangaroo-eel.ts.net:443` (tailnet only) | `/mgr` | `http://127.0.0.1:8084` | `homepage-manager` — **200** | +| `runtipi.kangaroo-eel.ts.net:443` (tailnet only) | `/steel` | `http://127.0.0.1:5173` | Steel Browser UI — **200** on :443. ⚠ **`/steel` is NOT served on :8443** — it 502s there | +| `runtipi.kangaroo-eel.ts.net:443` (tailnet only) | `/steel-api` | `http://127.0.0.1:3000` | Steel Browser API (path prefix not stripped — use direct IP for API calls) | + +Two corrections to the pre-2026-10-25 table: +1. **`:8443` is served by `tailscaled` on CT201, but so is `:443`.** `ss -ltnp` on CT201 shows `tailscaled` bound to `100.96.244.39:443`, and the serve table above lists routes on **both** ports. The old note claiming "Port 443 occupied by Traefik on CT201" is **false as of 2026-10-25** — no Traefik container or process exists on CT201 (`docker ps -a` and `ps aux` both came back empty for `traefik`), and Tailscale owns 443 there. The Homebox/steel path prefix is not stripped on `/steel-api`. +2. The old table routed `:8443` straight to `http://localhost:8082`. That port has **no listener**; the live target is `8085` (the `asset_proxy.py` front door), which itself proxies to the dead 8082 and returns 502. → [[systems/homepage-dashboard]] ## Atomic Restore Script `/home/hermes/.hermes/scripts/tailscale-serve-apply.sh` — Rebuilds the complete CT460 route table, including tailnet Serve on `:443` and public Funnel on `:8443`. @@ -137,9 +148,9 @@ tailscale serve --set-path /jobs off ``` ## Notes -- Port 443 occupied by Traefik on CT201 — Tailscale uses port 8443 there -- CT460 has no conflict — Tailscale uses 443 directly -- Routes must be re-added in order (restore script handles this) +- **CT201 now serves Tailscale on BOTH `:443` and `:8443`** (verified 2026-10-25). The old "Port 443 occupied by Traefik on CT201 — Tailscale uses port 8443 there" claim was **wrong**: no Traefik container or process exists on CT201, and `tailscaled` owns 443 there (`ss -ltnp` shows it bound to `100.96.244.39:443`). The CT201 Serve Routes table above now records both ports. +- CT460 has no conflict — Tailscale uses 443 directly, with the public webhook Funnel on `:8443`. +- Routes must be re-added in order (restore script handles this). - After every rebuild, verify that `tailscale serve status` contains both the `:443` Serve routes and the `:8443/webhook` Funnel route. ## Related diff --git a/log.md b/log.md index d121866..c9a4348 100644 --- a/log.md +++ b/log.md @@ -1199,3 +1199,68 @@ No secrets written; host names, IPs, VMIDs, job/incident IDs, ports and probe st `+08:00` offset and SQLite's `date()` normalises to UTC, so `date(started_at)` moves 00:00–07:59 AWST rows onto the previous day. Bucket days with `substr(started_at,1,10)`. - **No secrets written.** Job IDs, incident IDs, table names, counts, paths and timestamps only. + +## [2026-10-25] stocktake | wiki-maintain.sh + drift correction (tailscale, homepage-dashboard, 2 stale pages) +- **Script ran clean.** `wiki-maintain.sh` completed all three stages at 03:02–03:03 AWST: + `systems/skills-index.md` regenerated (302 skills / 69 categories, 45 archived — the count fell + from 306 because four skills moved to `~/.hermes/skills/.archive/`: `courier-tracking-monitor`, + `pve-vm-console-recovery`, `model-provider-comparison-research`, `live-application-verification` — + all four confirmed present in the archive directory), freshness audit written to + `raw/stocktake/freshness-20261025.txt`, Quartz rebuilt (630 files) and deployed to `public/`, + `hermes-wiki-serve.service` restarted. Verified the served pages return **200** afterwards. +- **Freshness audit at run time:** 2 stale / 99 fresh / 4 no-date of 105 pages. The two stale pages + were both re-probed live and corrected (see below); after correction the audit reports + **0 stale**. +- **`infrastructure/tailscale.md` — node table rebuilt from live `tailscale status --json`.** The + 2026-10-21 table had drifted again: + - **`springroll-browser` (100.109.221.91) was missing from the table entirely** — added (online). + - **`omarchybook` (100.107.9.100) and `openmausbot` (100.91.214.91) have both gone offline** + (online → idle/offline 3d). `openmausbot`'s m93p LXC (CT1264) is still running but no longer + has the `tailscale` binary on PATH, so the node itself has stopped connecting. + - **Every offline age was stale** and was refreshed: `mattermost` 31d → **35d**, `omni` 64d → **68d**, + `elementsynapse` 91d → **95d**, `ubuntu-server-xfce` 60d → **64d**, `cloudreve` 88d → **92d**, + `anthonys-imac` 27d → **31d**, `cachyos` 47d → **51d**, `conduit` 44d → **48d**, + `freshrss-new` 64d → **68d**, `omarchymac` 3d → **7d**. + - `homeassistant` still advertises `ExitNodeOption: true` but `ExitNode: false` — it offers + exit-node capability but is not currently serving as one; the old "active; offers exit node" + wording overstated the live state and was corrected. + - `m93p` (100.104.51.98) reads **idle/offline 13m ago** in the peer table, but the host is plainly + reachable (both `pct list` probes and the SSH session succeeded during this audit), so it is + recorded as a Tailscale-side liveness artefact, not a hypervisor outage. + - Container identities confirmed the authoritative way this run: `tailscale ip -4` executed **inside** + each candidate LXC on both `pve` (100.96.100.82) and `m93p` (100.104.51.98), because peer names + and LXC names do not always match. CT209 (cloudreve), CT255 (mattermost), CT555 (elementsynapse) + and CT601 (omni) confirmed **stopped**; CT600 (omniroute, live OmniRoute) and CT101 (m93p) + confirmed **running**. + - Funnel peer count re-checked: still **23** `funnel-ingress-node` peers with IPv6-only addresses + (excluded). Total non-funnel nodes 51 → **52** (51 IPv4 peers + `hermes` itself). +- **`infrastructure/tailscale.md` + `systems/homepage-dashboard.md` — the CT201 route tables were wrong.** + Live `pct exec 201 -- tailscale serve status` shows CT201 serving Tailscale on **both `:443` and + `:8443`**, and the old "Port 443 occupied by Traefik on CT201 — Tailscale uses port 8443 instead" + note was **false**: no Traefik container or process exists on CT201 (`docker ps -a` and `ps aux` both + come back empty for `traefik`), and `ss -ltnp` shows `tailscaled` bound to `100.96.244.39:443`. + Corrected routes: `/` → 8085 and `/mgr` → 8084 on **both** ports; `/steel` → 5173 and + `/steel-api` → 3000 on **`:443` only** (`/steel` on `:8443` returns **502**; on `:443` it returns + **200**). The old table also routed `:8443` straight to `http://localhost:8082`, which has **no + listener** — the live target is 8085 (`asset_proxy.py`), which itself proxies to the dead 8082 and + returns 502. Both pages corrected. The **CT460** route table was checked and matched live exactly + (12 paths, no drift). +- **`reports/communities-wa-social-media-audit-2026.md` (was 58d stale) — re-verified, not drifted.** + Checked against the live Department of Communities pages: the remit wording, the ten portfolios, + the **1 July 2025** Housing → Department of Housing and Works restructure, the five-minister + structure and the WA Seniors Card carve-out all still hold; the Department site was updated + 23 October 2026 and its recent announcements (carers, youth grants, forced adoption) match the + content pillars recorded here. Audience metrics were **not** re-counted and are left as the + 2026-08-28 point-in-time figures; `review_after: 2026-11-26` stands. +- **`incidents/2026-08-26-work-outlook-basic-auth-disabled.md` (was 22d stale) — re-probed, still open.** + `himalaya envelope list -a work -s 1` reproduces the identical failure (`cannot build IMAP client` + / `login not supported`). The tenant still advertises only `XOAuth2` and the account still + authenticates by password, so no remediation has landed. Status stays `open`; `updated` and + `verified_on` bumped to the verification date with the probe output recorded on the page. +- **`systems/scheduled-tasks.md` checked and left unchanged.** Live `~/.hermes/cron/jobs.json` reads + 28 jobs — 25 enabled / 3 disabled, matching the page. All 28 job IDs are present on the page. + Non-clean `last_status` is still **4** (`0e753e9720fd` error, `fad5a86979d4` delivery_failed, + `066bb5191280` delivery_failed, `c0a9fa314542` error streak 1) and unclosed incident rows are + still **2** (`0e753e_e7f8194a7d06`, `c0a9fa_764558b5ae83`) — identical to the page's 2026-10-25 + entry. No drift, nothing to change. +- **No secrets written.** Job IDs, incident IDs, IPs, counts, paths and timestamps only. diff --git a/raw/stocktake/freshness-20261025.txt b/raw/stocktake/freshness-20261025.txt new file mode 100644 index 0000000..4cfeacb --- /dev/null +++ b/raw/stocktake/freshness-20261025.txt @@ -0,0 +1,118 @@ +# Wiki freshness audit — 2026-10-25 +Threshold: >21 days since `updated` + +## STALE (0) + + +## FRESH (101) + +- [ 5d] CONTRIBUTING.md +- [ 21d] agents/hermes-chaos.md +- [ 21d] agents/hermes-production.md +- [ 5d] agents/index.md +- [ 14d] agents/nanobot.md +- [ 5d] agents/open-claw.md +- [ 14d] agents/qwenpaw.md +- [ 5d] agents/zeroclaw.md +- [ 5d] comparisons/camoufox-vs-chrome.md +- [ 5d] comparisons/hermes-vs-nanobot.md +- [ 5d] comparisons/memory-backends.md +- [ 5d] comparisons/model-routers.md +- [ 12d] comparisons/steel-vs-camoufox.md +- [ 5d] concepts/agent-memory.md +- [ 12d] concepts/browser-automation.md +- [ 5d] concepts/model-routing.md +- [ 5d] concepts/persistent-shells.md +- [ 5d] concepts/tool-calling.md +- [ 0d] current-state.md +- [ 5d] decisions/index.md +- [ 5d] decisions/keep-openrouter-as-fallback.md +- [ 5d] decisions/persistent-shell-enabled.md +- [ 5d] decisions/rollback-steel-to-camofox.md +- [ 5d] experiments/index.md +- [ 1d] incidents/2026-07-29-mnemosyne-relay.md +- [ 5d] incidents/2026-08-01-mnemosyne-capture-failure.md +- [ 1d] incidents/2026-08-04-omniroute-free-deepseek-silent-stops.md +- [ 3d] incidents/2026-08-08-gitea-config-backup-push-dead.md +- [ 2d] incidents/2026-08-15-skills-index-drift.md +- [ 13d] incidents/2026-08-18-mnemosyne-capture-pipeline.md +- [ 0d] incidents/2026-08-26-work-outlook-basic-auth-disabled.md +- [ 5d] incidents/2026-08-29-gmail-read-state.md +- [ 4d] incidents/2026-09-02-sftpgo-outage.md +- [ 14d] incidents/2026-09-28-hermes-managed-runtime-deps.md +- [ 19d] incidents/2026-10-01-cliproxy-connection-auth-expired.md +- [ 21d] incidents/2026-10-03-ct450-hermes-update.md +- [ 21d] incidents/2026-10-03-mnemosyne-vector-recall-fts-only.md +- [ 19d] incidents/2026-10-05-dead-model-pin-repin.md +- [ 1d] incidents/2026-10-09-cron-provider-timeout-storm.md +- [ 16d] incidents/2026-10-09-memory-recall-relevance.md +- [ 9d] incidents/2026-10-14-omniroute-node-connection-refused-storm.md +- [ 3d] incidents/2026-10-16-omniroute-503-resource-pressure.md +- [ 6d] incidents/2026-10-18-degenerate-stream-canned-substitute.md +- [ 4d] incidents/2026-10-20-gateway-unclean-exit-orphaned-run.md +- [ 3d] incidents/2026-10-21-omniroute-pre-dispatch-filter-skip.md +- [ 0d] incidents/2026-10-22-conduit-memory-start-timeout.md +- [ 0d] incidents/2026-10-24-conduit-call-request-refused.md +- [ 3d] infrastructure/backups.md +- [ 5d] infrastructure/credentials-map.md +- [ 14d] infrastructure/docker-services.md +- [ 5d] infrastructure/domains-and-tunnels.md +- [ 21d] infrastructure/hosts.md +- [ 11d] infrastructure/network-map.md +- [ 11d] infrastructure/proxmox.md +- [ 0d] infrastructure/tailscale.md +- [ 13d] queries/retained-research-answers.md +- [ 0d] reports/communities-wa-social-media-audit-2026.md +- [ 4d] reports/uber-eats/2026-07.md +- [ 4d] reports/uber-eats/2026-08.md +- [ 4d] reports/uber-eats/2026-09.md +- [ 4d] reports/uber-eats/index.md +- [ 5d] runbooks/backup-wiki.md +- [ 5d] runbooks/diagnose-docker.md +- [ 5d] runbooks/gateway-resource-resilience.md +- [ 12d] runbooks/job-radar.md +- [ 5d] runbooks/multiplexer-setup.md +- [ 21d] runbooks/provider-health.md +- [ 5d] runbooks/recover-docker-service.md +- [ 5d] runbooks/restart-browser.md +- [ 5d] runbooks/restart-hermes.md +- [ 5d] runbooks/restore-openrouter.md +- [ 5d] runbooks/test-openrouter.md +- [ 5d] runbooks/troubleshoot-tool-loop.md +- [ 21d] runbooks/update-hermes-safely.md +- [ 12d] systems/browser-backend.md +- [ 5d] systems/cloudflare-tunnel.md +- [ 0d] systems/conduit.md +- [ 4d] systems/current-profile.md +- [ 5d] systems/guanaco.md +- [ 5d] systems/headless-server.md +- [ 3d] systems/hermes-agent.md +- [ 5d] systems/hermes-ui.md +- [ 13d] systems/home-assistant.md +- [ 0d] systems/homepage-dashboard.md +- [ 14d] systems/ignis.md +- [ 21d] systems/memory-backend.md +- [ 6d] systems/messaging-integrations.md +- [ 1d] systems/mnemosyne.md +- [ 2d] systems/model-providers.md +- [ 13d] systems/nanobot.md +- [ 5d] systems/nextcloud.md +- [ 5d] systems/obsidian.md +- [ 3d] systems/omniroute.md +- [ 5d] systems/opencode-go.md +- [ 5d] systems/openrouter.md +- [ 14d] systems/paseo.md +- [ 6d] systems/push-notifications.md +- [ 0d] systems/scheduled-tasks.md +- [ 0d] systems/skills-index.md +- [ 5d] systems/terminal-backend.md +- [ 5d] systems/tool-search.md + +## NO updated DATE (4) + +- SCHEMA.md +- experiments/active/example.md +- index.md +- log.md + +TOTAL: 0 stale, 101 fresh, 4 no-date of 105 pages \ No newline at end of file diff --git a/reports/communities-wa-social-media-audit-2026.md b/reports/communities-wa-social-media-audit-2026.md index a422494..7d57539 100644 --- a/reports/communities-wa-social-media-audit-2026.md +++ b/reports/communities-wa-social-media-audit-2026.md @@ -3,7 +3,8 @@ title: Department of Communities WA Social Media Audit and First-Day Brief type: report status: active created: 2026-08-28 -updated: 2026-08-28 +updated: 2026-10-25 +verified_on: 2026-10-25 review_after: 2026-11-26 confidence: medium tags: [content, research, department-of-communities, social-media] @@ -16,6 +17,26 @@ sources: [/home/hermes/.hermes/cache/documents/doc_3cc87da4957f_deep-research-re Anthony Martin commenced as Social Media Officer managing communications for the Western Australian Department of Communities in August 2026. This page records the durable strategic findings from the public-source audit supplied on 2026-08-28. It is a public baseline, not a substitute for native platform analytics. +**Re-verified 2026-10-25 (stocktake).** The organisational facts below were checked against the +live Department of Communities pages and still hold — the remit, the ten portfolios, the July 2025 +housing transfer and the five-minister structure are unchanged. Specifically confirmed live: +- The Department's remit still reads *"keep children safe; provide vital community services, + including in emergencies; address homelessness; prevent family and domestic violence; provide + stewardship for the disability sector; regulate the early childhood and care sector; and manage + the agenda for women's interests, youth, seniors and ageing, carers and volunteering"* — + matching the portfolio list recorded here. +- **Housing → Department of Housing and Works** is confirmed as a **1 July 2025** restructure + (the announcement page is dated 18 July 2025), so the legacy-Housing-correction advice stands. +- Five Ministers are listed, matching the "five Ministers / ten key human service portfolios" + structure. +- The Department site was itself updated **23 October 2026**, and recent announcements + (carers, youth grants, forced adoption) confirm the active content pillars are live topics. + +**Not re-verified:** the audience metrics (follower counts) and platform-algorithm claims are +point-in-time public-source figures from the 2026-08-28 audit and remain as recorded; they were +not re-counted. The `review_after` date of 2026-11-26 stands for a full refresh against native +analytics. + ## Strategic baseline - The Department's current remit spans child protection, community services, homelessness, prevention of family and domestic violence, disability services, early childhood education and care regulation, women's interests, youth, seniors and ageing, carers, and volunteering. diff --git a/systems/homepage-dashboard.md b/systems/homepage-dashboard.md index 1bda802..687d50f 100644 --- a/systems/homepage-dashboard.md +++ b/systems/homepage-dashboard.md @@ -3,8 +3,8 @@ title: Homepage Dashboard type: systems status: degraded created: 2026-07-26 -updated: 2026-10-20 -verified_on: 2026-10-20 +updated: 2026-10-25 +verified_on: 2026-10-25 confidence: high tags: [dashboard, homepage, homelab, proxmox, monitoring] --- @@ -40,7 +40,8 @@ CT201 (runtipi) ├── homebox container (7745) — up ├── asset_proxy.py (python3, port 8085) — proxies 8085 → 8082, currently 502 ├── manager.py (python3) — dashboard management service, up -└── Tailscale serve (port 8443) — / → 8085, /mgr → 8084, /steel → 5173, /steel-api → 3000 +└── Tailscale serve (ports 443 AND 8443) — / → 8085, /mgr → 8084 on both; + /steel → 5173 and /steel-api → 3000 on :443 ONLY ``` No container is listening on **8082** — `docker ps` on CT201 lists no `homepage` container at all. @@ -115,7 +116,10 @@ Type anywhere on the dashboard to search services by name/description. Google se - Custom CSS in `custom.css` ## Tailscale Serve -Port 443 occupied by Traefik on CT201 — Tailscale uses port 8443 instead. +**CT201 serves Tailscale on BOTH `:443` and `:8443`** (verified live 2026-10-25 via `pct exec 201 -- tailscale serve status`). +The earlier note on this page — "Port 443 occupied by Traefik on CT201 — Tailscale uses port 8443 instead" — was **wrong**: +no Traefik container or process exists on CT201 (`docker ps -a` and `ps aux` both return nothing for `traefik`), and +`ss -ltnp` shows `tailscaled` bound to `100.96.244.39:443`. Corrected on 2026-10-25. ## Maintenance - **Restart Manager:** `docker restart homepage-manager` @@ -124,9 +128,15 @@ Port 443 occupied by Traefik on CT201 — Tailscale uses port 8443 instead. (not in Docker) — restart via whatever supervises them; check `ps aux | grep -E 'manager.py|asset_proxy'` - **Recover the upstream Homepage (8082):** the image `ghcr.io/gethomepage/homepage` is still present on CT201 (4 months old) but no container uses it — recreate it to restore 8082 and the 8085 proxy path -- **Tailscale serve on CT201:** `/` → 8085, `/mgr` → 8084, `/steel` → 5173, `/steel-api` → 3000 +- **Tailscale serve on CT201:** `/` → 8085 and `/mgr` → 8084 on **both** `:443` and `:8443`; + `/steel` → 5173 and `/steel-api` → 3000 on **`:443` only** (`/steel` on `:8443` returns 502) ## Recent Changes +- **2026-10-25 (live probe, stocktake):** the "Port 443 occupied by Traefik on CT201" note was **false** — no Traefik + container or process exists on CT201, and `tailscaled` owns **both** `:443` and `:8443` there. Serve tables corrected: + `/` → 8085 and `/mgr` → 8084 on both ports, but `/steel` → 5173 and `/steel-api` → 3000 on **`:443` only** (`/steel` + on `:8443` returns **502**; on `:443` it returns **200**). Re-confirmed live: 8084 → **200**, 8085 → **502**, + 8082 → **no listener**, `homepage-manager` up. → [[infrastructure/tailscale]] - **2026-10-20 (live probe):** `homepage` container absent, 8082 dead, 8085 → 502, Homarr on 8102 → 200. Status changed `active` → `degraded`. VM/LXC table re-read from both PVE hosts; corrected IDs and host assignments, dropped the non-existent OpenClaw VM 403, marked Mattermost CT255 stopped. diff --git a/systems/skills-index.md b/systems/skills-index.md index 407d993..040ba51 100644 --- a/systems/skills-index.md +++ b/systems/skills-index.md @@ -3,8 +3,8 @@ title: Installed Skills type: system status: active created: 2026-07-22 -updated: 2026-10-24 -verified_on: 2026-10-24 +updated: 2026-10-25 +verified_on: 2026-10-25 confidence: high tags: [skills, hermes] sources: [] @@ -12,9 +12,9 @@ sources: [] # Installed Skills -**Total installed: 306 skills** in `~/.hermes/skills/`. +**Total installed: 302 skills** in `~/.hermes/skills/`. -- **41 archived skills** are parked under `~/.hermes/skills/.archive/` and are excluded from this count — the loader does not expose them. +- **45 archived skills** are parked under `~/.hermes/skills/.archive/` and are excluded from this count — the loader does not expose them. - The loader's own catalogue (`hermes skills list`, e.g. *34 hub-installed, 52 builtin, N local — N enabled*) is the authoritative loadable figure; this page is a filesystem inventory. This page is auto-regenerated from the live skill inventory. Do not hand-edit. @@ -102,7 +102,7 @@ This page is auto-regenerated from the live skill inventory. Do not hand-edit. - `ddia-systems` — # Designing Data-Intensive Applications Framework -## Devops (110) +## Devops (108) - `abyss-ios-pairing` — # Pair iPhone with The Abyss (iOS) - `agent-extension-audit` — # Agent Extension Audit @@ -117,7 +117,6 @@ This page is auto-regenerated from the live skill inventory. Do not hand-edit. - `chat4000-ops` — # chat4000 Operations & Pairing - `cloudflare-ops` — # Cloudflare Operations - `codex-via-cliproxy` — # Codex CLI via Cliproxy (mitmproxy redirect) -- `courier-tracking-monitor` — # Courier / Shipment Tracking Monitor - `crawlee-batch-scrape` — ## Installation - `cron-job-maintenance` — ## Mnemosyne Watchdog Cron Job — Conflict Alert Thresholds (2026-07-25) - `cross-profile-session-handoff` — # Cross-Profile Session Handoff @@ -193,7 +192,6 @@ This page is auto-regenerated from the live skill inventory. Do not hand-edit. - `omniroute-skill-execution` — # Execute Skills on OmniRoute MCP - `openclaw-ops` — # Open-Claw Operations & Configuration - `pve-ops` — # PVE Operations -- `pve-vm-console-recovery` — # PVE VM Console Recovery (headless keystroke injection) - `radar-jobs-dashboard` — # RADAR Jobs Dashboard - `readlater-ops` — # ReadLater Operations - `runtipi-container-management` — # Runtipi Container Management @@ -433,7 +431,7 @@ This page is auto-regenerated from the live skill inventory. Do not hand-edit. - `refactoring-ui` — # Refactoring UI Design System -## Research (15) +## Research (14) - `arxiv` — # arXiv Research - `blogwatcher` — # Blogwatcher @@ -442,7 +440,6 @@ This page is auto-regenerated from the live skill inventory. Do not hand-edit. - `grounded-citations` — # Grounded Citations - `llm-wiki` — # Karpathy's LLM Wiki - `local-dining-scene-monitor` — # Local Dining Scene Monitor -- `model-provider-comparison-research` — # Model-versus-provider comparison research - `operations-wiki` — # Operations Wiki - `polymarket` — # Polymarket — Prediction Market Data - `research-paper-writing` — # Research Paper Writing Pipeline @@ -469,7 +466,7 @@ This page is auto-regenerated from the live skill inventory. Do not hand-edit. - `software-design-philosophy` — # A Philosophy of Software Design Framework -## Software Development (19) +## Software Development (18) - `code-wiki` — # Code Wiki Skill - `codebase-inspection` — # Codebase Inspection with pygount @@ -478,7 +475,6 @@ This page is auto-regenerated from the live skill inventory. Do not hand-edit. - `github` — # GitHub - `hermes-agent-skill-authoring` — # Authoring Hermes-Agent Skills (in-repo) - `inspecting-hermes-desktop-dom` — # Inspecting the live Hermes desktop DOM -- `live-application-verification` — # Live Application Verification - `node-inspect-debugger` — # Node.js Inspect Debugger - `plan` — # Plan Mode - `python-debugpy` — # Python Debugger (pdb + debugpy)