audit corrections 2026-11-05: fleet count 29/26/3 (was 158/144/14), 11-04 closes 167 completed/2 failed/1 running, 11-03 re-settled 171/1, deepseek-paid-smart 503 on omniroute:20128 vs 200 on omniroute-1
This commit is contained in:
@@ -47,7 +47,11 @@ Cron jobs inherit the profile-level `fallback_providers` chain; Hermes does not
|
||||
> process and confirm the letters rendered - do **not** ship a run without its cover letters. Note the same model
|
||||
> name still serves other cron jobs successfully (e.g. the 23:59 nightly audit), and the endpoint itself is live:
|
||||
> `omniroute:20128/v1/models` -> **401** and `100.78.63.20:20128/v1/models` -> **401** on 2026-11-05 (key-gated,
|
||||
> not down). Treat a 402 as **route/time-specific until re-tested**, not as proof the route is dead.
|
||||
> not down). Treat a 402 as **route/time-specific until re-tested**, not as proof the route is dead. **Keyed re-test 2026-11-05 01:33:12 AWST:** `deepseek-paid-smart` -> **503 `ALL_TARGETS_SKIPPED`**
|
||||
> (`poolSize 5`, `attempted 0`) on `omniroute:20128`, but **200** on `100.78.63.20:20128` (`omniroute-1`, resolved to
|
||||
> `deepseek/deepseek-v4-flash`). As of that probe the default `CL_MODEL` **cannot dispatch on the CT600 node**, so a
|
||||
> `CL_MODEL` override (or an `omniroute-1` base URL) is required for cover-letter runs. An unkeyed `/v1/models` 401 is
|
||||
> auth-gating, not health.
|
||||
|
||||
|
||||
A successful radar run includes the cover-letter stage.
|
||||
|
||||
Reference in New Issue
Block a user