18 Commits

Include renames

Author	SHA1	Message	Date
root	1b8186f6b9	no-mistakes(document): docs: reword Tanko .122 SSH dependency claims in zulip-health	2026-09-08 13:00:05 +00:00
root	9dd0cb18d5	no-mistakes(document): docs: align zulip-health tanko snapshot schema to dsh-web probes	2026-09-08 12:49:34 +00:00
root	4684ee64e0	no-mistakes(review): Align zulip-monitor Tanko probe and B2/B3 criteria to dsh-web	2026-09-08 12:10:58 +00:00
root	5313e6b9ba	fix: tanko zulip-health probes via amdpve pct exec (dsh-web loopback :3080 + public-URL fallback)	2026-09-08 10:26:56 +00:00
root	36ae464f59	fix: probe alignment across multiple monitoring contracts ... - infra-monitoring: Added Router+LiteLLM+PVE API probes with expected HTTP codes (200/401/500) - gpu-monitor: Added explicit check-health section with Router+LiteLLM probe commands - proxmox-monitor: Added check-health section for Prometheus/Grafana/exporters (all bound to 0.0.0.0) - zulip-health: Fixed A2A port from :8001 to :50080 and added auth-gated expectation (401) Closes: infra-monitoring-probe-alignment, gpu-monitor-probe-alignment, proxmox-monitor-probe-alignment, zulip-health-probe-alignment	2026-09-08 07:20:41 +00:00
root	2dfc3e1530	Merged PR #50: fix/gpu-dense-docs	2026-08-30 12:16:39 +00:00
root	79af0ae7a3	Merged PR #52: fix/tanko-runtime	2026-08-30 12:16:28 +00:00
mumuni-bot	ca39fead74	fix: correct Mumuni gateway lifecycle path (no sudo on kagentz) + 2 leftover CT100 mentions ... Post-merge verification of PR #54 found: 1. Lifecycle commands in zulip-health/zulip-self-heal used 'sudo systemctl' for hermes-gateway - sudo is NOT installed on kagentz (no sudoers, no polkit user rules). Correct path: root SSH invocation (root@192.168.68.14), matching how the Proxmox host actually manages the unit. 2. hermes-zulip-restore.prose.md line 5 + zulip-resilience-v3 line 423 still said 'Mumuni CT100' in prose - repointed. Found via independent review + live runtime check (whoami, which sudo, journalctl, systemctl show). Refs PR #54, relay #738/#739.	2026-08-30 01:06:30 +00:00
mumuni-bot	e898048baf	fix: repoint Mumuni refs from CT100/.24 to kagentz CT105/.14 post-migration ... Mumuni migrated off Abiba CT100 (192.168.68.24, purged) to dedicated CT kagentz (192.168.68.14) on minipve. Verified live on kagentz: - Gateway: systemd unit hermes-gateway.service (User=hermes), active - Hermes home: /home/hermes/.hermes - gateway_state.json present at ~/.hermes/gateway_state.json Updates Mumuni rows/references in 9 contracts. Abiba-owned refs (.24 pi agent, GPU monitor, infrastructure-control CRITICAL file) and historical runs/ logs intentionally left unchanged. Per relay #738 follow-ups. Refs #735-#738.	2026-08-29 21:41:07 +00: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
root	c13a15acad	Ship: pm2-zulip contract fixes (captain ruling 2026-08-09)	2026-08-09 22:11:27 +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
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
root	5aa93117de	docs: capture all session changes — port conflict, health check, streaming ... Updated contracts to reflect all infrastructure changes made 2026-07-05/06: gpu-fleet.prose.md: - Port conflict detection on all 3 GPU wrappers - Ghost process root cause documented (.8 stale pid 25836) infrastructure-control.prose.md: - Section 7: Agent Health Check (consolidated, non-disruptive) - Disabled scripts documented (zulip-watchdog, zulip-monitor) hermes-agent-baseline.prose.md: - Health verification section + GPU port conflict detection - Change log updated zulip-health.prose.md: - Streaming support section (edit_message + PATCH API)	2026-07-06 02:46:41 +00:00
root	52566ff36e	fix: remove test file, add missing descriptions to zulip-health + memory-audit-maintenance	2026-07-04 23:06:40 +00:00
Abiba	57178e4647	feat(zulip-health): v3 rewrite — full OpenProse responsibility structure ... - kind: contract -> responsibility (valid kind fix) - Add Requires, Maintains (JSON schema), Strategies, Invariants, Continuity - Merge Platform A/B/C into structured Step 1-6 under Execution - Add response_pipeline, queue_healthy, agent_busy_duration diagnostics - Add restart debounce (300s) and PM2 crash-loop safety invariants - Add runtime_contract: 2 versioning	2026-07-02 20:47:17 +00:00
root	8a190fa803	feat(zulip-health): Gen 3 — stuck detection, proactive queue recovery, restart debounce ... - Health endpoint now reports stuck:bool + idle_seconds + last_activity_time - Extension re-registers queue after 30min idle (even without BAD_EVENT_QUEUE_ID) - Broadened queue expiry detection (matches deregistered, invalid queue, etc.) - zulip-monitor.sh detects stuck:true + enforces 300s restart debounce - Prevents silent death where bot shows connected:true but processes 0 messages Fixes the 'getting stuck and restarts once and for all' issue.	2026-06-28 13:22:11 +00:00
root	c59afa7f1a	feat(zulip-health): v2 — multi-platform monitor for pi, Hermes, Agent Zero ... Covers all 4 Zulip agents across 3 platforms with checks, auto-heal, and consolidated action matrix.	2026-06-27 19:22:44 +00:00