Health check logs (LITELLM-HEALTH, GPU-SELF-HEAL, PM2) no longer create nodes in the shared knowledge graph. They are now pushed to SyslogSolution/health-logs — versioned, searchable, and retention-managed via Gitea.
Hard rule: Logs NEVER go into RA-H OS knowledge graph.
Health check logs (LITELLM-HEALTH, GPU-SELF-HEAL, PM2) no longer create nodes in the shared knowledge graph. They are now pushed to `SyslogSolution/health-logs` — versioned, searchable, and retention-managed via Gitea.
**Updated contracts:**
- `litellm-self-heal.prose.md` — Phase 4: kg-logger → gitea-logger
- `gpu-self-heal.prose.md` — Reporting: graph node → Gitea path
- `pm2-self-heal.prose.md` — Log step: LEARN node → Gitea file
**Hard rule:** Logs NEVER go into RA-H OS knowledge graph.
Logs (LITELLM-HEALTH, GPU-SELF-HEAL, PM2) now pushed to SyslogSolution/health-logs
instead of creating orphan nodes in the shared knowledge graph.
- litellm-self-heal: Phase 4 now calls gitea-logger instead of kg-logger
- gpu-self-heal: Reporting section updated to Gitea path
- pm2-self-heal: Log step redirected to Gitea
- 271 existing orphan nodes remain in graph (no delete tool available)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Health check logs (LITELLM-HEALTH, GPU-SELF-HEAL, PM2) no longer create nodes in the shared knowledge graph. They are now pushed to
SyslogSolution/health-logs— versioned, searchable, and retention-managed via Gitea.Updated contracts:
litellm-self-heal.prose.md— Phase 4: kg-logger → gitea-loggergpu-self-heal.prose.md— Reporting: graph node → Gitea pathpm2-self-heal.prose.md— Log step: LEARN node → Gitea fileHard rule: Logs NEVER go into RA-H OS knowledge graph.