mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-11-06 05:17:15 +00:00
Teknium
ffe2f6411c
When an update had to disable a plugin it also cleared memory.provider, so the memory provider stayed lost even after the plugin was re-enabled, and nothing ever retried the plugin: one transient failure (a TLS proxy, a mirror outage, a since-fixed resolver bug) left it off for good. - The dependency union now honours plugins.disabled for memory.provider the same way the provider loader already does, so eviction no longer has to blank the selection. Re-enabling the plugin brings the provider back. - The eviction is recorded in the home's config under plugins.disabled_by_update (was it enabled, and why). Every later update retries recorded plugins after the enabled ones and undoes exactly the edit once a plugin fits again. - A user's own enable/disable/remove takes the decision back: PM's selection publication forgets the record for the plugin the user settled, and `hermes plugins disable` on an update-disabled plugin now writes that. - Spellings come from the plugin's own manifest instead of a plugin scan of the PM process's home, so a profile's plugins are matched in that profile. - A parked provider is reported, not re-installed: agent init tells the user once why external memory is off (naming the update's reason), and `hermes memory status` and `hermes doctor` show it instead of "plugin not found" or "All checks passed". Doctor lists every update-disabled plugin.