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
This commit is contained in:
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user