3 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
mumuni-bot	b001b657d4	feat(memory-fixer): v2.1.0 — stale nodes are auto-archived (Kwame directive 2026-09-11) ... - New Level 1 fix 4: archive-suggested stale nodes are archived outright via one updateNode call (description -> '[ARCHIVED] ' + metadata state=archived). The [REVIEW: archive] tag is retired. - Fix 3 now tags refresh-suggested (living) nodes only; those are still escalated. - Corrected the SSH claim: updateNode DOES accept state transitions and bumps updated_at (verified 2026-09-11 archiving 7 nodes: #61 #373 #388 #465 #475 #526 #1476). - Level 2 escalation 1 rescoped to refresh-suggested nodes. - Checks section: any remaining [REVIEW: archive] means fix 4 was skipped.	2026-09-11 12:10:16 +00:00
mumuni-bot	0aa0ea4906	fix: restore agent-health-check AGENTS roster + land missed Tanko-DSH rows ... 2dfc3e1 (PR #50's out-of-band squash) overwrote agent-health-check.py with a version whose AGENTS dict was empty — the health check silently skipped every agent since. Restore the pre-stomp roster verbatim: tanko (runtime: dsh), abiba, koby, koonimo. Also land two Tanko-DSH rows from PR #52 that the earlier merge missed: - hermes-zulip-plugin live-state table (plugin retired on CT112) - zulip-self-heal restart-services table (restart via DSH service, not hermes gateway restart) Mumuni rows from the branch were NOT restored: they carry pre-migration CT100/.24 data, superseded by PRs #54-56 (Mumuni now on kagentz CT105/.14). Closes the reland of PR #52's substance; the stale branch head stays closed.	2026-09-07 07:31:34 +00:00
mumuni-bot	403fbcdd9f	fix: remove duplicated ## Execution block in infrastructure-monitoring ... PR #50's content was squash-merged out-of-band (2dfc3e1, 2026-08-30) while the PR itself stayed open, double-applying the check-health/Execution section. This drops the second copy; keeps one canonical Execution -> check-health -> Phases 1-4 -> Verification Commands flow.	2026-09-07 07:08:49 +00:00