Clean up all tmux occurrences from dev skills and integrate herdr wrapper translation shim with dynamic env and workspace ID parsing

.agents/skills/multi-agent-mux-delegate-job/registry.md

@@ -2,7 +2,7 @@
 
 The registry is the **single source of truth** for delegated work. Job metadata
 (id, prompt, broker, status, timeouts) lives in files, **not** environment
-variables — so one tmux session can handle many jobs sequentially or in
+variables — so one herdr session can handle many jobs sequentially or in
 parallel without collisions, and `publish_event.py` / `job_subscriber.py` can
 reconstruct everything they need from the registry alone.
 
@@ -37,7 +37,7 @@ Reference implementation: [`./scripts/registry.py`](./scripts/registry.py)
   "updated_at": "2026-06-19T09:32:00Z",
   "prompt": "정렬 문제 10개를 만들어 sort_problems.md로 저장…",
   "agent": "claude-code",
-  "agent_session": "tmux:claude",
+  "agent_session": "herdr:claude",
   "broker": {
     "host": "broker.hivemq.com",
     "port": 1883,
@@ -69,7 +69,7 @@ Reference implementation: [`./scripts/registry.py`](./scripts/registry.py)
 
 Every read-modify-write (`register_job`, `pick_pending`, `update_status`,
 `next_seq`) runs inside `registry_lock(registry_dir)`, an exclusive
-`fcntl.flock` over `.lock`. Single-host, good enough for many tmux sessions on
+`fcntl.flock` over `.lock`. Single-host, good enough for many herdr sessions on
 one machine.
 
 ### Production — SQLite WAL
@@ -83,8 +83,8 @@ signatures stay identical; only the storage backend changes.
 
 ## 4. How multiple sessions take only their own work
 
-Each tmux session carries an `agent_session` label (`tmux:claude`,
-`tmux:claude-a`, `tmux:claude-b`, …). `pick_pending(agent_session)`:
+Each herdr session carries an `agent_session` label (`herdr:claude`,
+`herdr:claude-a`, `herdr:claude-b`, …). `pick_pending(agent_session)`:
 
 1. acquires the registry lock,
 2. scans for the **oldest** record with `status == "pending"` **and**
@@ -99,7 +99,7 @@ the job already `running` and moves on.
 
 ```bash
 # session A only ever runs its own pending jobs
-PY scripts/registry.py pick --agent-session tmux:claude-a   # prints id or exits 3
+PY scripts/registry.py pick --agent-session herdr:claude-a   # prints id or exits 3
 ```
 
 ---
@@ -127,12 +127,12 @@ SQLite transaction when you migrate.
 ```bash
 PY=.venv/bin/python
 $PY scripts/registry.py register --prompt "…" --agent claude-code \
-    --agent-session tmux:claude --timeout 3600 --idle-timeout 120   # → prints job_id
+    --agent-session herdr:claude --timeout 3600 --idle-timeout 120   # → prints job_id
 $PY scripts/registry.py list                                       # human table
 $PY scripts/registry.py list --json                                # full records
 $PY scripts/registry.py get    --job <id>                          # one record
 $PY scripts/registry.py status --job <id> --set completed          # set status
-$PY scripts/registry.py pick   --agent-session tmux:claude         # claim → running
+$PY scripts/registry.py pick   --agent-session herdr:claude         # claim → running
 ```
 
 Exit codes: `0` ok, `1` not found / bad status, `3` (`pick`) no pending job for