3b36a35b86
The previous pin (4474a8d1) declares build-backend
setuptools.backends._legacy:_Backend, which is not importable in any
setuptools release, so uv sync fails before dependency resolution and
the plugin cannot be enabled. d5b4ebf is the upstream fix (one commit
ahead, same version 3.0.1) that switches to setuptools.build_meta.
Fixes #124088
25 lines
1.4 KiB
YAML
25 lines
1.4 KiB
YAML
name: custodian
|
||
repo: https://github.com/indigokarasu/hermes-custodian-plugin
|
||
sha: d5b4ebfd2353a29380a51c8bcba84d4682cf4c91
|
||
version: "3.0.1"
|
||
description: "Autonomous operations monitor for a Hermes install: scans gateway logs, cron jobs, skill journals and agent data directories, classifies findings against a 27-fingerprint registry, auto-repairs Tier 1 problems, escalates the rest, and keeps an append-only issue ledger. Ships /custodian (status, scan, issues, repair, verify, schedule, confidence, init, escalation-runner), four scan/health tools and a grid dashboard. Disclosure — reads gateway logs, cron job state and per-skill journal files under HERMES_HOME to build its findings, and writes repair actions and an issues ledger back there; it performs no network I/O and holds no credentials. Disclosure — /custodian init registers 3 recurring agent cron jobs (deep scan 4×/day, cron-health 4×/day, escalation runner every 30 min on weekdays)."
|
||
maintainer: indigokarasu
|
||
tier: community
|
||
category: automation
|
||
docs_url: https://github.com/indigokarasu/hermes-custodian-plugin#readme
|
||
readme: true
|
||
platforms: []
|
||
capabilities:
|
||
provides_tools:
|
||
- custodian_status
|
||
- custodian_scan
|
||
- custodian_issues
|
||
- custodian_cron_health
|
||
provides_hooks:
|
||
- post_tool_call
|
||
- on_session_end
|
||
- on_session_start
|
||
- on_session_reset
|
||
provides_middleware: []
|
||
requires_env: []
|