12 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
agent-zero	64790ebd19	feat(litellm): align contracts for 7-provider cloud consolidation (2026-09-20) ... - hermes-key-enforcement: add Model Access Tiers (local vs cloud) and cloud-scoping clause - litellm-api-keys: add Cloud Provider Consolidation section (provider map, vault secrets, access tiers) - litellm-api-keys: pin standard agent keys to explicit local-only models list; forbid {}/all-proxy-models (Community-edition cloud leak) - contract-registry: register litellm-api-keys (was unregistered drift) Additive only. Local prose-lint: PASSED.	2026-09-20 10:53:33 -04:00
agent-zero	832b184af6	fix(litellm): upgrade contract refs 1.90.0-rc.1 -> 1.99.1 and correct redis role ... - harness-litellm pinned tag updated to 1.99.1 in infrastructure-control, litellm-health, litellm-self-heal container tables - infrastructure-update MCP per-key limitation note now cites v1.99.1 - harness-redis role corrected: dead 'Router slots, circuit breakers' -> 'LiteLLM cache + rate-limit state' (router decommissioned 2026-09-11) - litellm-self-heal Rule 9 wording clarified for cache/rate-limit only Live verification 2026-09-11: harness-litellm healthy, /health 200/200, 7 models, 46 keys, prisma migrations 127 -> 157.	2026-09-11 15:05:00 -04:00
agent-zero	c26255f5ff	fix(router): decommission legacy GPU router across contracts and fleet scripts ... Router container, image, and config are purged on CT 116 (verified: no container, no image, inference-harness-router:latest removed, :9000 free, 11 containers healthy, 7 models, live syslog-auto completion OK). Updates: - gpu-fleet.prose.md: topology diagram rebuilt without the router tier - gpu-monitor / gpu-self-heal / litellm-health / litellm-self-heal: router steps dropped - infrastructure-control.prose.md: container inventory + litellm row corrected - scripts/daily-infra-report.py, scripts/prose-ai-review.sh: host-scoped checks Verified: 40/40 anchors matched uniquely, 0 U+FFFD across changed files, daily-infra-report.py compiles, no stray harness-router references remain.	2026-09-11 14:20:18 -04:00
agent-zero	2e70c834cb	docs(infrastructure-update): add mandatory digest-pin sweep to Wave 3 verification ... Digest-pinned images (image: repo@sha256:...) are invisible to 'docker compose pull' — the pin re-pulls the same digest forever, so new releases never appear. Verified 2026-09-10: audiobookshelf ran 2.34.0 for 7 weeks despite weekly pulls; un-pinned to :latest, now 2.36.0 (HTTP 200). Dockhand stack (also pinned) was removed 2026-09-10 as unused (user decision). Weekly task qSOOVzsU now sweeps for digest pins every run and flags them for user-approved un-pinning.	2026-09-10 06:30:07 -04:00
agent-zero	bfdff13ae7	docs(infrastructure-update): point weekly trigger at scheduler task qSOOVzsU ... Weekly Sunday 03:00 America/New_York run is now implemented as Agent Zero scheduled task 'weekly-fleet-docker-update' (qSOOVzsU) with built-in post-update service verification and old-image pruning.	2026-09-08 05:27:38 -04:00
agent-zero	8bf32f6f0f	update(infrastructure-update): v1.3.0 — full Docker ecosystem coverage from 2026-09-08 live run ... - Add 5 Docker ecosystems: docker-vm .7, CT 116 .116, CT 117 (zulip+jitsi), hwpve .11 (Authentik), NetBird VPS 72.61.0.17 - Wave 3: add trove-test, docker-stats, monitoring stack, Zulip (pct exec + compose recreate preserves zulip_default network), Jitsi, Authentik, NetBird - Firecrawl test is now POST /v1/search (GET / returns 404 by design) - Add Authentik 302 + NetBird dashboard 200 checks - Document harness-litellm 3-5 min cold start after recreate (verified 2026-09-08) - Add hwpve + VPS compose files to config backup list; success criteria covers 5 hosts	2026-09-08 03:23:03 -04:00
Agent Zero	8b00a4beea	docs: Mumuni now inside Abiba CT 100 in zulip-resilience-v3 status table	2026-08-15 20:13:29 -04:00
Agent Zero	19a67c6815	fix: align mumuni ct field to 100 in daily-infra-report.py	2026-08-15 20:12:09 -04:00
Agent Zero	8f89603c31	fix: use IP 192.168.68.17:3000 instead of git.sysloggh.net hostname for CI checkout ... The Gitea Actions runner cannot resolve the internal hostname git.sysloggh.net during checkout. Using the direct IP address resolves the DNS resolution issue in CI pipeline steps.	2026-07-06 18:54:12 -04:00
Agent Zero	f1a031b682	fix: Firecrawl health endpoint is / not /health	2026-07-06 18:21:30 -04:00
Agent Zero	f14b2fc04e	infra-update contract: v1.1.0 - fix CT→VM refs, remove deprecated stacks	2026-07-06 18:05:16 -04:00
Agent Zero	09ffbf10aa	infra-update contract: v1.1.0 — fix CT→VM refs, add missing stacks, correct paths	2026-07-06 18:05:16 -04:00