phase 3-4: get_execution_status tool, approval creation, delete bin/ + homelab.go, update AGENTS.md

AGENTS.md

@@ -105,16 +105,16 @@ historical reference.
 
 ## 5. Acting on the homelab
 
-- **Read state**: prefer MCP tools, then files, then shell. Examples:
-  `homelab whoami`, `homelab list`, `homelab status`, `homelab logs caddy`.
-- **Cross-host actions** (caddy reload, pct exec, etc.): use the `homelab`
-  CLI — it resolves hostname → mesh address → ssh / pct path for you.
-- **Secrets**: never hardcode. Call `homelab secret <name>` to decrypt on
-  demand using the per-client age key at `/etc/age/key.txt`.
-- **Mutations** (restart, edit configs, etc.): classify against
-  `seeds/policy.yaml` first (`homelab decide <action> <entity>`).
-  `reversible_low` actions just need the interactive confirmation prompt;
-  `config_mutation`/`destructive` actions are mechanically refused without
+- **Read state**: use MCP tools. Hermes (the AI agent) is the primary
+  operator interface — it has 21 MCP tools for observe/orient/decide/act.
+- **Actions** (restart, logs, apt, pct exec): Hermes calls `request_execution`
+  via MCP. `reversible_low` actions execute immediately; `config_mutation`
+  and `destructive` actions are queued for operator approval via Matrix.
+- **Secrets**: managed by Infisical (`oikos secret` subcommand for migration).
+  Never hardcode secrets — use env vars from `.env`.
+- **Mutations** (restart, edit configs, etc.): classified against
+  `seeds/policy.yaml`. `reversible_low` actions auto-execute;
+  `config_mutation`/`destructive` actions require approval.
   a valid `--approval-id` from `homelab approval request` — see OIKOS.md.
 
 ## 6. Communication mode