Abiba Bot 39cf297a8f Phase 0: Dual-key router — no hardcoded keys, gemma sync, 262K context fix ...

- Removed all hardcoded API_KEYS from source (env var now REQUIRED)
- Added dual-key transition support (old keys deprecated, logged)
- Model sync: qwen3.5-9b-vlm → gemma-4-12b everywhere
- Dense context: 131K → 262K (all 3 models at 262K)
- Added /admin/keys endpoints for key lifecycle management
- Added ADMIN_KEY env var for admin auth
- Dashboard already synced to gemma-4-12b labels

Deployment: set API_KEYS from phase0-dual-keys.json in docker-compose
Transition: 7 days dual-key, then POST /admin/keys/revoke

2026-06-06 00:51:29 +00:00

..

Dockerfile

Initial commit: CT 116 inference harness — nginx, LiteLLM, router, dashboard, Redis

2026-05-16 18:51:50 +00:00

requirements.txt

Initial commit: CT 116 inference harness — nginx, LiteLLM, router, dashboard, Redis

2026-05-16 18:51:50 +00:00

route_v2.py

router: reference - new 5-tier routing with vision guard (deployed CT116)

2026-06-05 23:32:27 +00:00

route_v3.py

router: v3 — 5-tier routing with vision guard, MoE spillover, code hint

2026-06-05 23:48:45 +00:00

router.py

Phase 0: Dual-key router — no hardcoded keys, gemma sync, 262K context fix

2026-06-06 00:51:29 +00:00