feat(agents): add Hermes ACP runtime - #17
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Temporarily closing and reopening this draft to trigger the newly enabled canonical CI workflows; source head remains unchanged. |
|
This pre-reset staging PR is closed as superseded by merged upstream-first reset PR #37 and the current thin-adapter tracker #1/#36. No code is being deleted. The branch and review history remain available. Retained behavior was replayed narrowly in #37; dropped managed brokers, blanket guards, duplicate UI, and control-signed routine collaboration must not be revived from this PR. |
Summary
hermesandhermes-acp, launching them with command-specific ACP argumentshermes acp --checkas dependency readiness only, with no Hermes command-level authentication probeTruth boundary
hermes acp --checkcan mark the runtime dependency surface ready or in need of setup. It never produceslogged_in. Hermes provider authentication remains owned by Hermes and is discovered only when the ACP runtime is launched.Focused validation
cargo test --manifest-path desktop/src-tauri/Cargo.toml hermes --lib -- --test-threads=1cargo clippy --manifest-path desktop/src-tauri/Cargo.toml --lib -- -D warningscargo fmt --manifest-path desktop/src-tauri/Cargo.toml -- --checkcd desktop && pnpm run typecheckcd desktop && pnpm check:file-sizesScope
Generic upstream candidate only. No Electric Sheep, evaOS, Supabase, customer VM, or managed-business behavior.
Closes #2