stocktake 2026-11-06 (pass 2): re-verify the one page sitting on the 21-day threshold

incidents/2026-10-14-omniroute-node-connection-refused-storm.md was at exactly 21d and
would have tripped the threshold on the next run. Its residual claim ("omniroute-1
answers again") was re-probed live and still holds: TCP connect to 100.78.63.20:20128
succeeds (no Errno 111), the Tailscale peer reads Online:true, and a keyed
POST /v1/chat/completions returns HTTP 200. Page re-verified (updated/verified_on ->
2026-11-06, review_after -> 2026-12-06) with the probe recorded on the page.

New trap recorded on the page and in systems/scheduled-tasks.md: on omniroute-1 the
RAW model id deepseek/deepseek-v4-flash returns HTTP 401 "No active credentials for
provider: deepseek", while the fleet's deepseek-paid-smart alias returns HTTP 200 and
resolves to that same model. The 401 is an alias-routing artefact, not an outage - probe
the alias the fleet pins, never the raw model id. (A first probe using the wrong
key_env also produced a 401; omni-101's key env is HERMES_CUSTOM_100_78_63_20_20128_API_KEY.)

Freshness re-run after the edits: 0 stale / 124 fresh / 3 no-date of 127 pages.
Quartz rebuilt and redeployed. Vault mirror synced to both conventions (sha-verified).
This commit is contained in:
Tony0410
2026-11-06 04:07:12 +08:00
parent 88baf4fb5a
commit 2d5219b068
4 changed files with 35 additions and 5 deletions
+13
View File
@@ -2171,3 +2171,16 @@ embedded credential was seen during verification and is not reproduced here ([RE
`deepseek-paid-smart`-on-`omniroute` dispatch fault and the `066bb5191280` delivery failure carried, not
re-diagnosed; the open secrets-at-rest incident not re-litigated. **No secrets, tokens or keys written or
quoted.**
- **Follow-up (04:0x AWST): the one page sitting exactly on the 21-day threshold was re-verified rather
than left to expire.** `incidents/2026-10-14-omniroute-node-connection-refused-storm.md` was at **21d** and
would have tripped the threshold tomorrow. Its residual claim ("`omniroute-1` answers again") was
re-probed **live** and still holds: TCP connect to `100.78.63.20:20128` succeeds (no `Errno 111`),
the Tailscale peer reads `Online: true`, and a keyed `POST /v1/chat/completions` returns **HTTP 200**.
Page re-verified (`updated`/`verified_on` -> 2026-11-06, `review_after` -> 2026-12-06) with the probe
recorded. ⚠ **New trap recorded on the page and in [[systems/scheduled-tasks]]:** on `omniroute-1` the
**raw** model id `deepseek/deepseek-v4-flash` returns **HTTP 401 `No active credentials for provider:
deepseek`**, while the fleet's **`deepseek-paid-smart` alias returns HTTP 200** and resolves to that same
model. The 401 is an **alias-routing artefact, not an outage** — probe the alias the fleet pins, never the
raw model id. (A first probe with the wrong `key_env` also produced a 401; the correct key for
`omni-101` is `HERMES_CUSTOM_100_78_63_20_20128_API_KEY`.)