🦉 wiki stocktake 2026-10-21: tailscale node table rebuilt, 2 missing Uber Eats reports recovered

Maintenance script ran clean (skills-index 346 -> 347, freshness audit, Quartz rebuilt
596 files and deployed, hermes-wiki-serve.service restarted).

infrastructure/tailscale.md — node table rebuilt from live `tailscale status --json`.
  The 2026-10-19 table had drifted: octop (100.92.163.122) and springroll
  (100.100.153.125) missing entirely, openmausbot / openmausbot-vm present in prose
  but absent from the table body, omarchymac now offline, all offline ages stale.
  Rebuilt keyed on DNS name rather than the JSON HostName — HostName is `ct260` for
  the freshrss node and BOTH OmniRoute nodes report the hostname `omniroute`, which
  collides silently. Now 51 non-funnel nodes. Container states cross-checked against
  live `pct list` on pve and m93p: CT255 stopped, CT601 stopped, CT299 running.

reports/uber-eats/ — 2026-08 and 2026-09 recovered. The generator wrote only to
  ~/wiki/reports/uber-eats/ and never to the canonical tree, so both months were
  missing from the published wiki. Root cause fixed in
  ~/.hermes/cron/scripts/generate-uber-eats-report.py: it now targets
  ~/workspace/agent-estate-wiki/reports/uber-eats/ and mirrors to the legacy tree,
  and now emits YAML frontmatter (without it the pages landed in the audit's
  "no updated DATE" bucket and Quartz could not read the page date). 2026-08
  previous-month column corrected from $0.00 to $264.51 / 11 orders.

incidents/2026-08-15-skills-index-drift.md — re-verified live; the named
  regenerate-skills-index.sh no longer exists on disk (regeneration now lives in
  wiki-maintain.sh step 1/3). Incident prevention confirmed working: 347 skills.
incidents/2026-09-02-sftpgo-outage.md — re-verified live: CT299 running, health
  endpoint HTTP 401 (auth required, service up), no recurrence.

reports/communities-wa-social-media-audit-2026.md — left stale (54d). Its source
  document no longer exists on disk, so the baseline cannot be re-verified against
  a live source. Flagged, not edited.

Freshness after this run: 1 stale, 94 fresh, 6 no-date of 101 pages.
This commit is contained in:
Tony0410
2026-10-21 03:14:26 +08:00
parent b662254569
commit c1d3b59260
13 changed files with 537 additions and 32 deletions
+12 -2
View File
@@ -3,8 +3,9 @@ title: "Skills Index Drift — 4x Undercount"
type: incident
status: resolved
created: 2026-08-15
updated: 2026-08-15
updated: 2026-10-21
resolved_on: 2026-08-15
verified_on: 2026-10-21
confidence: high
tags: [skills, wiki, drift, auto-regeneration]
sources: [session-investigation, agent-estate-wiki]
@@ -25,7 +26,9 @@ Static documentation for a mutable inventory. The skills tree at `~/.hermes/skil
## Resolution
1. Regenerated `systems/skills-index.md` from the live skill tree (all 330 skills, 26 categories)
2. Created `regenerate-skills-index.sh` script for automated regeneration
2. Created a regeneration script for automated regeneration — **superseded on 2026-10-21:** the
regeneration now lives inside `wiki-maintain.sh` (step 1/3) in the wiki repo; no standalone
`regenerate-skills-index.sh` exists on disk any more.
3. Set up cron job `1a8e90ea2271` to run daily at 03:00 AWST
4. Script auto-commits and pushes to Gitea (`Anthony/agent-estate-wiki`)
5. Quartz site at `http://100.118.5.51:9120/systems/skills-index` rebuilt and redeployed
@@ -33,6 +36,13 @@ Static documentation for a mutable inventory. The skills tree at `~/.hermes/skil
## Lesson
Static wiki pages that reflect **mutable inventory** (skills, services, cron jobs) **MUST be auto-regenerated on a schedule**, not hand-maintained. The moment the estate grows, a hand-written page becomes stale.
## Re-verified 2026-10-21
The prevention mechanism is live and working. `wiki-maintain.sh` step 1/3 regenerated
`systems/skills-index.md` from `~/.hermes/skills/` on the 2026-10-21 03:00 scheduled run:
**347 skills across 70 categories** (the "26 categories" figure in the original write-up was
the count at the time of the incident, not the current topology — the skill tree has since
nested deeper). The daily cron job `1a8e90ea2271` is `active` with `last_status: ok`.
## Prevention
- Daily cron job regenerates skills-index.md from live tree
- Page includes "auto-regenerated, do not hand-edit" warning
+8 -2
View File
@@ -3,8 +3,8 @@ title: SFTPGo Outage — CT299 Offline (2026-09-02)
type: incident
status: resolved
created: 2026-09-04
updated: 2026-09-04
verified_on: 2026-09-04
updated: 2026-10-21
verified_on: 2026-10-21
confidence: high
tags: [incident, sftpgo, ct299, tailscale, proxmox]
sources: [session:20260902_014540_c193be]
@@ -62,6 +62,12 @@ tailscale ping sftpgo
curl -sS http://100.88.223.70:10080/healthz
```
## Re-verified 2026-10-21
Live state checked: **CT299 `sftpgo` is `running`** on `pve` (100.96.100.82) per `pct list`;
the node is `active` in `tailscale status` at `100.88.223.70`; the SFTPGo health endpoint
`http://100.88.223.70:10080/healthz` returns **HTTP 401** (expected — auth required, service up).
The 2026-09-02 outage remains resolved; no recurrence.
## Lessons Learned
1. **Clean up `lxc-attach` probes** — always exit cleanly and verify no lingering processes after diagnostic sessions