stocktake(2026-11-01): fix the Quartz build (YAML title), close the "unfixed memory ranking" incident, and correct live drift in tailscale/docker/proxmox

BUILD FIX — the stocktake script was failing at step 3/3 with an opaque esbuild panic.
Root cause: incidents/2026-10-31-conduit-voice-local-mode-not-applying.md had an
unquoted YAML title containing ": " (from "voice mode: local"), which YAML parsed as a
mapping entry and Quartz rejected with "bad indentation of a mapping entry (2:27)".
A scan of all 117 pages found exactly one such line; it is now properly quoted.
Quartz now builds cleanly: 690 files emitted and deployed.

RESOLVED — incidents/2026-10-09-memory-recall-relevance.md (was the only stale page).
The page claimed the recall-ranking fix "was not present in live config" and that
conflict 152 was "the only open conflict". Both claims were false:
- The weights ARE persisted, in ~/.hermes/mnemosyne/config.yaml (vec_weight 0.5,
  fts_weight 0.3, importance_weight 0.3) plus MNEMOSYNE_IMPORTANCE_WEIGHT=0.3 —
  not in ~/.hermes/config.yaml's memory.mnemosyne block, which is what the
  2026-10-10 probe read. The page was the reason the incident looked open for 3 weeks.
- The original regression test now passes: "mnemosyne recall 'Are you up to date'"
  returns only substantive current-state facts (scores 0.174/0.130/0.123); the stale
  Uber Eats episode no longer outranks anything.
- Conflict 152 was auto-resolved 2026-10-29 23:53:47Z as extraction noise.
All three open items closed; page moved to status: resolved.

LIVE DRIFT CORRECTED (all verified against live systems on 2026-11-01):
- infrastructure/tailscale.md: omarchymac went offline (genuine transition, ping
  times out); m93p peer record reads false for the 4th consecutive time while the
  host pongs and SSH returns up 1d12h, so the row stays online; 5 offline ages
  refreshed; no IP changes, no missing peers.
- infrastructure/docker-services.md: CT201's Tailscale IP was wrong
  (100.116.116.116 -> 100.96.244.39); 3 misspelled overchat-* entries and 1 stale
  worldmonitor-seeder-fast entry removed from the CT200 list, which is now
  regenerated verbatim from live docker ps; CT333's adoring_jemison renamed to
  thirsty_payne.
- infrastructure/proxmox.md: storage percentages refreshed on both hosts from live
  pvesm status; pct/qm lists re-confirmed (no CT601 anywhere); m93p uptime and an
  elevated load average recorded.
- systems/mnemosyne.md, systems/omniroute.md, systems/messaging-integrations.md:
  re-probed and verified_on bumped.
- systems/skills-index.md: regenerated — 301 unique skills in 68 categories,
  46 archived. (301 is the unique (category, skill_name) count; find returns 302
  files due to the known nested obsidian-git-sync alias duplicate.)

Freshness report: 0 stale / 114 fresh / 3 no-date of 117 pages.
This commit is contained in:
Tony0410
2026-11-01 04:48:30 +08:00
parent c69681dc16
commit a0b3734c95
14 changed files with 596 additions and 111 deletions
+29 -2
View File
@@ -3,8 +3,8 @@ title: Messaging Integrations
type: system
status: active
created: 2026-07-22
updated: 2026-10-26
verified_on: 2026-10-26
updated: 2026-11-01
verified_on: 2026-11-01
confidence: high
tags: [messaging, telegram, discord, email, integrations]
sources: [raw/configs/hermes-config-sanitized.txt, live-jobs-json, live-himalaya-debug]
@@ -125,3 +125,30 @@ one of those happens — restarting the adapter while the host is stopped achiev
process's** attempts, not the outage's length — do not quote it as downtime.
- **Impact unchanged:** messaging path only; no cron job delivers via Mattermost.
- **Not attempted:** `pct start 255` — starting a service on the PVE host is Anthony's call.
## 2026-10-31 06:2x AWST — ✅ Mattermost RECOVERED (outage over)
**The ~40-day Mattermost outage is over.** All three live checks pass, and the gateway log confirms
the adapter stayed connected since.
| Check | Live result (2026-10-31) |
|---|---|
| `pct list` on `pve` | **CT255 (`mattermost`) → `running`** (was `stopped`) |
| `pct exec 255 -- systemctl is-active mattermost` | **`active`** |
| `pct exec 255 -- ss -ltn` | `LISTEN *:8065` |
| `tailscale ping 100.98.116.14` | **`pong from mattermost ... in 0s`** |
| `curl http://100.98.116.14:8065/api/v4/system/ping` | **HTTP 200** |
| Tailscale peer record | **`Online: true`** — first time since the outage began |
- **Gateway reconnection (CT460's own `gateway.log`):** `Mattermost: authenticated as @rhino-bot` at
**2026-10-30 07:19:37**, with `✓ mattermost reconnected successfully` and a successful WebSocket
handshake at the same second. A second connect cycle at **2026-10-30 16:36:07** produced
`✓ mattermost connected` at **16:36:17**.
- **No errors since.** Grepping every `mattermost` line in `gateway.log` after `2026-10-30 16:36:17`
returns **zero** `error` / `timeout` / `disconnect` / `fail` lines — the 5-minute reconnect loop that
produced 264–268 timeouts a day is **no longer running**.
- **The prior "cause: CT255 is stopped" finding is superseded.** CT255 is running; the gateway can
reach `http://100.98.116.14:8065/` and authenticate. → [[infrastructure/proxmox]],
[[infrastructure/tailscale]]
- **Open item now closed:** the platform is no longer an outage. The home channel startup notification
was delivered successfully on reconnect (`Sent home-channel startup notification to mattermost:…`).