Add compact Athena MCP release workflow
This commit is contained in:
@@ -65,7 +65,9 @@ repository and use live measurements only as evidence of current state.
|
||||
5. **Change the source of truth.** Modify repository sources, not only a live
|
||||
container. Prefer `athena_operator_prepare`; show its full preview and stop
|
||||
for the exact user confirmation before `athena_operator_execute`.
|
||||
Use `file_update` for the exact source paths. Never clone the repository in
|
||||
Prefer `patch_update` with a small unified diff and the current file SHA for
|
||||
ordinary edits. Use `file_update` only for new files or intentional complete
|
||||
replacements. Never clone the repository in
|
||||
the Hermes sandbox and never request or copy an SSH key; the Operator owns
|
||||
the canonical worktree and its deploy credentials.
|
||||
Completion: the approved ticket matches the intended content.
|
||||
@@ -75,7 +77,11 @@ repository and use live measurements only as evidence of current state.
|
||||
7. **Verify behavior.** Run syntax/config checks, focused tests, service health,
|
||||
and one bounded functional test. A running container alone is not proof.
|
||||
Completion: expected behavior and rollback path are both verified.
|
||||
8. **Close the maintenance loop.** Update relevant docs, publish only the
|
||||
8. **Close the maintenance loop.** For a normal MCP delivery, prefer one
|
||||
confirmed `mcp_release`; it applies the reviewed patches, runs checks,
|
||||
deploys only named services, synchronizes OpenWebUI, publishes selected
|
||||
paths and creates recovery. Use separate operations only for diagnosis or a
|
||||
deliberately partial workflow. Otherwise update relevant docs, publish only the
|
||||
explicitly selected changed paths with `git_publish`, create a newer
|
||||
recovery bundle, then check maintenance status.
|
||||
Completion: source commit, deployed state, docs, and recovery agree.
|
||||
@@ -106,8 +112,9 @@ repository and use live measurements only as evidence of current state.
|
||||
- A profile switch can terminate active generation and invalidate prompt cache.
|
||||
- A healthy container can still expose the wrong model, route, or tool set.
|
||||
- `/opt/mike-ai/stack` is deployed source, not automatically the canonical Git
|
||||
worktree. Complete durable changes through Operator operations `file_update`,
|
||||
`run_checks`, `compose_deploy`, `git_publish`, and `recovery`.
|
||||
worktree. Use `patch_update` for compact edits and `mcp_release` for the
|
||||
complete MCP lifecycle. Do not reconstruct whole Compose or installer files
|
||||
for a small change.
|
||||
- New skills are loaded at the next Hermes session; absence in the current
|
||||
session is expected.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user