audit(2026-10-19): degenerate-stream incident page + push-notifications page; refresh scheduled-tasks, current-state, index, log, messaging, mnemosyne, tailscale, proxmox

This commit is contained in:
Tony0410
2026-10-19 00:21:26 +08:00
parent dd53e5fbe1
commit 0ed522bfb8
10 changed files with 312 additions and 24 deletions
+64
View File
@@ -848,3 +848,67 @@ second provider pin on a subset of jobs, or router-side failover. **Not applied*
an audit one.
No secrets written; host names, IPs, VMIDs, job/incident IDs and probe status codes only.
## [2026-10-19] Nightly wiki audit — window 2026-10-18 00:00 → 23:59 AWST
**Window verdict: one failure all day, and it was a failure mode the wiki had never recorded.** Fleet
**28 jobs (25 enabled / 3 disabled)**; `10-18 = 168 completed / 1 failed` against `10-17 = 163 / 5`;
`10-19` so far `5 / 0` plus this audit. **11 sessions in the window, all `cron` — no interactive
sessions**, so no user decisions arrived to document; every finding below is machine-observed.
- **A model stream repeated itself and Hermes delivered the placeholder to Telegram.** `ecc1fc13655a`
(FreshRSS Midday, 12:00) wrote *"Your request was not processed. Send it again if you still want me to
carry it out."*, **delivered it** (`delivery_outcome: delivered`, 12:08:11) and then died at 12:08:25 on
`RuntimeError: Model output entered a repetition loop and the stream was cut mid-loop; discarding the
degenerate response.` New page → [[incidents/2026-10-18-degenerate-stream-canned-substitute]]. The open
question is written down, not fixed: should the degenerate-stream guard suppress delivery (or re-queue)
instead of substituting text on the job's normal route?
- **Mattermost: cause found — CT255 is stopped**, superseding the 10-11 entry's "cause not determined".
Reconnect loop unchanged (`attempt 471` at 00:14:07, `connect timed out after 30s`, 5-minute cadence),
peer offline **29d**, and the host answers neither TCP `:8065` nor ICMP. Platform config still says
`enabled: true`, so the loop will keep logging until the container is started or the block retired.
- **New page: [[systems/push-notifications]] — the bridge is broken and has been for as long as the logs
go back.** `status.json`: `connected: false`, `error: …connection refused (nothing listens there on
this machine)`; the bridge dials `HERMES_PUSH_GATEWAY_URL=https://hermes.kangaroo-eel.ts.net`, which
`/etc/hosts` resolves to **`127.0.1.1`** where nothing serves 443, while the gateway itself is healthy
on `0.0.0.0:9119` (`/` → 302) and Serve still maps the name to it. **23,469** occurrences of that string
across `agent.log(.1-3)` + `errors.log(.1-2)`. Fix documented, **not applied**.
- **Mnemosyne: the 10-18 12:0x red was a capture-staleness false positive, not a break.** `working_memory`
had no non-cron row since 10-16 11:07 because no conversation had happened; consolidation ran 10-18
03:55 with 0 items; coverage 96.8 % working / 99.4 % episodic (from the 10-18 12:1x read now carried in
the page); 1 unresolved conflict. The 24 h threshold in `mnemosyne-health-check.sh:92` will keep
flagging idle weekends.
- **Stocktake landed and closed the two-day hole:** `1a8e90ea2271` exited 0 on 10-18 03:00,
`freshness-20261018.txt` written, [[systems/skills-index]] regenerated (346 skills / 70 categories;
freshness 47 stale / 41 fresh / 7 no-date) and committed (`dd53e5f`).
- **Carried forward, still open:** the GitHub Trending Radar delivery token (`getMe` → 401, verified
10-18) — its next exercise is **Mon 2026-10-19 09:00**; the single-node `custom:omni-101` topology with
no model-call failover; and the vault drift below.
**Pages touched:** `incidents/2026-10-18-degenerate-stream-canned-substitute.md` (**new**);
`systems/push-notifications.md` (**new**); `systems/scheduled-tasks.md` (frontmatter + Count bullet +
FreshRSS row + totals); `systems/messaging-integrations.md` (frontmatter + new Mattermost section);
`systems/mnemosyne.md` (frontmatter + new tier/health block); `infrastructure/tailscale.md` (frontmatter +
inventory header + three missing peers + `mattermost` age); `infrastructure/proxmox.md` (CT255 age);
`current-state.md`; `index.md`; `log.md`. **Nothing removed or archived** — no page became obsolete and no
one-way sync was run.
**Bridge housekeeping + vault drift (verified 2026-10-19 00:2x).** Of the ten files this run touched, six
were byte-identical between the authoring tree and the vault copy *before* the edits; two more
(`infrastructure/tailscale.md`, `infrastructure/proxmox.md`) differed only because the vault holds
**older** versions (2026-07-27 and 2026-10-12), i.e. the vault never received the 10-14/10-16 tailscale and
proxmox work. Files were committed and pushed in the authoring tree, then copied into the vault (`wiki/`
nesting) with sha256 verified per file.
**Vault drift measured:** against authoring `HEAD`, the vault holds **74 identical pages, 11 stale** and
**12 missing**. Stale: `infrastructure/network-map.md`, `infrastructure/tailscale.md`,
`infrastructure/proxmox.md`, `infrastructure/docker-services.md`, `systems/skills-index.md`,
`systems/current-profile.md`, `systems/home-assistant.md`, `systems/ignis.md`, `systems/nanobot.md`,
`systems/obsidian.md`, `incidents/2026-08-01-mnemosyne-capture-failure.md`. Missing:
`incidents/2026-09-02-sftpgo-outage.md` (flagged by the 10-18 audit and still absent), the seven
`agents/*` pages, `reports/communities-wa-social-media-audit-2026.md`, `CONTRIBUTING.md`, plus this run's
two new pages (copied immediately after). The vault repo's own HEAD is still `9bacd8e mirror(2026-10-16)`
with a working tree carrying uncommitted 10-17/10-18 changes, and it has **no remote**, so it cannot be
pushed. **Not fixed** — a full mirror pass is a bigger call than an audit's mandate; flagged here.
No secrets written; host names, IPs, VMIDs, job/incident IDs, ports and probe status codes only.