Add staged MCP release imports
This commit is contained in:
@@ -4,7 +4,7 @@ description: Operate and extend the Athena AI platform safely.
|
||||
license: MIT
|
||||
metadata:
|
||||
hermes:
|
||||
version: 0.1.0
|
||||
version: 0.2.0
|
||||
author: Michael Roll, Hermes Agent
|
||||
platforms: [linux, macos, windows]
|
||||
tags: [athena, operations, docker, mcp, models, recovery]
|
||||
@@ -86,6 +86,34 @@ repository and use live measurements only as evidence of current state.
|
||||
recovery bundle, then check maintenance status.
|
||||
Completion: source commit, deployed state, docs, and recovery agree.
|
||||
|
||||
## Compact MCP Release Recipe
|
||||
|
||||
Use this route for a new self-written MCP. Do not rediscover the platform file
|
||||
by file.
|
||||
|
||||
1. Inspect Athena once and check the service catalogue so an existing backend
|
||||
is reused rather than duplicated.
|
||||
2. Treat an already reviewed artifact in an approved staging directory as an
|
||||
input. Calculate its SHA once and pass it to `mcp_release.imports`; never
|
||||
reproduce a long staged source file in chat or a `file_update` payload.
|
||||
3. Patch only the actual integration sources: `platform/mcp/compose.yaml`, the
|
||||
managed Hermes config in `platform/hermes/config.yaml`, OpenWebUI's
|
||||
versioned connector sync/seed, the env example, tests and relevant docs.
|
||||
4. Set `hermes_sync: true` when the managed Hermes MCP list changes and
|
||||
`openwebui_sync: true` when OpenWebUI's connector list changes. Neither sync
|
||||
restarts Hermes, Router, Qwen, WireGuard, or the complete stack.
|
||||
5. Do not add a VPN port or edit WireGuard for an ordinary in-stack MCP. Hermes
|
||||
and OpenWebUI use Docker DNS on the private tool network. Add external VPN
|
||||
publication only when the user explicitly asks for access by outside MCP
|
||||
clients.
|
||||
6. One `mcp_release` should import/patch, test, deploy only the named MCP,
|
||||
synchronize clients, publish selected paths and create recovery. Then verify
|
||||
handshake plus one bounded non-writing function.
|
||||
|
||||
A tool-call budget that ends "at a checkpoint" means: report a compact status,
|
||||
then continue the same approved task with a fresh budget. It does not mean
|
||||
abandon the requested implementation after reconnaissance.
|
||||
|
||||
## Persistent Versus Temporary Work
|
||||
|
||||
- "Use" a missing helper for one task: place it in a task-specific temporary
|
||||
|
||||
Reference in New Issue
Block a user