5 Commits

Include renames

Author	SHA1	Message	Date
root	8210fd905c	fix: align contracts to 4-name LiteLLM registry (2026-09-12) ... - Remove retired names (qwen3.6-27B-code, qwen3.6-35B-udq4) from live alias claims - Update Strix Halo model to Carnice-Qwen3.6-MoE-35B-A3B-Q4_K_M.gguf (strix-moe, 256K ctx) - Fix litellm-health step 7 probe to gpu-vision (monitor key scoped) - Move qwen3.6-27B-code/35B-udq4 from raw-but-live to non-resolving in audit - Fold in pm2-self-heal: remove spoton-service (live PM2 set is 4/4) - Update hermes templates, key enforcement, timeout tables to live names	2026-09-12 21:39:54 +00:00
root	ce48070f21	no-mistakes(review): Derive model fields recursively; fix historical latency and key claims	2026-09-12 16:33:58 +00:00
abiba	221f9f79f3	fix(audit): reject retired aliases; sweep gpu-light/gemma-4-12b to gpu-vision ... audit-hermes-config.py Rule 8 required auxiliary.vision.model and auxiliary.web_extract.model to equal the retired 'gpu-light', so a config adopting the live canonical 'gpu-vision' FAILED our own audit - the audit was enforcing a dead alias (400 Invalid model name). Rule 8 now requires gpu-vision; retired names gpu-light/crew-auto join the raw-name rejection set; the guidance message names the live aliases. Sweep of the remaining references: gpu-self-heal stops canonicalizing gpu-light; hermes-config-template, hermes-agent-baseline, hermes-key-enforcement, inference-optimization, litellm-client-timeouts and gpu-fleet now use the live gpu-vision alias. Where a file restated model/rpm/weight/fallback state it now points at CT 116 /opt/inference-harness/litellm_config.yaml instead of duplicating it. koby's .129 config is report-only and recorded, not edited. Adds tests/test_audit_hermes_config_alias.py: executes the audit CLI and asserts gpu-vision passes while gpu-light and gemma-4-12b fail.	2026-09-12 16:11:46 +00:00
root	21f7b6171c	no-mistakes(document): Dedupe cadence copies; registry remains authoritative	2026-09-12 16:02:15 +00:00
mumuni-bot	7bbf148778	feat: litellm-client-timeouts contract — standard client timeout/retry policy ... Root cause of the 2026-09-06 incident: 157 client-abandoned 408s against a backend that was succeeding at 20-70s/call once clients stopped giving up. Measured grounding: syslog-auto 28.8s avg / 25.4s TTFT over 888 calls; nginx already allows 600s (Rule 5); the gap was entirely client-side. Values: >=300s primary path, >=120s gpu-dense delegation, 2 retries with 15s/45s backoff, identified probes at 30s/hourly, batch jobs chunked + day-scheduled. Verified live: Prometheus metrics, 0.56s syslog-auto probe, gpu-fleet /health/unified topology.	2026-09-08 06:07:43 +00:00