hermes - 💡(How to fix) Fix Add Hermes agent-readiness sentinel inspired by Cursor agent-compatibility

Motivation

Cursor's agent-compatibility plugin is a strong pattern for coding operations: one deterministic scan plus focused startup, validation-loop, and docs-reliability reviews, then a single prioritized fix list.

Hermes already has repo sentinels, AGENTS.md conventions, cron, Kanban, and coding skills. The compatible adaptation is not to install Cursor plugin runtime files, but to add a Hermes-native agent-readiness sentinel that can run against active repos and open actionable hygiene issues.

Proposed Hermes adaptation

Add a small hermes coding readiness / script-driven sentinel that scores and reports:

• Deterministic repo signals: AGENTS.md/runbook presence, package manager lockfiles, test/lint commands, CI workflows, setup docs, env examples, task scripts, non-interactive CLI paths.
• Startup compatibility: can a fresh agent discover setup and boot/test the repo without guesswork?
• Validation loop: can a small no-op or targeted change be verified quickly without full-suite-only friction?
• Docs reliability: do documented commands match reality?

Output should be compact and actionable:

## Hermes Agent Readiness Score: N/100

Top fixes
- <highest leverage repo fix>
- <next fix>

Acceptance criteria

• Non-destructive command can run locally against a repo path and emit markdown/json.
• Scanner is heuristic and does not block normal coding workflows.
• Coding ops cron can call it for active repos and update /root/.hermes/coding-ops/dashboard.md or open issues only for real fixable gaps.
• Documentation explains that this is inspired by Cursor plugin patterns but implemented as Hermes-native tooling.

Source pattern reviewed

• cursor/plugins/agent-compatibility at d1cdb88
• Key idea: blend deterministic scan + focused behavioral reviews, hide internal score math by default, output only the prioritized top fixes.