Simplify Athena stack and recovery

platform/hermes/skills/athena-operator/SKILL.md

@@ -4,22 +4,22 @@ description: Understand, operate and extend the Athena AI host.
 license: MIT
 metadata:
   hermes:
-    version: 1.0.0
+    version: 2.0.0
     author: Michael Roll
     platforms: [linux]
-    tags: [athena, docker, mcp, models, recovery]
+    tags: [athena, docker, mcp, models, backup]
 ---
 
 # Athena Operator
 
 Use this skill for work on Athena itself: Docker, MCPs, models, profiles,
-Hermes, OpenWebUI, TTS, STT, image generation, Git and recovery.
+Hermes, OpenWebUI, TTS, STT, image generation, Git and backups.
 
 ## Start
 
-1. Read `ATHENA.md` through Athena Platform Context. It is the normal source
-   of architectural truth.
-2. Call `athena_operator_inspect` once for the affected area.
+1. Call `athena_operator_inspect` with `subject=guide`; it returns the current
+   `ATHENA.md` as the architectural truth.
+2. Inspect the affected live area only if needed.
 3. Search for the concrete source file, then read only the required lines.
 
 Do not rediscover the complete platform for every task. Do not read entire
@@ -32,8 +32,9 @@ apply the smallest durable change. The operator owns the Git worktree and
 deployment access; do not clone another repository or request another SSH key.
 
 Afterwards run focused checks, verify the affected service, commit and push.
-Create a recovery kit after the complete change works, not after every
-intermediate edit.
+The scheduled Docker-data backup is automatic. After storage-affecting work,
+run one manual backup and verify its archive instead of building a special
+recovery kit.
 
 For a new MCP, normally change only its server code, Dockerfile, MCP Compose
 service, env example, client registration and a focused test. Reuse an existing
@@ -47,7 +48,7 @@ backend instead of installing a duplicate service.
 - Prefer specialist MCPs for Home Assistant, Unraid, ARR, Navidrome and other
   external systems.
 - A healthy container is not proof; perform one bounded functional check.
-- Never claim a write, deploy, commit, push or recovery succeeded without its
+- Never claim a write, deploy, commit, push or backup succeeded without its
   actual result.
 
 ## Remote-host boundary