feat(hermes): map task-loop as pending (intended auto/mcp)

task-loop orchestrates the projects-meta board cycle (tasks_claim_next /
tasks_close / tasks_update / tasks_heartbeat) and may arm a long ScheduleWakeup —
critical-infra-adjacent, so it lands in the behavioral-audit pending tier, not auto.
Promotion to auto gated on task-loop-test-trigger. Schema version untouched.

Closes [task-loop-hermes-mapping] (baseline 2/3).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

hermes/mapping.yaml

@@ -138,7 +138,7 @@ skills:
     mode: skip
     reason: "Claude-Code-only orchestrator — Hermes uses hermes-installer-skill instead."
 
-  # ─── pending (6 — behavioral audit required) ─────────────────────────
+  # ─── pending (7 — behavioral audit required) ─────────────────────────
 
   delegate-task:
     mode: pending
@@ -181,3 +181,10 @@ skills:
       mode: auto
       category: software-development
     reason: "Steps shell out to git / gh / Gitea-API, handle tokens, force-push, and repo deletion/privacy toggles — not a purely stylistic skill. Behavioral audit via private-dev-public-publish-test-trigger required before promotion to auto."
+
+  task-loop:
+    mode: pending
+    intended:
+      mode: auto
+      category: mcp
+    reason: "Orchestrates the board claim/close/update/heartbeat cycle via mcp__projects-meta__tasks_claim_next / tasks_close / tasks_update / tasks_heartbeat (cross-session claim ownership, irreversible close, Gitea side-effects) and may arm a single long ScheduleWakeup for the explicit long-watch opt-in. Critical-infra-adjacent — touches the same claim/close machinery the unattended poller relies on. Behavioral audit via task-loop-test-trigger required before promotion to auto."