refactor: rename metadata directory .hermes to .mam in backplane scripts and documents

.agents/skills/tmux-agent-orchestrate-delegate-job/SKILL.md

@@ -27,7 +27,7 @@ canonical concrete instance.
 
 The model is deliberately small. A **job** is one delegated task. An **agent**
 is a worker (a claude-code tmux session, a codex run, a human). The **registry**
-(`.hermes/jobs/<id>.json`) holds everything about a job so nothing important
+(`.mam/jobs/<id>.json`) holds everything about a job so nothing important
 lives in environment variables — which means one tmux session can process many
 jobs sequentially, and many sessions can fan out in parallel, with no env
 collisions. The **event channel** is one MQTT topic per job carrying JSON
@@ -83,7 +83,7 @@ tmux-agent-orchestrate-delegate-job submit \
 #          subscriber pid: …
 #          agent launched in tmux session: demo
 #          subscriber output: <one line per event>
-#          /path/to/project/.hermes/delegate_job_logs/<JID>     ← audit log dir
+#          /path/to/project/.mam/delegate_job_logs/<JID>     ← audit log dir
 
 # 2) at any time, query the job or its audit log
 tmux-agent-orchestrate-delegate-job status --job <JID>
@@ -148,9 +148,9 @@ One topic per job: `python/mqtt/jobs/<job_id>/events`. Payload (JSON, UTF-8,
 ## Registry Format
 
 ```
-.hermes/jobs/<id>.json        # metadata record (single source of truth)
-.hermes/jobs/<id>.events.log  # append-only JSON-lines log (debug, optional)
-.hermes/jobs/.lock            # fcntl advisory lock for the registry
+.mam/jobs/<id>.json        # metadata record (single source of truth)
+.mam/jobs/<id>.events.log  # append-only JSON-lines log (debug, optional)
+.mam/jobs/.lock            # fcntl advisory lock for the registry
 ```
 
 The record holds `status`, `prompt`, `agent`, `agent_session`, a `broker` block,
@@ -163,13 +163,13 @@ the atomic rename trick, and multi-session job claiming are in
 ## Audit Logs
 
 Every job's lifecycle is mirrored to a **persistent, append-only audit log**
-under `.hermes/delegate_job_logs/` (override with `DELEGATE_JOB_LOGS_DIR`;
-default `<cwd>/.hermes/delegate_job_logs`). Unlike the registry — live state
+under `.mam/delegate_job_logs/` (override with `DELEGATE_JOB_LOGS_DIR`;
+default `<cwd>/.mam/delegate_job_logs`). Unlike the registry — live state
 mutated in place and liable to be cleaned up — the audit log is durable
 history you can replay after the fact. It is git-ignored.
 
 ```
-.hermes/delegate_job_logs/<job_id>/
+.mam/delegate_job_logs/<job_id>/
   meta.json      # registration snapshot: prompt, agent, broker, timeouts, …
   events.ndjson  # append-only, one JSON event per line, in time order
   status.json    # current status only (fast point-query)
@@ -371,7 +371,7 @@ has been verified (2026-06-21, 6-batch refactoring sprint):
 - [ ] `publisher.py`/`subscriber.py`/`README.md` demo on `python/mqtt/sample`
       still works unchanged (regression).
 - [ ] **audit log integrity** — for a completed job,
-      `.hermes/delegate_job_logs/<JID>/events.ndjson` contains `registered` →
+      `.mam/delegate_job_logs/<JID>/events.ndjson` contains `registered` →
       `received started` → `published completed` (in that order), and
       `status.json.status == "completed"` matches the registry record. A
       logging failure (e.g. read-only log dir) does not break the publish or