Adds mnemosyne_remember_media (images, audio, video and documents
become recallable memories) and moves the pinned tree onto the
mnemosyne-hermes 0.7.3 / mnemosyne-memory 4.0.0b3 release pair, which
fixes the provider failing to initialize with 0.7.2.
The Devs-Foundation/mnemosyne entry (created 2026-08-10, last push 2026-08-11, 0 stars) is
unrelated to the Mnemosyne project per its maintainers and registers the same memory-provider
name, which makes memory.provider: mnemosyne ambiguous. It is delisted (plain removal, not the
removed.yaml blocklist: nothing malicious) and welcome back under a distinct name. The official
mnemosyne-oss submission (#113581, wrapper shape validated end to end) takes the bare key.
requires_hermes floor set to the first release that carries #113851 (0.21.4 or later).
README gains the delist-vs-remove distinction and the provider-name collision rule.
Every entry is pinned to the commit reviewed on 2026-09-15 and passed, at that
commit: `hermes plugins validate` (declared tools/hooks/middleware match
registrations, no built-in tool collisions) in both the main venv and a bare
`pip install -e .` venv, `tools.plugin_guard.scan_plugin` with a non-dangerous
verdict, a self-updater grep over every .js file, and a vendor-credential-store
write grep over every .py file. Capabilities and requires_env are copied from
each plugin.yaml; category was assigned by hand.
