meta(hermes): register session-handoff (mode: pending, intended: auto/productivity)

Without an entry, scripts/build-hermes.py fails ("unmapped skill" — every
skill in skills/ must appear in mapping exactly once). Registered under
the pending block alongside using-yt-tools and using-vds-ops because the
skill has bidirectional file-system side effects (read/write
.tasks/NEXT_SESSION.md) and warrants a behavioral audit before promotion.

intended.category = productivity (mirrors using-tasks/setup-tasks —
workflow-state continuity primitive, not engineering toolchain).

Build now reports 28 skills (14 auto / 2 manual / 9 skip / 3 pending).
SKIPPED.md gains an entry under "Pending" with the intended block
preserved across MVP iterations.

Closes [session-handoff-hermes-mapping].
Promotion to mode: auto deferred to a separate post-audit task.

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

.tasks/STATUS.md

@@ -1,5 +1,5 @@
 # Task Board
-_Updated: 2026-05-24 (session-handoff кластер: install + bootstrap-template-extend 🟢; project-bootstrap 1.11→1.12.)_
+_Updated: 2026-05-24 (session-handoff: install + bootstrap-template-extend + hermes-mapping 🟢; 3 из 7 кластера закрыто.)_
 
 <!--
   Canonical layout. One block per task. Per-task deep context lives in
@@ -1353,21 +1353,18 @@ Findings — отдельные follow-up tasks (`using-vds-ops-<gap>-fix` ил
 
 ---
 
-## ⚪ [session-handoff-hermes-mapping] — Добавить запись для session-handoff в ~/projects/claude-skills/hermes/mapping.yaml в режиме `pending` (не auto).
+## 🟢 [session-handoff-hermes-mapping] — Добавить запись для session-handoff в ~/projects/claude-skills/hermes/mapping.yaml в режиме `pending` (не auto).
 
 **Reason для pending mode:** скил трогает file-system (write/overwrite .tasks/NEXT_SESSION.md, append .wiki/log.md), не чисто стилевой / response-style. Требует отдельного аудита перед auto-режимом.
 
 **Прецедент:** pulling-before-work — ближайший по структуре (тоже trigger-line в CLAUDE.md, тоже file-system effect, тоже single-direction раньше — pull only; session-handoff bidirectional read/write).
 
-**Status:** ready
-**Where I stopped:** (not started)
-**Next action:** 1. Открыть ~/projects/claude-skills/hermes/mapping.yaml.
-2. Добавить блок session-handoff по образцу pulling-before-work (ближайший прецедент).
-3. Mode: pending.
-4. Запустить build-hermes.py.
-5. Закоммитить с semver-bump в commit message (per project-discipline rule 3) — это правка hermes mapping, потенциально MINOR в зависимости от семвер-политики claude-skills.
-**Branch:** n/a
+**Status:** done
+**Where I stopped:** done
+**Closed by:** Прецедент уточнён: `pulling-before-work` ныне `mode: auto` (не pending) — настоящий ближайший прецедент для pending — `using-yt-tools` и `using-vds-ops` (file-system + tool-side-effects, ждут behavioral audit'а). Entry для `session-handoff` добавлен в `hermes/mapping.yaml:160-166` с `mode: pending`, `intended: { mode: auto, category: productivity }`, reason про bidirectional file-system side-effect. Comment header bumped "(1)" → "(3)" (now using-yt-tools + using-vds-ops + session-handoff). Category = **productivity** (не software-development) — ближе к using-tasks/setup-tasks (workflow-state continuity), не engineering toolchain. `python scripts\build-hermes.py` → 28 skills (был 27): 14 auto / 2 manual / 9 skip / **3 pending**. SKIPPED.md содержит entry под "Pending (deferred to follow-up tasks)" с full intended-block. No semver-bump — `claude-skills` repo не имеет top-level версии, hermes mapping — meta-config, не versioned artifact (precedent: using-yt-tools-hermes-mapping closure note также без bump'а).
+**Branch:** master
 <!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-05-24T18:20:32.363Z -->
+<!-- closed-by: vitya@DESKTOP-NSEF0UK / 2026-05-24 / acceptance: entry registered ✓; build exit 0 ✓; SKIPPED.md pending block ✓; intended block preserved ✓ -->
 
 ---