What problem does it solve? It determines whether the hermes-agent-setup repository still matches the current stable upstream hermes-agent contract, catching config, provider, auth, or CLI drift that would make the documented GonkaGate setup plan stale or unsafe. ## Core Features & Use Cases - Primary-source auditing: Compares official Hermes docs, GitHub release tags, and tagged source against repository assumptions in README, docs, src, and tests. - Structured verdicts: Classifies findings as confirmed upstream change, confirmed compatible, repo-overstatement, or inferred risk, then returns a compatible, compatible-with-caveats, or incompatible verdict. - Read-only safety: Enforces isolated, non-mutating inspection so audits never touch the user's real ~/.hermes state. - Use Case: Before publishing a new release of the setup helper, run the audit to confirm that the latest hermes-agent stable release still supports the gonkagate custom-provider wiring and .env secret handling the repository documents. ## Quick Start Audit whether this repository is still compatible with the latest stable hermes-agent release and report any breaking upstream changes.