SyslogSolution/prose-contracts
7
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

fix: correct tanko runtime to DSH across contracts & scripts #52

Closed
mumuni-bot wants to merge 2 commits from fix/tanko-runtime into master
pull from: fix/tanko-runtime
merge into: :master
Conversation 1 Commits 2 Files Changed 18
+89 -80
mumuni-bot commented 2026-08-27 03:00:47 +00:00
Owner
Copy Link
Copy Source

Summary

Tanko migrated from Hermes to DSH (DeepSeek Harness) on 2026-08-27. This PR corrects every record in prose-contracts that described tanko as a Hermes agent or Hermes runtime, so the self-healing homelab's guiding documents are accurate.

Facts preserved (unchanged): Tanko = CT 112, IP 192.168.68.122, LiteLLM alias tanko, SSH user jerome, Infisical vault-backed.

Changes by file

Identity / runtime corrections

  • infrastructure-control.prose.md — CT 112 platform: Hermes agent → DSH (DeepSeek Harness) agent
  • hermes-agent-baseline.prose.md — Agent Map platform → DSH; excluded from "For Hermes Agents" config section
  • hermes-config-template.prose.md — tanko removed from agents_configured; key alias corrected tanko-* → tanko; host shown as CT 112 (.122)
  • memory-audit-maintenance.prose.md — tanko removed from Hermes roster (uses DSH-native memory)
  • build-zulip-plugin.prose.md — tanko excluded (no longer uses Hermes Zulip plugin)
  • hermes-zulip-plugin.prose.md / hermes-zulip-restore.prose.md — tanko excluded from target; rows marked historical
  • zulip-health.prose.md — Platform B now "Tanko (DSH) & Mumuni (Hermes)"; schema platform hermes→dsh; gateway/heartbeat probes scoped to Mumuni
  • zulip-self-heal.prose.md, zulip-mention-reliability.prose.md, pi-approval-architecture.prose.md — "Hermes agents (Tanko, Mumuni)" → "agents (Mumuni on Hermes, Tanko on DSH)"
  • infrastructure-maintenance.prose.md — Hermes-gateway check no longer probes tanko CT 112

Operational scripts (stop false alarms on retired Hermes gateway)

  • scripts/daily-infra-report.py — fixed CT-ID regression (CT 122 → CT 112); tanko reported as platform: dsh, no longer reads ~/.hermes/gateway_state.json
  • scripts/zulip-monitor.sh — tanko probe skipped (DSH, no Hermes gateway since 2026-08-27)
  • scripts/agent-health-check.py — tanko gets runtime: dsh, skips Hermes gateway/state/streaming/journal checks
  • scripts/prose-auth-check.sh + AGENTS.md — authorize tanko/tanko-bot for the restricted files it owns/maintains

Docs

  • README.md — safe-mutate note: tanko on DSH but enforcement still applies

Left intact (history): dated incident logs (zulip-resilience-v3 2026-07-18), migration records (litellm-api-keys, hermes-key-enforcement), runs/ outputs.

Verification

  • scripts/prose-lint.sh ✅ PASS
  • Frontmatter validation ✅ PASS
  • prose-auth-check.sh (author tanko-bot) ✅ PASS for all changed restricted files
  • python3 -m py_compile on edited scripts ✅
  • bash -n on edited shell scripts ✅
