241 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
tanko-bot	aa2451e8ae	fix: skip Hermes config/wrapper integrity checks for tanko (DSH) ... check_config_integrity and check_wrapper_integrity still probed tanko (CT 112) for Hermes-only artifacts (/root/.hermes/config.yaml, the hermes CLI wrapper) that no longer exist since tanko moved to DSH on 2026-08-27. This caused false FAILs in the agent health check. Both now skip tanko via runtime=dsh.	2026-08-27 03:06:49 +00:00
tanko-bot	c23462eba8	fix: correct tanko runtime to DSH across contracts & scripts ... Tanko migrated from Hermes to DSH (DeepSeek Harness) on 2026-08-27. Update all records that described tanko as a Hermes agent / Hermes runtime: - infra-control: CT 112 tanko platform Hermes -> DSH - zulip-health / zulip-self-heal / zulip-mention-reliability / pi-approval: tanko is on DSH, mumuni remains on Hermes - memory-audit-maintenance: exclude tanko from Hermes roster (uses DSH-native memory) - hermes-config-template / hermes-agent-baseline: remove tanko from Hermes roster, keep LiteLLM key alias 'tanko' - hermes-zulip-plugin / hermes-zulip-restore / build-zulip-plugin: tanko excluded - infrastructure-maintenance: gateways check no longer probes Hermes on tanko CT112 - scripts/daily-infra-report.py: fix CT-ID regression (CT 122->112), report tanko as DSH - scripts/zulip-monitor.sh: stop probing tanko's retired Hermes gateway - scripts/agent-health-check.py: skip Hermes gateway checks for tanko (runtime=dsh) - scripts/prose-auth-check.sh + AGENTS.md: authorize tanko/tanko-bot for its own records Tanko remains CT 112 at 192.168.68.122; infrastructure facts unchanged. Dated/incident records (run logs, migration logs) left intact as history.	2026-08-27 03:01:24 +00:00
abiba-bot	b835986d44	Merge pull request 'Add check-health section with live probes to infrastructure-monitoring contract' (#51) from fix/infra-check-health into master ... Merged by captain approval 2026-08-22: add check-health section with live probes to infrastructure-monitoring contract	2026-08-23 00:01:39 +00:00
root	d6ad016ac9	Add check-health section with live probes to infrastructure-monitoring contract ... Fixes the canned 'API UNREACHABLE (HTTP 000)' reporting. Adds an explicit check-health execution section (Zulip POST, pm2, GPU exporters, Prometheus, Grafana, LiteLLM probes) with a hard RUN LIVE, NEVER ECHO rule, mirroring the gpu-monitor contract pattern. Captain priority 2026-08-22.	2026-08-22 23:59:28 +00:00
mumuni-bot	c3306e87e4	Merge pull request 'fix: ship pm2-self-heal crash-loop guard + align gpu-dense docs to Qwen3.8-27B' (#49) from fix/pm2-guard-gpu-doc into master	2026-08-17 02:34:49 +00:00
mumuni-bot	20fe5adcbc	fix: ship pm2-self-heal crash-loop guard + align gpu-dense docs to Qwen3.8-27B ... - pm2-self-heal.sh: restart abiba-telegram when TEL_RESTARTS > 1000 even if 'online' (catches quiet crash-loops like the 10k-restarts spoton incident); alert includes count. - pm2-self-heal.prose.md: document the crash-loop guard under Rule 2. - gpu-fleet.prose.md / gpu-self-heal.prose.md: gpu-dense is Qwen3.8-27B-Uncensored-Q4_K_M (~16.8GB, alias qwen3.6-27B-code for LiteLLM routing), not SmartCode-Fable-5 (verified live on .8:8080 Aug 16).	2026-08-17 02:32:52 +00:00
mumuni-bot	82eae77cc5	Merge pull request 'docs: reflect hwepve removal from Tabiri cluster (5 nodes + standalone London node)' (#48) from fix/hwepve-london-migration into master	2026-08-17 02:24:44 +00: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
kagentz-bot	44f7008302	docs: reflect hwepve removal from Tabiri cluster (5 nodes + standalone London node) ... - Remove hwepve from cluster member lists/diagrams in infrastructure-control, proxmox-monitor, infrastructure-update, litellm-health, mumuni-delegation - CTs 100 (abiba) and 105 (kagentz) moved to minipve; CT 114 (mumuni) no longer exists (Mumuni runs inside Abiba CT 100) - Add standalone London role + NetBird routing peer description for hwepve - Update scripts: agent-health-check.py, pct-run.sh, prose-ai-review.sh - Update disk-gc CT access table, hermes baselines/restore host references	2026-08-15 20:03:02 -04:00
mumuni-bot	a179164f1f	Merge pull request 'Ship: Koby external-agent ruling (fix api_key_env hygiene + docs)' (#46) from ship/koby-external-agent-fix into master ... merge	2026-08-13 00:33:54 +00:00
mumuni-bot	c4626c3512	Merge pull request 'fix: redirect pm2/zulip health-check logging to Gitea, never graph (hard rule)' (#47) from fix/health-logs-not-graph into master ... merge	2026-08-13 00:33:33 +00:00
mumuni-bot	b799d46596	fix: redirect pm2/zulip health-check logging to Gitea, never graph (hard rule) ... - pm2-self-heal.prose.md: description said 'logs every action to the knowledge graph', contradicting its own execution step (line ~60) that says '(not knowledge graph - hard rule)'. Align description to Gitea. - zulip-self-heal.prose.md: Reporting section said 'every cycle produces a knowledge graph node'. Contract is RETIRED; remove graph-node directive. - Both now consistently log to SyslogSolution/health-logs, never the graph.	2026-08-13 00:09:40 +00:00
root	3abf784538	Fix no-mistakes warnings: remove prose from fence, reorder/renumber rules, and add Koby exception to Rule 10	2026-08-11 18:16:12 +00:00
root	d73084d481	Trivial: trigger no-mistakes re-run (all fixes applied)	2026-08-11 18:04:31 +00:00
root	9f0a940cee	Fix no-mistakes warnings: prose out of YAML fence, Rule 16 rename, table cell fix	2026-08-11 18:02:08 +00:00
root	5c3ba31b17	Ship: Koby external-agent ruling (Resolve conflict and merge master)	2026-08-11 17:48:36 +00:00
root	d0144d6db6	Ship: Koby external-agent ruling (fix api_key_env hygiene + docs)	2026-08-11 17:22:25 +00:00
jerome	1d4f6c8ebb	Merge pull request 'Ship: enforcement-rules-reality-fix (captain directive 2026-08-09)' (#45) from ship/enforcement-rules-reality-fix into master ... Reviewed-on: #45	2026-08-10 16:38:05 +00:00
root	38a32f8b32	Ship: enforcement-rules-reality-fix (captain directive 2026-08-09)	2026-08-10 13:28:53 +00:00
jerome	96b0caa0b3	Merge pull request 'Ship: pm2-zulip contract fixes (captain ruling 2026-08-09)' (#44) from ship/pm2-zulip-contract-fixes into master ... Reviewed-on: #44	2026-08-10 01:10:13 +00:00
jerome	ea17f64bb4	Merge pull request 'Ship: monitoring contract fixes (2026-08-09)' (#43) from ship/monitoring-contract-fixes into master ... Reviewed-on: #43	2026-08-10 01:08:07 +00:00
root	c13a15acad	Ship: pm2-zulip contract fixes (captain ruling 2026-08-09)	2026-08-09 22:11:27 +00:00
root	68f9ebff74	Ship: monitoring contract fixes (2026-08-09)	2026-08-09 21:57:44 +00:00
root	93fb0d8e1e	feat(contracts): add MCP URL validation and verify virtual keys on LiteLLM	2026-08-07 21:33:59 +00:00
mumuni-bot	cb6efa81c3	Merge pull request 'fix(contracts): memory-fixer executes decisions to completion (v2.0.0)' (#42) from fix/memory-fixer-execution-v3 into master	2026-08-04 12:32:56 +00:00
mumuni-bot	2dc77ee7da	fix(contracts): memory-fixer executes decisions to completion ... Rewrite memory-fixer to v3 semantics: when Kwame replies to an escalation, execute the action fully - set state (archived/active), clear or rename the [REVIEW:] tag, and bump updated_at so the node exits the stale window and is not re-flagged on the next run. Bump version 1.1.0 -> 2.0.0.	2026-08-04 12:30:37 +00:00
jerome	561c4d98c9	Merge pull request 'fix: correct SearXNG endpoint from dead storepve hostname to live VM109 IP' (#40) from fix/searxng-endpoint into master ... Reviewed-on: #40	2026-08-02 16:20:49 +00:00
root	8f719ca7c7	fix(contracts): Pulse port 3001→7655 (verified), jdownloader decommissioned from docker-vm → CT 118 LXC (.20)	2026-08-01 20:28:50 +00:00
root	c243fcddc3	no-mistakes(document): docs: fix stale SearXNG endpoint in monitoring checks	2026-08-01 15:19:15 +00:00
root	50114f32c0	fix: correct SearXNG endpoint from dead storepve hostname to live VM109 IP (192.168.68.7:8888) ... storepve (192.168.68.6) has no service on :8888. SearXNG runs on VM 109 (docker-vm) at 192.168.68.7:8888 (verified HTTP 200). Aligns with every other contract reference. Missed in PR #39.	2026-08-01 14:56:45 +00:00
jerome	4dc59633b3	Merge pull request 'fix(agent-health): vault token fallback + strix-server service name' (#39) from fix/agent-health-check into master ... Reviewed-on: #39	2026-08-01 14:20:02 +00:00
root	b3193e5e1b	fix(agent-health): 14 stale-reference fixes (Mumuni CT100/.24, Koby .129, Koonimo CT113, wrapper paths)	2026-08-01 14:10:52 +00:00
root	f1490b656e	no-mistakes(document): docs: fix stale ornith refs to strix-server/strix-moe	2026-08-01 13:35:21 +00:00
root	b56501a1cf	no-mistakes(review): Guard infisical-token fallback read against OSError crashes	2026-08-01 13:27:41 +00:00
root	1921937bee	fix(agent-health): vault token fallback + strix-server service name	2026-08-01 13:24:38 +00:00
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