Fix zulip-monitor.sh LOG variable scope bug

Move LOG, TIMESTAMP, and ISSUES declarations from inside notify() to
script scope so they are available throughout the script.

hermes-config-template.prose.md

@@ -296,6 +296,7 @@ The following MUST be identical across ALL profiles:
 - See `devops-hermes-compression` skill for full reference
 
 ### Rule 10: Default Model Must Be `syslog-auto` (All Agents)
+- **Koby Exception**: Per captain ruling 2026-08-11, Koby is a DeepSeek-primary external agent; its primary model remains `deepseek-v4-flash` (via api.deepseek.com to preserve DeepSeek-specific reasoning, while other sections follow Rule 10.
 - **Hermes agents**: `model.default: syslog-auto`, `custom_providers[0].model: syslog-auto`
 - **pi agents**: `defaultModel: syslog-auto` in `settings.json`, first model in `models.json`
 - `syslog-auto` is the LiteLLM routing model — it load-balances between strix-moe
@@ -423,3 +424,13 @@ curl -s -o /dev/null -w '%{http_code}' -H "Authorization: Bearer $K" http://192.
 5. **Set model choice** — Per agent's workload
 6. **Verify** — curl all shared endpoints, test the model with the new key
 7. **Report** — What was changed, preserved, custom
+### Rule 16: Koby Configuration (DeepSeek-primary)
+(Ref: See Rule 10 for default model behavior, with Koby exception)
+
+Koby uses a split-model architecture:
+
+- Primary Model: `deepseek-v4-flash` via `api.deepseek.com` (for reasoning)
+- Auxiliary Models: `gpu-light` (vision/web_extract) and `syslog-auto` (compression)
+- Key Hygiene: `api_key_env` is strictly `LITELLM_API_KEY` or `DEEPSEEK_API_KEY`
+- Constraint: Do NOT touch Koby's primary model/provider/compression settings unless explicitly ruled by the captain.
+

hermes-key-enforcement.prose.md

@@ -191,7 +191,7 @@ litellm_settings:
 |-------|-----|-----|---------------|------------|--------|-----------------|---------------|
 | Tanko | 112 | .122 | `tanko` | Infisical vault | ✅ Fixed | `infisical run` | 20:17 UTC Jul 5 |
 | Mumuni | 100 (abiba) | .24 | `mumuni` | Infisical vault | ✅ Fixed | Pi Hermes gateway | 2026-07-27 |
-| Koby | 111 | .129 | `koby` | Infisical vault | ✅ Fixed | `infisical run` | 23:30 UTC Jul 5 |
+| Koby | 111 | .129 | `koby` | Infisical vault | ✅ Fixed (DeepSeek-primary) | `infisical run` | 23:30 UTC Jul 5 |
 | Koonimo | 113 | .114 | `koonimo` | Infisical vault | ✅ Fixed | `infisical run` (migrated 2026-07-11) | 2026-08-09 |
 | Abiba | 100 | .65 | `abiba-pi` | Infisical vault | ✅ N/A (pi native) | — | 19:44 UTC Jul 5 |
 | Kagenz0 | 105 | .14 | — | — | ❌ DOWN | — | 19:14 EDT Jul 4 |
@@ -205,7 +205,7 @@ litellm_settings:
 |-------|--------------|-------------|--------|
 | Mumuni | ✅ harness provider | ✅ auxiliary on /v1 (valid) | ✅ Authenticated (verified 2026-08-09) |
 | Tanko | ✅ 5 sections | 0 | ✅ Migrated 2026-08-08, keys 200 |
-| Koby | ✅ custom provider (harness name) | — | ✅ External DeepSeek primary (intentional) |
+| Koby | ✅ custom provider (harness name) | — | ✅ External DeepSeek primary (intentional, captain ruling 2026-08-11) |
 | Koonimo | ✅ .114 (baggy) | — | ✅ 128K context applied 2026-08-09 |
 
 ### Systemd Service Pattern (2026-07-11 — vault migration)

pm2-self-heal.prose.md

@@ -4,7 +4,8 @@ name: pm2-self-heal
 description: >
   Monitors critical PM2 processes (abiba-zulip, abiba-telegram, gitea-runner,
   spoton-service, zulip-watchdog) and auto-restarts any that are stopped or
-  errored. Logs every action to the knowledge graph and alerts the owner via
+  errored. Logs every action to Gitea (SyslogSolution/health-logs — not
+  knowledge graph, hard rule) and alerts the owner via
   Zulip DM on failures.
   CRITICAL: Never restart abiba-zulip — it runs this contract.
   AS-BUILT 2026-08-09 (captain ruling, ecosystem is authoritative):

scripts/zulip-monitor.sh

@@ -9,10 +9,11 @@ ZULIP_EMAIL="abiba-bot@chat.sysloggh.net"
 ZULIP_KEY="cKTDMZAPW08dk3zl05sStzO7HRztzyn8"
 OWNER_ZULIP_ID="9"
 
-# Email config
-GMAIL_USER="jtabiri@gmail.com"
-GMAIL_PASS="rgbuomwcydxwbszd"
-EMAIL_TO="jerome@sysloggh.com"
+
+LOG="/root/zulip-health-monitor.log"
+TIMESTAMP=$(date -u '+%Y-%m-%d %H:%M UTC')
+ISSUES=0
+echo "=== Zulip Health Check — $TIMESTAMP ===" >> "$LOG"
 
 notify() {
   local severity="$1" msg="$2"
@@ -24,30 +25,14 @@ notify() {
   curl -sf -X POST "${ZULIP_SITE}/api/v1/messages" \
     -u "${ZULIP_EMAIL}:${ZULIP_KEY}" \
     -d "${form}" > /dev/null 2>&1 || true
-  
-  # Email alert
-  local subject="${severity} Zulip Monitor Alert"
-  python3 -c "
-import smtplib
-from email.mime.text import MIMEText
-m = MIMEText('''${msg}''')
-m['From'] = 'abiba@sysloggh.com'
-m['To'] = '${EMAIL_TO}'
-m['Subject'] = '${subject}'
-s = smtplib.SMTP('smtp.gmail.com', 587)
-s.starttls()
-s.login('${GMAIL_USER}', '${GMAIL_PASS}')
-s.sendmail('abiba@sysloggh.com', ['${EMAIL_TO}'], m.as_string())
-s.quit()
-" 2>/dev/null || true
+  # Zulip stream post to #agent-hub on topic 'zulip-health'
+  local stream_content="${severity} Zulip Monitor: ${msg}"
+  curl -sf -X POST "${ZULIP_SITE}/api/v1/messages" \
+    -u "${ZULIP_EMAIL}:${ZULIP_KEY}" \
+    -d "type=stream\&to=%5B7%5D\&topic=zulip-health\&content=$(python3 -c "import urllib.parse; print(urllib.parse.quote(str()))")" \
+    > /dev/null 2>&1 || true
 }
 
-TIMESTAMP=$(date -u '+%Y-%m-%d %H:%M UTC')
-ISSUES=0
-LOG="/root/zulip-health-monitor.log"
-
-echo "=== Zulip Health Check — $TIMESTAMP ===" >> "$LOG"
-
 # ── Global: Zulip Server ──
 SERVER_CODE=$(curl -s -o /dev/null -w "%{http_code}" --connect-timeout 10 \
   https://chat.sysloggh.net/api/v1/server_settings \

zulip-health.prose.md

@@ -324,6 +324,7 @@ Track via `/tmp/zulip-monitor-debounce` (unix timestamp of last restart).
    - **Persistent failure threshold**: Only restart after 3 consecutive failed checks (45 min) AND no self-healing in progress
    - **Debounce gate**: Skip all checks entirely if recently restarted
 
+4. **Zulip stream delivery** — Alerts posted to #agent-hub on topic 'zulip-health' (stream_id 7) instead of email, keeping DM to captain for critical (🔴) alerts
 ### Gen 4 (2026-06-29) — Response Pipeline Fix
 
 **Root Cause**: LLM hangs due to GPU saturation (503 QUEUE_TIMEOUT) → pi's `agent_end` never fires → pending Zulip replies accumulate with no timeout. Health endpoint showed `connected: true, stuck: false` while user experienced complete silence.

zulip-self-heal.prose.md

@@ -75,9 +75,8 @@ Track via `/tmp/zulip-heal-debounce-<agent>` (unix timestamp of last restart).
 
 ## Reporting
 
-Every cycle produces a knowledge graph node:
-- Title: `[LEARN] zulip-self-heal: <timestamp>`
-- metadata: { type: "remediation", status: "fixed" | "escalated" | "healthy" }
+This contract is RETIRED — health-check logs are NOT knowledge graph content.
+No graph nodes are created. Logs go to Gitea (SyslogSolution/health-logs).
 - Issues fixed → DM: "🛠 Zulip Self-Heal: fixed <issue>"
 - Issues escalated → DM: "⚠️ Zulip Self-Heal: <issue> needs attention"