## Summary Tanko migrated from **Hermes** to **DSH (DeepSeek Harness)** on 2026-08-27. This PR corrects **every record** in prose-contracts that described tanko as a Hermes agent or Hermes runtime, so the self-healing homelab's guiding documents are accurate. **Facts preserved (unchanged):** Tanko = CT 112, IP 192.168.68.122, LiteLLM alias `tanko`, SSH user `jerome`, Infisical vault-backed. ## Changes by file ### Identity / runtime corrections - `infrastructure-control.prose.md` — CT 112 platform: `Hermes agent` → `DSH (DeepSeek Harness) agent` - `hermes-agent-baseline.prose.md` — Agent Map platform → **DSH**; excluded from "For Hermes Agents" config section - `hermes-config-template.prose.md` — tanko removed from `agents_configured`; key alias corrected `tanko-*` → `tanko`; host shown as CT 112 (.122) - `memory-audit-maintenance.prose.md` — tanko removed from Hermes roster (uses DSH-native memory) - `build-zulip-plugin.prose.md` — tanko excluded (no longer uses Hermes Zulip plugin) - `hermes-zulip-plugin.prose.md` / `hermes-zulip-restore.prose.md` — tanko excluded from `target`; rows marked historical - `zulip-health.prose.md` — Platform B now "Tanko (DSH) & Mumuni (Hermes)"; schema platform `hermes`→`dsh`; gateway/heartbeat probes scoped to Mumuni - `zulip-self-heal.prose.md`, `zulip-mention-reliability.prose.md`, `pi-approval-architecture.prose.md` — "Hermes agents (Tanko, Mumuni)" → "agents (Mumuni on Hermes, Tanko on DSH)" - `infrastructure-maintenance.prose.md` — Hermes-gateway check no longer probes tanko CT 112 ### Operational scripts (stop false alarms on retired Hermes gateway) - `scripts/daily-infra-report.py` — **fixed CT-ID regression (CT 122 → CT 112)**; tanko reported as `platform: dsh`, no longer reads `~/.hermes/gateway_state.json` - `scripts/zulip-monitor.sh` — tanko probe skipped (DSH, no Hermes gateway since 2026-08-27) - `scripts/agent-health-check.py` — tanko gets `runtime: dsh`, skips Hermes gateway/state/streaming/journal checks - `scripts/prose-auth-check.sh` + `AGENTS.md` — authorize `tanko`/`tanko-bot` for the restricted files it owns/maintains ### Docs - `README.md` — safe-mutate note: tanko on DSH but enforcement still applies **Left intact (history):** dated incident logs (`zulip-resilience-v3` 2026-07-18), migration records (`litellm-api-keys`, `hermes-key-enforcement`), `runs/` outputs. ## Verification - `scripts/prose-lint.sh` ✅ PASS - Frontmatter validation ✅ PASS - `prose-auth-check.sh` (author tanko-bot) ✅ PASS for all changed restricted files - `python3 -m py_compile` on edited scripts ✅ - `bash -n` on edited shell scripts ✅
mumuni-bot added 1 commit 2026-08-27 03:01:33 +00:00
fix: correct tanko runtime to DSH across contracts & scripts
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 4s
Details
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 1s
Details
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 1s
Details
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 1s
Details
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 1s
Details
c23462eba8 
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.
mumuni-bot force-pushed fix/tanko-runtime from 0d5064f49d to c23462eba8 2026-08-27 03:01:33 +00:00 Compare
mumuni-bot added 1 commit 2026-08-27 03:07:09 +00:00
fix: skip Hermes config/wrapper integrity checks for tanko (DSH)
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 3s
Details
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 3s
Details
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 2s
Details
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 3s
Details
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 0s
Details
aa2451e8ae 
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.
mumuni-bot commented 2026-09-07 07:34:35 +00:00
Author
Owner
Copy Link
Copy Source

Closing: substance relanded via PR #60 (merged, all CI green) on top of current master — AGENTS roster in agent-health-check.py restored (lost when 2dfc3e1 stomped the file) + two missed Tanko-DSH rows. The branch head itself was too stale to merge (would revert PRs #53-58); Mumuni rows from it were superseded by #54-56. @tanko runs on DSH per captain confirmation — contracts now consistent across master.

Closing: substance relanded via PR #60 (merged, all CI green) on top of current master — AGENTS roster in agent-health-check.py restored (lost when 2dfc3e1 stomped the file) + two missed Tanko-DSH rows. The branch head itself was too stale to merge (would revert PRs #53-58); Mumuni rows from it were superseded by #54-56. @tanko runs on DSH per captain confirmation — contracts now consistent across master.
mumuni-bot closed this pull request 2026-09-07 07:51:01 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
abiba-bot jerome (Jerome Kwame Tabiri) kagentz-bot kwame (Kwame Tabiri) mumuni-bot (Mumuni 🦅 (Syslog Falcon)) tanko-bot theo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SyslogSolution/prose-contracts#52