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.

hermes-config-template.prose.md

@@ -296,7 +296,6 @@ 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
@@ -424,13 +423,3 @@ 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 (DeepSeek-primary) | `infisical run` | 23:30 UTC Jul 5 |
+| Koby | 111 | .129 | `koby` | Infisical vault | ✅ Fixed | `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, captain ruling 2026-08-11) |
+| Koby | ✅ custom provider (harness name) | — | ✅ External DeepSeek primary (intentional) |
 | 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):

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:
+This contract is RETIRED — health-check logs are NOT knowledge graph content.
-- Title: `[LEARN] zulip-self-heal: <timestamp>`
+No graph nodes are created. Logs go to Gitea (SyslogSolution/health-logs).
-- metadata: { type: "remediation", status: "fixed" | "escalated" | "healthy" }
 - Issues fixed → DM: "🛠 Zulip Self-Heal: fixed <issue>"
 - Issues escalated → DM: "⚠️ Zulip Self-Heal: <issue> needs attention"