simplify Athena runtime and centralize MCP management

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

@@ -16,10 +16,10 @@ Use these paths directly. Do not search the filesystem for alternatives.
 - Host: Unraid `192.168.1.2`
 - Container: `MCPHub`
 - UI/base URL: `http://192.168.1.2:8787`
-- Operational source/build tree: `/mnt/nvme-storage/appdata/MCPHub/build`
+- Operational source/build tree: `/mnt/nvme-storage/appdata/MCPHub/build/repo`
 - Dockerfile: `platform/mcphub/Dockerfile` below that tree
-- Server declaration: `platform/mcphub/configure-settings.py`
-- Client registry: `config/mcp-registry.json`
+- Single server and client registry: `config/mcp-registry.json`
+- Registry renderer: `platform/mcphub/configure-settings.py` (normally unchanged)
 - Unraid template: `config/unraid-templates/my-MCPHub.xml`
 - Persistent state: `/mnt/nvme-storage/appdata/MCPHub`
 - Secrets: `/mnt/nvme-storage/appdata/MCPHub/secrets/<server>.env`, mode `0600`
@@ -91,8 +91,8 @@ Modify only the necessary fixed production files. Rules:
 - Put credentials only in the matching secret file with mode `0600`.
 - Never print, log, commit, summarize, or return a secret.
 - Use `/usr/local/bin/run-with-env` for secret-backed stdio servers.
-- Declare servers in `configure-settings.py`; do not manually treat
-  `mcp_settings.json` as the source of truth.
+- Declare servers only in `config/mcp-registry.json`; do not hard-code a server
+  in `configure-settings.py` and do not edit `mcp_settings.json` manually.
 - Preserve existing users, bearer keys, prompts, resources, enabled states,
   and per-tool toggles.
 - Build a new image tag. Never overwrite the tag currently running.
@@ -104,7 +104,7 @@ unfiltered large server to clients.
 
 ### 5. Deploy without collateral changes
 
-Build from `/mnt/nvme-storage/appdata/MCPHub/build`, then recreate only
+Build from `/mnt/nvme-storage/appdata/MCPHub/build/repo`, then recreate only
 `MCPHub` through Unraid DockerMan so it stays a managed Unraid container.
 Preserve all Appdata and mounts.