let Hermes manage MCPHub through its API

platform/hermes/install-profiles.sh

@@ -95,7 +95,7 @@ docker run --rm --entrypoint python \
   -v "$HERMES_DATA_DIR:/hermes:rw" \
   -v "$mcphub_registry:/run/input/mcp-registry.json:ro" \
   "${token_mount[@]}" \
-  casaderoll/mcphub:1.2.1 \
+  casaderoll/mcphub:1.2.2 \
   /stack/platform/mcp/sync-clients.py "${sync_args[@]}"
 
 "$STACK_DIR/platform/hermes/install-skills.sh"

platform/hermes/skills/mcphub-deployer/SKILL.md

@@ -77,14 +77,14 @@ docker exec MCPHub python3 /opt/casaderoll/deploy-extension.py stage \
 The helper copies verified files, updates the registry atomically, and always
 stages disabled. It technically blocks activation when the dedicated secret
 or a required key is missing.
-7. Recreate only `MCPHub` once so it reconciles the external registry. Do not
-   restart Hermes, Athena, Router, Qwen, WireGuard, Unraid, or other services.
-8. If credentials are ready, activate with the helper, recreate only MCPHub,
-   then verify: health; all old routes; new handshake; `list_tools` schemas;
-   one bounded read-only call; no test writes or residue. Otherwise stop while
-   disabled.
-9. Run the existing client-sync script only after successful activation. Do
-   not edit client YAML by hand. New routes are not advertised automatically.
+7. The helper registers the disabled server through MCPHub's official API. Do
+   not recreate MCPHub and do not restart Hermes, Athena, Router, Qwen,
+   WireGuard, Unraid, or other services.
+8. If credentials are ready, activate with the helper, then verify: health;
+   all old routes; new handshake; `list_tools` schemas; one bounded read-only
+   call; no test writes or residue. Otherwise stop while disabled.
+9. Ask Hermes to reload MCP connections. Hermes uses MCPHub's aggregate `/mcp`
+   endpoint, so no per-server client config or YAML edit is needed.
 10. Report version, state, tool count, secret path (never values), tests,
     client sync, durable source status, and rollback.