feat: memory plugin for keep

[hughpyle]

Summary

Add a keep external memory provider plugin for Hermes.

This integrates keep-skill (PyPI, GitHub) as a first-class Hermes memory provider, exposes Keep's tool surface (keep_flow, keep_help, keep_prompt).

Small changes in Hermes: makes hermes memory setup handle Keep-specific provider configuration, and passes per-turn user information to memory providers.

What changed

Keep memory plugin

• add a new memory plugin at plugins/memory/keep/
• expose Keep tools through the Hermes memory provider interface

Hermes updates

• make hermes memory setup handle provider choice schemas more reliably
• avoid reporting provider config success when the provider's own config save failed
• pass user_id and user_name to memory providers so that they can provide correct attribution

Why

Keep is a reflective memory system with:

• persistent storage, summarization and document extraction
• structured tagging and relationship edges
• version history and parts analysis
• semantic search and contextual retrieval
• prompt-backed reflection workflows for skill improvement

This plugin lets Hermes use Keep directly as an external memory provider without changes to Hermes core memory-manager behavior.

Manual verification

Tested the Keep setup flow through Hermes:

• run hermes memory setup
• select keep
• confirm Hermes installs keep-skill automatically when needed
• confirm Keep appears as an available provider
• Keep requires an embedding provider and works best with a summarization provider as well. Local Ollama can be automatically detected and bootstrapped, other options generally require provider API keys in the environment. See docs for provider coverage.
• start a new Hermes session
• confirm the agent can call keep_help, review the returned guidance, and use keep_flow / keep_prompt productively (not just exposing the tool names)
• confirm messages are visible in keep --store ~/.hermes/keep list (or appropriate path per profile).

[Daniels77777]

I have been using the Keep and Hermes Agent v0.6.0 for 48 hours -> My existence system keeps getting better results.

[hughpyle]

Updated behavior: Keep wants to build a graph of user/message relationships, so this PR also extends the Hermes per-turn memory interface to pass user_id, user_name where available.

Still benefits from #7789 for full per-turn attribution but doesn't require that.

[hughpyle]

Updated behavior: reverted my user_id changes to the per-turn memory interface, covered by #5895

[hughpyle]

Aligned with upstream.

[kshitijk4poor]

Thanks for the contribution!

Per the updated CONTRIBUTING.md, new memory providers are no longer accepted as in-tree additions to plugins/memory/:

Memory Providers: CLOSED to new in-tree additions
PRs adding to plugins/memory/ will be closed. Publish as standalone plugin into ~/.hermes/plugins/ or via pip entry point. Must implement MemoryProvider ABC (sync_turn, prefetch, shutdown, optional post_setup).

Closing this in line with that policy. The path forward is to publish it as a standalone plugin so users can install it directly without touching the Hermes source tree. Once it's published, a small docs PR adding it to the Community plugins section of the README is welcome.

Sorry for the bump — appreciate the time you put into this.