2026-11-18 stocktake: re-verify 7 stale pages against live state, resolve gmail-digest refire incident
This commit is contained in:
@@ -3,8 +3,8 @@ title: Provider Health Check
|
||||
type: runbook
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-26
|
||||
verified_on: 2026-10-26
|
||||
updated: 2026-11-18
|
||||
verified_on: 2026-11-18
|
||||
last_tested: 2026-10-26
|
||||
confidence: high
|
||||
tags: [runbook, providers, health, routing]
|
||||
@@ -58,6 +58,8 @@ with urllib.request.urlopen(req, timeout=5) as r:
|
||||
```
|
||||
Current verified result (2026-10-26): reachable and returns a non-empty model catalog — **6,480 models** on `omniroute:20128` (CT600, 100.88.81.19).
|
||||
|
||||
> **Re-executed 2026-11-18:** step-3 snippet OK — CT600 `/models` → 200, **6,501 models** (3.6 s; one earlier attempt at the default 5 s timeout timed out, so give this probe headroom). CT600 `/api/health` → 200; `omni-101` `/api/health` → 200; fallback endpoints `opencode.ai` / `inference-api.nousresearch.com` / `ollama.com` all → 200.
|
||||
|
||||
### 3b. Check the default `omni-101` provider (CT101, 100.78.63.20)
|
||||
The **default provider** is `custom:omni-101` → `http://100.78.63.20:20128`, keyed via
|
||||
`HERMES_CUSTOM_100_78_63_20_20128_API_KEY`. Probe it with its **own** key — the CT600 key is rejected here:
|
||||
|
||||
@@ -3,8 +3,8 @@ title: Update Hermes safely
|
||||
type: runbook
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-26
|
||||
verified_on: 2026-10-26
|
||||
updated: 2026-11-18
|
||||
verified_on: 2026-11-18
|
||||
last_tested: 2026-10-26
|
||||
confidence: high
|
||||
tags: [runbook, hermes, update]
|
||||
@@ -28,6 +28,8 @@ Update Hermes to a newer release without losing configuration, skills, or sessio
|
||||
- Available disk space in Hermes install and backup paths
|
||||
- No active Hermes chat/webui shell issues before starting
|
||||
|
||||
> **Re-verified 2026-11-18:** prerequisites hold on CT460 — `hermes --version` → `v0.23.0` from the git install at `/home/hermes/.hermes/hermes-agent`, legacy `venv/` present, three managed runtime venvs present under `~/.hermes/installs/019d0d114d22b7e6/environments/*/venv`. (CT450 currently runs `v0.23.1` — see [[incidents/2026-10-03-ct450-hermes-update]].)
|
||||
|
||||
## Procedure
|
||||
|
||||
### 1. Create a backup first
|
||||
|
||||
Reference in New Issue
Block a user