205 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
root	245a4ffbea	Merge PR #38: feat: add Level 0 auto-delete for heartbeat log orphans	2026-07-29 21:52:14 +00:00
root	7c0adefdeb	Merge PR #38: feat: add Level 0 auto-delete for heartbeat log orphans	2026-07-29 21:50:19 +00:00
root	88b8cb96a5	feat: add Level 0 auto-delete for heartbeat log orphans	2026-07-28 23:30:33 +00:00
mumuni-bot	2623e05752	Merge pull request 'docs: add gitea-logger implementation example' (#37) from fix/gitea-logger-docs into master	2026-07-28 21:23:24 +00:00
root	42a1d0bd91	docs: add gitea-logger implementation example to litellm-self-heal	2026-07-28 21:23:04 +00:00
mumuni-bot	e052a069cb	Merge pull request 'fix: redirect health check logs from knowledge graph to Gitea (hard rule)' (#36) from fix/health-logs-to-gitea into master	2026-07-28 21:21:46 +00:00
root	c9359e1808	fix: redirect health check logs from knowledge graph to Gitea (hard rule) ... Logs (LITELLM-HEALTH, GPU-SELF-HEAL, PM2) now pushed to SyslogSolution/health-logs instead of creating orphan nodes in the shared knowledge graph. - litellm-self-heal: Phase 4 now calls gitea-logger instead of kg-logger - gpu-self-heal: Reporting section updated to Gitea path - pm2-self-heal: Log step redirected to Gitea - 271 existing orphan nodes remain in graph (no delete tool available)	2026-07-28 21:20:56 +00:00
mumuni-bot	6a0af728e9	Merge pull request 'fix: update all Mumuni IP references from .123 to .24 (inside Abiba CT100)' (#35) from fix/mumuni-ip-abiba into master	2026-07-28 08:57:05 +00:00
root	3b6cf44a30	fix: update all Mumuni IP references from .123 to .24 (inside Abiba CT100) ... Mumuni CT114 destroyed. Mumuni now runs inside Abiba CT100 at 192.168.68.24. Updated all contract files and agent-health-check.py.	2026-07-28 08:56:45 +00:00
mumuni-bot	835647e241	Merge pull request 'fix: correct quant to UD-Q3_K_XL (Q4 too large for 24GB VRAM)' (#34) from fix/gpu-dense-q3-correction into master	2026-07-27 20:26:13 +00:00
root	22b015e182	fix: correct quant to UD-Q3_K_XL (Q4 too large for 24GB VRAM)	2026-07-27 20:25:51 +00:00
mumuni-bot	29e32340a4	Merge pull request 'fix: swap gpu-dense to SmartCode-Fable-5 (ThinkingCap + Fable 5 CoT)' (#33) from fix/gpu-dense-smartcode-fable5 into master	2026-07-27 16:43:46 +00:00
root	179529de71	fix: swap gpu-dense to SmartCode-Fable-5 (ThinkingCap + Fable 5 CoT) ... gpu-dense on RTX 3090 swapped from qwen3.6-27B-code to SmartCode-Fable-5-CoT-Reasoning-QKVO-Qwen-3.6-27B-Distilled (UD-Q4_K_XL, ~17.9GB).\n\nImprovements:\n- ~50% fewer thinking tokens via ThinkingCap finetune\n- Fable 5 CoT distillation for improved coding reasoning\n- Same 27B base, fits RTX 3090 at ~73% VRAM\n- Recommended samplers: temp 0.9, top-p 0.95, top-k 60\n- Context: 128K (fleet standard)	2026-07-27 16:43:29 +00:00
mumuni-bot	fb45007ace	Merge pull request 'fix: remove mumuni from health check — now inside Abiba CT 100' (#32) from fix/update-health-check-remove-mumuni into master	2026-07-26 12:37:35 +00:00
root	0f572ff9f2	fix: remove mumuni from health check — now inside Abiba CT 100	2026-07-26 12:37:07 +00:00
mumuni-bot	3a8e7d9b3a	Merge pull request 'fix: remove CT 114 (mumuni) — destroyed, moved inside CT 100' (#31) from fix/remove-mumuni-ct114 into master	2026-07-26 12:36:31 +00:00
root	0fb54926f6	fix: remove CT 114 (mumuni) — destroyed, moved inside CT 100	2026-07-26 12:36:02 +00:00
mumuni-bot	146abf7f82	Merge pull request 'fix: agent health check v2 — CT liveness, config validation, wrapper integrity, vault emptiness' (#30) from fix/agent-health-check-v2 into master	2026-07-26 12:27:20 +00:00
root	c869e75c61	ci: trigger recheck	2026-07-26 12:24:05 +00:00
root	47aa92bee3	fix: verification protocol findings — CT 118 static IP, .110 llama-server restored ... Verification protocol run 2026-07-26: - CT 118 (jdownloader): DHCP had moved it to .131 post-reboot. Now set to static .20. - RTX 5070 (.110) llama-server: was stopped (disabled unit). Started and verified — gemma-4-12b responding through LiteLLM. - All 6 PVE nodes confirmed at correct IPs. - All 18 CTs confirmed at correct IPs on correct nodes. - All public endpoints responding (meet, chat, git, litellm, vault, auth). - Container counts verified: docker-vm 14 ctrs, CT 116 10 ctrs, VPS 5 ctrs.	2026-07-26 12:20:58 +00:00
root	de9adb13cf	fix: agent health check v2 — CT liveness, config validation, wrapper integrity, vault emptiness ... Gaps fixed: - Koby (.129) and Koonimo (.114) now have SSH hosts — no longer skipped - Agent key lookup uses correct {NAME}_LITELLM_API_KEY format - New CT liveness check via pct status on PVE nodes - New config YAML integrity check via yaml.safe_load() - New wrapper/CLI integrity check (hermes wrapper, infisical path, hermes-real) - New vault secret non-emptiness check - Ops escalation: failures produce ALERT lines for cron capture	2026-07-26 12:06:32 +00:00
root	2ace79fcab	no-mistakes(document): Update 5→6 node references and fix CT ID contradictions	2026-07-24 21:36:38 +00:00
root	87b4d67067	no-mistakes(review): Fix 5 review findings: duplicate table header, hwepve specs/Wave2 target, dangling ref, Authentik port	2026-07-24 21:31:28 +00:00
root	7d1db62a8e	no-mistakes(document): Fix stale CT placements across 5 docs matching infrastructure-control updates	2026-07-24 20:21:03 +00:00
root	9943be5e68	no-mistakes(test): Lint, shell syntax, and all 13 user-intent constraints pass on 3 changed files. One mode fix: netbird-add-domain.sh 644→755	2026-07-24 20:16:57 +00:00
root	fa26b7a579	no-mistakes(test): Fixed 7 cross-table inconsistencies: kagentz placement, mumuni placement, stale 5-node references	2026-07-24 20:14:49 +00:00
root	c380196fab	fix: address review findings ... - Remove kagentz from amdpve node table (belongs on hwepve) - Fix kagentz pct-run table: hwepve (was amdpve) - Fix mumuni pct-run table: hwepve (was minipve) - Fix Zulip recovery command: wrap in single SSH call	2026-07-24 20:11:32 +00:00
root	b17c60f997	fix: contract accuracy updates post fleet-wide reboot ... infrastructure-control.prose.md: - Add hwepve as 6th Proxmox node - Fix Gitea IP: .17 (was .110) - Fix AdGuard IP: .10 on minipve (was .102 on acerpve) - Fix Abiba placement: hwepve (was amdpve) - Fix Mumuni placement: hwepve (was minipve) - Fix Authentik port: add :9000 - Add CT 118 (jdownloader), CT 119 (infisical-vault) - Add last-verified date (2026-07-24) infrastructure-update.prose.md: - Add post-reboot CT sweep procedure - Add Zulip Docker network recovery steps - Add WireGuard tunnel verification scripts/netbird-add-domain.sh: - New script to register domains in Netbird proxy store.db	2026-07-24 20:01:43 +00:00
abiba-bot	2f0c3c1850	fix: update contracts for hwepve 6th node + Mumuni recovery	2026-07-23 18:47:17 +00:00
jerome	cedbdc465d	Merge branch 'master' into fm/mumuni-recovery-hwepve	2026-07-23 18:11:06 +00:00
abiba-bot	8b09c78efd	Merge: PR #26 conflict resolution — hwepve 6th node + qwen model ref	2026-07-23 18:10:36 +00:00
root	767ab25128	merge: resolve PR #26 conflict — keep qwen model ref + add hwepve node	2026-07-23 18:10:18 +00:00
root	cd479caeec	Fix: update compression model to syslog-auto across contract and audit (Rule 7) ... - Updated hermes-config-template.prose.md: all references to strix-moe for compression changed to syslog-auto to match operational decision on 2026-07-23 (prevents sustained Strix Halo thermal load via weighted pool). - Updated audit-hermes-config.py Rule 7 to expect syslog-auto instead of strix-moe, ensuring Abiba's next run validates against the correct baseline.	2026-07-23 18:02:56 +00:00
root	1b1de8b0fc	Add Rule 14 (provider name must match custom_providers) + audit script ... Rule 14: model.provider MUST be 'harness' (custom_providers[0].name), NOT 'custom'. When provider: custom, Hermes falls through to generic resolution path that ignores key_env, producing 'no-key-required' → HTTP 401. audit-hermes-config.py: encodes all 14 contract rules as automated checks. Run before and after any Hermes config change. Root cause: WAL #1471 (2026-07-19 Mumuni 401 incident)	2026-07-23 12:16:33 +00:00
abiba-bot	75381f9737	Captain decision batch 2026-07-21: ornith decommission, 256K→128K context, Mumuni Discord disable ... Three contract updates per captain decision batch. Validated through no-mistakes pipeline (green).	2026-07-23 09:13:06 +00:00
root	2b9b545ca9	no-mistakes(document): Fixed 2 stale model-name references in doc files	2026-07-23 09:10:43 +00:00
root	e6c52bf071	no-mistakes(review): Fix F1 model rename and F2 128K compaction math in contracts	2026-07-23 09:04:51 +00:00
root	1c44bf1259	contract updates: ornith decommissioned, 256K→128K context, Mumuni Discord disabled ... Change 1: Strix Halo — ornith decommissioned - gpu-fleet: Genesis Hermes V3 APEX → qwen3.6-35B-udq4 throughout - inference-optimization: ornith→strix-moe/qwen3.6-35B-udq4 - gpu-monitor: ornith status → Strix Halo status - infrastructure-control: Strix Halo — ornith → qwen3.6-35B-udq4 - infrastructure-update: ornith→strix-moe via router - proxmox-monitor: Strix Halo LLM (ornith) → (qwen3.6-35B-udq4, strix-moe) Change 2: GPU context 256K→128K fleet-wide - hermes-agent-baseline: frontmatter description updated - litellm-health: GPU Fleet Topology table 256K→128K - litellm-self-heal: GPU Fleet Topology, engine flags, VRAM alert - inference-optimization: compress threshold 256K→128K compact at 85K - gpu-fleet: instability note updated Change 3: Mumuni Discord platform disabled - gpu-fleet: Mumuni platforms: removed discord	2026-07-23 09:00:42 +00:00
root	9f0e04f22c	fix: update contracts for hwepve 6th node + Mumuni migration (lxc/114 on hwepve) ... - proxmox-monitor: 5→6 nodes, add hwepve (.4, Huawei Matebook 16), note Mumuni (lxc/114) placement - zulip-health: add dual-gateway collision detection to B2, note Mumuni on hwepve - hermes-agent-baseline: fix Mumuni node minipve→hwepve - hermes-zulip-restore: add hwepve Proxmox column for Mumuni - mumuni-delegation: fix CT 118/storepve/.6 → lxc/114/hwepve/.123, 5→6 nodes - pm2-self-heal: verified — no Mumuni references, no changes needed Post-migration discoveries: - Mumuni container migrated from minipve to hwepve (6th node, 192.168.68.4) - IP preserved (192.168.68.123), hostname 'mumuni' unchanged - Dual gateway collision (PID 1442 --replace + PID 2924 --force) resolved by container restart at 10:07; gateway restarted clean at 13:06 with fresh Zulip queue (errors=0, reconnects=0)	2026-07-20 17:08:58 +00:00
jerome	fc88265e76	Merge pull request 'tune: switch compression model from strix-moe to syslog-auto' (#25) from tune/compression-syslog-auto into master ... Reviewed-on: #25	2026-07-19 01:32:44 +00:00
jerome	51da19d92d	Merge pull request 'feat(contracts): add infrastructure-maintenance contract' (#24) from fm/infra-maint-contract into master ... Reviewed-on: #24	2026-07-19 01:32:29 +00:00
root	6570fd60e7	tune: switch compression model from strix-moe to syslog-auto ... Relieve Strix Halo pressure by distributing compression across the syslog-auto weighted pool (55% RTX 3090, 30% Strix Halo, 15% RTX 5070). Updates: - compression.model: strix-moe -> syslog-auto - auxiliary.compression.model: strix-moe -> syslog-auto - Rule 7: Updated for syslog-auto compression, removed aux prohibition - Rule 8: Updated GPU workload distribution - All docs/comments updated to reflect the change	2026-07-18 23:28:07 +00:00
jerome	5d2ecbace6	Merge branch 'master' into fm/infra-maint-contract	2026-07-18 23:12:20 +00:00
root	99789a00a1	no-mistakes(document): Reframed infra-maintenance contract as deliberate partition	2026-07-18 22:16:09 +00:00
root	a68879e904	no-mistakes(review): fix docker rollback command to pin digest then compose up	2026-07-18 22:07:15 +00:00
jerome	06d2bcbc9e	Merge pull request 'fix: fleet config issues from 2026-07-18 relay review' (#23) from fix/fleet-config-issues-20260718 into master ... Reviewed-on: #23	2026-07-18 22:06:48 +00:00
jerome	c4a8c45835	Merge pull request 'zulip-resilience: fleet-wide audit findings and fixes 2026-07-18' (#22) from feat/zulip-resilience-audit-20260718 into master ... Reviewed-on: #22	2026-07-18 22:06:34 +00:00
root	1d027f71f6	feat(contracts): add infrastructure-maintenance contract ... New responsibility contract consolidating host-level system maintenance and Docker image lifecycle management, filling the gap left by infrastructure-update (which owns cluster-wide apt waves). Scope: - OS package updates on primary host with pre-update snapshot/backup check - Docker image pulls for LiteLLM, SearXNG, and other running containers - Container restarts with per-stack health verification - Post-update verification: LiteLLM, SearXNG, Zulip, Gitea, PM2, Hermes gateways - Rollback on failure (image/apt/config restore) with circuit breaker Owner: ops (firstmate secondmate). Trigger: weekly Sunday 2am ET. Escalation: warning/critical->abiba+mumuni, fatal->abiba+mumuni+kwame. circuit_breaker: max_retries 2, window 7200, trip_action escalate_to_fatal. depends_on: infrastructure-monitoring (pre-update health baseline). Registry: - Add infrastructure-maintenance to by_category.maintenance, by_domain.infrastructure, by_owner.ops (new), by_trigger.scheduled, by_sensitivity.high - Add 'ops' to owners list - Move infrastructure-update owner abiba -> ops (in contracts entry + by_owner index) Also adds '## Maintaining this file' section to AGENTS.md per fm-ensure-agents-md.	2026-07-18 22:02:45 +00:00
jerome	a74229ee74	Merge branch 'master' into fix/fleet-config-issues-20260718	2026-07-18 18:06:19 +00:00
root	aebc98ead6	fix: remove trailing whitespace from litellm-api-keys.prose.md	2026-07-18 17:48:52 +00:00