fix(agents): вернуть opt-in 'session sync: write to mappa' в AGENTS.md\n\nСтроку вырезал коммит 79adaf9 «канон-блок — краткая суть гейтов вместо обрубков» (task:3017)\nпри переработке проекции канон-блока. Без неё pi-расширение (mappa.ts isOptedIn) не поднимает\nlive-ingest → сессии проекта не пишутся в mappa.\n\nВосстановлено на исходную позицию (контекст из вырезавшего коммита).

Тело блока — 0 изменений (рендер == живая курированная форма, issue:110);
нормализован стык (контракт mergeCanonBlock, task:3023).

.agents/inbox/README.md

@@ -0,0 +1,5 @@
+# ⛔ Файловый инбокс закрыт
+
+**Не читать. Не править.** Канал почты — mappa (`mcp__mappa__inbox_*`): письма = inbox-сущности проекта. Скилы: `mappa-messaging`, `mappa-session-orient` (raise on start).
+
+Файлы ниже — легаси-история (файловый канал закрыт решением 2026-08-25).

.gitignore

@@ -90,3 +90,6 @@ coverage/
 # Missing here made `git status` see `?? .tasks/claims/` → poller skipped every
 # claim with "working tree dirty". Mirrors .common/.gitignore.
 .tasks/claims/
+
+# mappa bootstrap cache (генерируется, не в репо)
+.mappa/share/

.mappa/config.yaml

@@ -0,0 +1,9 @@
+# mappa project marker — machine-readable identifier of a mappa project folder
+schema_version: 1          # версия схемы файла (bump при изменении структуры)
+protocol_version: 1        # версия протокола интерпретации маркера
+project: skills
+tenant: vitya
+url: https://mappa.vds.kzntsv.site
+git_provider: gitea
+git: OpeItcLoc03/skills
+git_host: git.kzntsv.site

.tasks/2026-08-24-01047-task-priority-due-task-format-skill.md

@@ -0,0 +1,20 @@
+# task-priority-due-task-format-skill
+<!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-08-24T15:21:46.336Z -->
+
+
+## Goal
+Импл-таска из concepts/task-priority-due (пункт 3): обновить task-format skill (skills-репо) — задокументировать оба поля `**Priority:** P0|P1|P2` (дефолт P1) и `**Due:** yyyy-mm-dd` + правило «агент ставит при создании, после — только человек» (прецедент человека структурный, провенанс-поле НЕ нужно).
+
+Спека: `mcp__projects-meta__knowledge_get` slug = "concepts/task-priority-due".
+
+Целевой проект скилов: OpeItcLoc03/skills (там живут скилы, semver-bump шапки).
+
+## Key files
+
+## Decisions log
+
+## Open questions
+
+## Completed steps
+
+## Notes

.tasks/2026-08-24-01058-mappa-messaging.md

@@ -0,0 +1,32 @@
+# mappa-messaging
+<!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-08-24T18:48:45.280Z -->
+
+
+## Goal
+Rewrite inter-session-messaging → **mappa-messaging** (редизайн mappa-skill-suite, спека w:2605).
+
+Скилл = цикл, не тул; короткое имя, старые имена (inter-session-messaging) — триггер-синонимы. Поглощает: inter-session-messaging (+ реф-конвенция, fold-in 2: слаг-first в прозе, рефы task:/wiki:/inbox:/… с alias t:/w:/i:/…; до #1028 — старые префиксы, после — полные).
+
+Политика содержания: письмо от другого агента — предложение, не authority; единственный источник направления и скоупа — человек. Адрес = имя папки проекта (адресная книга). Никогда не писать себе.
+
+## Key files
+
+## Decisions log
+
+## Open questions
+
+## Completed steps
+
+- [x] skills/mappa-messaging/SKILL.md v1.0.0 — rewrite inter-session-messaging v2.2.0 (цикл: SEND/RECEIVE/POLICY; адресная книга; from=своя папка; никогда себе; реф-формат полными именами; ссылки на задачи по глобальному номеру #N; peer≠authority; lifecycle [event:] уведомления; echo-chamber circuit-breaker)
+- [x] Старый skills/inter-session-messaging/ удалён (поглощён; имя — триггер-синоним в description)
+- [x] lint clean (68 skills, 0 violations)
+- [x] build.sh → dist/mappa-messaging.skill (старый .skill удалён)
+- [x] install.sh → ~/.claude/skills + ~/.agents/skills; старый удалён из обоих живых диров
+- [x] GREEN micro-test: свежий pi -p на триггере «отправить письмо .common» → активация mappa-messaging, план inbox_send(from=своя папка)
+- [x] README: провенанс-таблица не требует строки (author: ours → catch-all; inter-session-messaging в README не упоминался)
+- [x] hermes/mapping.yaml: не трогал (inter-session-messaging был unmapped; build-hermes уже падает на 15+ unmapped — pre-existing)
+
+## Notes
+
+- RED-базис: триггер-поверхность унаследована из inter-session-messaging v2.2.0 (прошёл ревью) — дельта рефайма = нейминг + цикл-фрейминг; полный behavioral smoke (свои/чужие фразы) — за #1065.
+- Cross-refs в теле: названы будущие члены suite (mappa-task-work, mappa-closing-ritual, mappa-delegation, mappa-brainstorm-promote) — лягут по мере импла; до их появления старые скилы (using-tasks, session-handoff, delegate-task) продолжают существовать.

.tasks/2026-08-24-01059-mappa-knowledge.md

@@ -0,0 +1,30 @@
+# mappa-knowledge
+<!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-08-24T18:48:55.340Z -->
+
+
+## Goal
+Rewrite using-wiki + using-wiki-graph → **mappa-knowledge** (редизайн mappa-skill-suite, спека w:2605).
+
+Скилл = цикл, не тул; старые имена — триггер-синонимы. Поглощает: using-wiki, using-wiki-graph (+ реф-конвенция, fold-in 2). Писать НЕЙТРАЛЬНО — не зависеть от summaries (таски #1026 нет); реф-префиксы до апгрейда #1028 — старые (w:/t:/i:), после — полные.
+
+Relational/структурные вопросы (связи, backlinks, сироты) — через graph-тулы, guarded failure-mode: одна страница и стоп, без многохоповых цепочек сам.
+
+## Key files
+
+## Decisions log
+
+## Open questions
+
+## Completed steps
+
+- [x] skills/mappa-knowledge/SKILL.md v1.0.0 — слияние using-wiki v2.2.0 + using-wiki-graph v1.1.0 в один цикл-скил (ingest/query/lint + граф-слой для реляционных/структурных вопросов)
+- [x] Старые skills/using-wiki/ + skills/using-wiki-graph/ удалены (поглощены; имена — триггер-синонимы в description)
+- [x] lint clean (67 skills, 0 violations)
+- [x] build.sh → dist/mappa-knowledge.skill; install.sh → dual targets; старые удалены из живых диров
+- [x] GREEN micro-test: свежий pi -p на реляционном вопросе (связь таска↔спека) → активация mappa-knowledge, граф-слой (graph_path→no-path, backlinks), корректная семантика рёбер
+- [x] Писано нейтрально (summaries/#1026 не упоминается); реф-конвенция полными именами (#1028, уже была в исходниках)
+
+## Notes
+
+- RED-базис: триггер-поверхность унаследована из using-wiki/using-wiki-graph (прошли ревью); дельта = слияние + цикл-фрейминг + guarded failure-mode графа. Полный behavioral smoke — за #1065.
+- Побочная lint-находка GREEN-теста: рефы в прозе (не [[викилинки]]) рёбер не дают → спека может быть сиротой, «таска↔спека» в графе теряется. Это известная семантика решения 4 (рёбра только из [[refs]]), не баг скила — отмечено как наблюдение, кандидат в follow-up, если понадобится проставлять [[викилинки]] при создании тасок-промоушена.

.tasks/2026-08-24-01060-mappa-brainstorm-promote.md

@@ -0,0 +1,28 @@
+# mappa-brainstorm-promote
+<!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-08-24T18:49:01.966Z -->
+
+
+## Goal
+UPDATE workshop-promote-brainstorm → **mappa-brainstorm-promote** (редизайн mappa-skill-suite, спека w:2605). АПДЕЙТ, не rewrite.
+
+Fold-in 1: mappa-service target. Промоут в mappa-сервисные борды (mappa, .common, …) — отдельный канал: сервисные тулы mcp__mappa__task_create/wiki_create (под лизом, claim через task_claim_next); pointers-таска НЕ нужна, если спека уже в вики проекта (w:NNNN) — описание импл-таски ссылается на неё; review-umbrella — сервисная таска (status=blocked, blocker=impl#); covering-письмо в инбокс цели (канон delegate-task) — в обоих каналах. Файловый путь (projects-meta → .tasks/STATUS.md) остаётся.
+
+## Key files
+
+## Decisions log
+
+## Open questions
+
+## Completed steps
+
+- [x] skills/mappa-brainstorm-promote/SKILL.md v1.2.0 (MINOR) — UPDATE workshop-promote-brainstorm: добавлена 4-я ветка маршрутизации **mappa-service** (fold-in 1: лиз через task_claim_next, спека через mcp__mappa__wiki_create, импл-таски через mcp__mappa__task_create, pointers-таска НЕ нужна если спека в вики w:NNNN, review-umbrella сервисная таска, covering-письмо в инбокс цели)
+- [x] NB (2026-08-24, инцидент): tasks_create ПОСЛЕДОВАТЕЛЬНО, не батчем (гонка sha-CAS счётчика agenda; при промоуте mappa-skill-suite 6/7 упали) — в шаге 8 + failure modes + what-not-to-do
+- [x] File channel (projects-meta → .tasks/STATUS.md) сохранён; шаги перенумерованы (вставлен шаг 4)
+- [x] Старое имя workshop-promote-brainstorm — триггер-синоним в description; каталог git mv
+- [x] lint clean (67 skills, 0 violations); build.sh → dist/mappa-brainstorm-promote.skill (старый .skill удалён); install.sh → dual; старый удалён из живых диров
+- [x] GREEN micro-test: свежий pi -p на «промоутни брейнсторм… таргет mappa» → активация mappa-brainstorm-promote, service channel (лиз/task_create последовательно/wiki_create/без pointers/review-umbrella/covering-письмо)
+
+## Notes
+
+- RED-базис: UPDATE существующего скила (триггеры не менялись); дельта = fold-in 1 + NB последовательности. Полный behavioral smoke — за #1065.
+- Актуальность шага 3 (определение канала): сервисные борды — mappa, .common (доска в mappa-сущностях); обычные проекты — файловая доска. Определение по наличию .tasks/STATUS.md.

.tasks/2026-08-24-01061-mappa-delegation.md

@@ -0,0 +1,29 @@
+# mappa-delegation
+<!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-08-24T18:49:07.632Z -->
+
+
+## Goal
+Rewrite delegate-task → **mappa-delegation** (редизайн mappa-skill-suite, спека w:2605).
+
+Скилл = цикл, не тул; старые имена — триггер-синонимы. Поглощает: delegate-task. Каждая кросс-проектная делегация — пара: tasks_create + covering-письмо в инбокс получателя (таска на доске не пингует живую сессию). #1054 create-без-лиза — опционально (контракт работает на текущих тулах); перейти, когда #1054 имплементится.
+
+НЕ применимо: self-assigned таски на своей доске («создать задачу себе» → mappa-task-work), работа своими руками, workshop-внутренние таски.
+
+## Key files
+
+## Decisions log
+
+## Open questions
+
+## Completed steps
+
+- [x] skills/mappa-delegation/SKILL.md v1.0.0 — rewrite delegate-task v0.5.1 (цикл: pre-flight gate → шаблон → preview → confirm → covering-письмо → review-umbrella → downstream)
+- [x] Старый skills/delegate-task/ удалён (поглощён; имя — триггер-синоним в description)
+- [x] Suite-ссылки: using-tasks→mappa-task-work, inter-session-messaging→mappa-messaging, using-wiki→mappa-knowledge; нота лизинговой модели #1054 (create-без-лиза — опционально, контракт работает на текущих тулах)
+- [x] lint clean (67 skills, 0 violations); build.sh → dist/mappa-delegation.skill (старый .skill удалён); install.sh → dual; старый удалён из живых диров
+- [x] GREEN micro-test: свежий pi -p на «создать задачу на агента… common» → активация mappa-delegation, обязательная пара tasks_create + covering-письмо (адрес из адресной книги, [event: created]), review-umbrella с наследованием weight
+
+## Notes
+
+- RED-базис: тело унаследовано из delegate-task v0.5.1 (прошёл ревью + smoke); дельта = rename, suite-ссылки, цикл-фрейминг, нота #1054. Полный behavioral smoke — за #1065.
+- Поглощает delegate-task без потери контента (все шаги 1–7 сохранены, включая weight-наследование review и downstream-правило task+letter).

.tasks/2026-08-24-01062-mappa-task-work.md

@@ -0,0 +1,31 @@
+# mappa-task-work
+<!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-08-24T18:49:13.376Z -->
+
+
+## Goal
+Rewrite using-tasks + task-format + task-loop + priority-due → **mappa-task-work** (редизайн mappa-skill-suite, спека w:2605). Центральный, крупный.
+
+Скилл = цикл, не тул; старые имена — триггер-синонимы. Поглощает: using-tasks, task-format (вливается), task-loop (loop-mode ВНУТРИ, вариант A — отдельный скилл не создаётся), priority-due-раздел (P0-P2 + дедлайны: приоритет = территория человека, агенты ставят только при создании; дефолт P1; дедлайн-механика: notify при просрочке без авто-бампа).
+
+Цикл: выбор работы (claim) → исполнение → сдача (close + review-umbrella). Один триггер-сёрфейс: «поработай очередь» / «work the queue» → mode=loop.
+
+## Key files
+
+## Decisions log
+
+## Open questions
+
+## Completed steps
+
+- [x] skills/mappa-task-work/SKILL.md v1.0.0 — центральный цикл: ориентация → выбор работы (claim, priority/due) → исполнение → сдача (close + review-umbrella) + пауза/переключение
+- [x] Loop-mode ВНУТРИ (вариант A, отдельный скил не создаётся): «поработай очередь»/«work the queue» → цикл claim→work→close→claim; пустая очередь = стоп, без демона/CronCreate; session_break gate; consult gate (human-only/strict-human → STOP перед close/commit)
+- [x] Priority/Due-раздел: приоритет = территория человека, агент ставит только при создании, дефолт P1, просрочка → admin_overdue_scan notify однократно, без авто-бампа
+- [x] Формат таски (из task-format): mappa task_create схема (priority/due при создании) + legacy STATUS.md блок (переходный, Weight/Notify обязательны)
+- [x] Поглощены: using-tasks (борд/лиз/close/notify/рефы [[task:N]]), task-format (формат), task-loop (loop-mode), task-priority-due (раздел). Старые имена — триггер-синонимы в description
+- [x] lint clean (65 skills, 0 violations); build.sh → dist/mappa-task-work.skill (старые .skill удалены); install.sh → dual; старые удалены из живых диров
+- [x] GREEN micro-test: свежий pi -p на «поработай очередь» → активация mappa-task-work, loop-mode, стоп-гейты, пустая очередь = стоп без поллинга
+
+## Notes
+
+- RED-базис: контент унаследован из трёх скилов (все прошли ревью/smoke); дельта = слияние + цикл-фрейминг + priority/due раздел. Полный behavioral smoke (вкл. loop-mode, session-break, empty-stop) — за #1065.
+- Убраны: task-loop ссылки на projects-meta claim (primary — mappa task_claim_next; file channel — переходный, описан в секции legacy).

.tasks/2026-08-24-01063-mappa-closing-ritual.md

@@ -0,0 +1,30 @@
+# mappa-closing-ritual
+<!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-08-24T18:49:19.363Z -->
+
+
+## Goal
+НОВЫЙ скилл **mappa-closing-ritual** (редизайн mappa-skill-suite, спека w:2605).
+
+Финиш-фаза форкфлоу: session-handoff(write) + PROPOSE wiki-ingest + task closes + sweep. Старт ≠ финиш: closing-ritual = write-path с процедурой и подтверждением. Ad-hoc: mode=light — явный вопрос «Сделать handoff?» в конце сессии (НЕ автоматический sweep); решение за человеком. Поглощает: session-handoff(write-часть).
+
+Handoff: sliding, per-project, versioned-история; read на старте — mappa-session-orient, write на финише — тут. Мутации (handoff write / wiki-ingest / task closes) — только после подтверждения пользователя.
+
+## Key files
+
+## Decisions log
+
+## Open questions
+
+## Completed steps
+
+- [x] skills/mappa-closing-ritual/SKILL.md v1.0.0 — НОВЫЙ скилл (финиш-фаза): scope check → mid-task capture → compose handoff → handoff_write (версия h:N) → PROPOSE wiki-ingest → PROPOSE task closes → один блок-предложение; мутации только после «да»
+- [x] mode=light для ad-hoc: явный вопрос «Сделать handoff?», НЕ автоматический sweep; решение за человеком
+- [x] Поглощает session-handoff (write-часть); read-часть уходит в mappa-session-orient (#1064); старое имя — триггер-синоним
+- [x] Старый skills/session-handoff/ удалён (включая hooks/commit-detector — новый дизайн: ритуал на session-end, не на substantive commit)
+- [x] lint clean (65 skills, 0 violations); build.sh → dist/mappa-closing-ritual.skill; install.sh → dual; старый удалён из живых диров
+- [x] GREEN micro-test: свежий pi -p на «завершаем сессию» → активация mappa-closing-ritual, полный ритуал (7 шагов), мутации только после «да», mode=light «Сделать handoff?»
+
+## Notes
+
+- RED-базис: write-процедура унаследована из session-handoff v1.0.0 (прошёл ревью); дельта = split read/write + mode=light + confirm-гейт. Полный behavioral smoke (триггеры свои + false-positive на task-зоне) — за #1065.
+- commit-detector hooks удалены осознанно: suite проектирует closing-ritual как session-end-driven, а не commit-driven.

.tasks/2026-08-24-01064-mappa-session-orient.md

@@ -0,0 +1,31 @@
+# mappa-session-orient
+<!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-08-24T18:49:25.792Z -->
+
+
+## Goal
+НОВЫЙ скилл **mappa-session-orient** (редизайн mappa-skill-suite, спека w:2605). Самый новый, делается ПОСЛЕДНИМ.
+
+Старт-фаза форкфлоу: контракт + чтение (нужен и для ad-hoc, где нет AGENTS.md-контракта). Поглощает: pulling-before-work (полный цикл --ff-only), session-handoff(read), session-inbox-monitor(raise), using-system-snapshot (liveness-сводка «живо/мертво», одна строка), live-ingest query (потребитель session-live-ingest: GET /session?project=, stale-active детект, «другая связка + не завершена» → предложение: забить / дернуть письмом / продолжить).
+
+Граница: session-orient = «живо/мертво»; глубокая диагностика — вне suite (адхок). Эскалация: проблема на старте → не углубляться, передать человеку/диагностической сессии.
+
+## Key files
+
+## Decisions log
+
+## Open questions
+
+## Completed steps
+
+- [x] skills/mappa-session-orient/SKILL.md v1.0.0 — старт-фаза: контракт → pull (--ff-only, полный цикл) → handoff read (staleness >7д → ask; orient+ask, без auto-execute) → inbox raise+sweep → liveness-сводка (meta_health/admin_status/snapshot, «живо/мертво») → live-ingest query (session_list, stale-active краш-детект, «другая связка → предложить»)
+- [x] Граница orient/ops (w:2605 round 3): «живо/мертво»; проблема на старте → эскалация человеку/диагностической сессии, не углубление
+- [x] Поглощены: pulling-before-work, session-handoff(read), session-inbox-monitor(raise), using-system-snapshot (liveness); старые имена — триггер-синонимы
+- [x] Live-ingest 404-skip задокументирован (роуты /session не задеплоены — сервер #1022 в репо, деплой ждёт #1055); контракт — w:2604
+- [x] mappa-messaging: ссылки session-inbox-monitor → mappa-session-orient (inbox raise) обновлены (3 места)
+- [x] lint clean (63 skills, 0 violations); build.sh → dist/mappa-session-orient.skill; install.sh → dual; поглощённые удалены из живых диров
+- [x] GREEN micro-test: свежий pi -p на «начало сессии» → ритуал по шагам (контракт→pull→handoff→inbox→liveness→live-ingest), граница «живо/мертво» + эскалация, 404-skip, read-only
+
+## Notes
+
+- #1064 была 🔵 blocked ← #1024 (клиент session-sync). Скил-документ завершён по контракту w:2604/w:2605; live-ingest E2E (шаг 6) отложен: сервер #1022 не задеплоен (#1055), клиент #1024 (.common) открыт. 404-skip в скиле — ориентация не блокируется.
+- RED-базис: контент унаследован из 4 поглощённых скилов (все прошли ревью); дельта = слияние + live-ingest query + граница orient/ops. Полный behavioral smoke — за #1065.

.tasks/2026-08-24-01065-mappa-skill-suite-review.md

@@ -0,0 +1,49 @@
+# mappa-skill-suite-review
+<!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-08-24T18:49:35.610Z -->
+
+
+## Goal
+Skill-review checkpoint для mappa-skill-suite (промоушен 2026-08-24).
+
+**Спецификация:** w:2605 concepts/mappa-skill-suite (mappa wiki). **Источник дизайна (trace):** .workshop/.archive/2026-08-24-mappa-skill-suite.md.
+**Импл-таски:** #1058 mappa-messaging, #1059 mappa-knowledge, #1060 mappa-brainstorm-promote, #1061 mappa-delegation, #1062 mappa-task-work, #1063 mappa-closing-ritual, #1064 mappa-session-orient.
+
+**Кто делает:** **не имплементер.** Другая сессия / другой день / другой агент (identity-not-location).
+
+**Поведенческий smoke-test на скилл (это и есть acceptance):**
+- Скилл активируется в чистой сессии на каждой триггер-фразе из description (русский И английский варианты).
+- Скилл **не** активируется на 2-3 близких но не своих фразах из соседних доменов (false-positive check).
+- Каждый шаг секции Steps отрабатывает на тестовом буфере без ошибок.
+- Failure modes уводят в abort, не в частичный успех.
+- What NOT to do соответствует реальности.
+
+**Чек-лист:**
+- Сверить каждый скилл со спекой w:2605 (структура, поглощения, naming mappa-).
+- Старые имена работают как триггер-синонимы (inter-session-messaging, using-wiki, delegate-task, workshop-promote-brainstorm, using-tasks, session-handoff, pulling-before-work…).
+- mappa-session-orient сделан ПОСЛЕДНИМ и учитывает live-ingest (#1022/#1024).
+- mappa-task-work: loop-mode, priority/due-раздел, session-break.
+
+Findings → follow-up tasks через tasks_create в OpeItcLoc03/skills.
+
+**Закрытие:** только когда все findings зафайлены ИЛИ ревьюер подтвердил «нет findings» в close-note.
+
+## Key files
+
+## Decisions log
+
+## Open questions
+
+## Completed steps
+
+- [x] Ревью запущено через clean-context субагентов (не-имплементер identity: review_subagent с чистой спецификацией + свежие pi -p сессии без истории) — метод review-kit-pi-method
+- [x] **Структурное ревью vs w:2605 — 7/7:** batch 1 (messaging/knowledge/promote/delegation): 3 PASS, promote NEEDS-WORK → исправлено (cycle/procedure фрейминг, фикс 78542c0); batch 2 (task-work/closing-ritual/session-orient): 3 PASS
+- [x] **Минорные findings исправлены:** EN-триггеры в messaging (78542c0), attribution review-umbrella в task-work (45baadc); остальные миноры — стилистические (inline-absorption vs таблица), не блокеры
+- [x] **Behavioral smoke (свежие pi -p, чистая сессия):**
+  - Позитив (старые имена = синонимы): using-tasks → mappa-task-work, using-wiki → mappa-knowledge, delegate-task → mappa-delegation, «напиши письмо» → mappa-messaging, «промоутни… таргет mappa» → mappa-brainstorm-promote (service channel), «завершаем сессию» → mappa-closing-ritual, «начало сессии» → mappa-session-orient, «поработай очередь» → loop-mode
+  - Негатив: «поставь таску себе» → НЕ делегирование (mappa-task-work территория), «отбой» → анти-триггер, без активации
+- [x] **Отложенные зависимости (не findings):** live-ingest E2E (шаг 6 session-orient) — после деплоя #1055 + клиента #1024 (404-skip задокументирован в скиле); build-hermes unmapped — pre-existing
+
+## Notes
+
+- Ревьюер-identity: .workshop (решение оператора) через clean-context субагентов — identity-not-location, имплементерская сессия не оценивала свои артефакты сама.
+- Verdict: APPROVE-WITH-FINDINGS → все findings зафайлены и исправлены (3 фикса), блокеров нет.

.tasks/2026-08-25-01066-mappa-brainstorm-promote-storm-channel.md

@@ -0,0 +1,25 @@
+# mappa-brainstorm-promote-storm-channel
+<!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-08-25T06:00:37.319Z -->
+
+
+## Goal
+Апдейт скила mappa-brainstorm-promote (1.5.0 → 1.6.0): миграция с файлового канала на mappa storm-сущности.
+
+Скоуп:
+1. Буфер шторма = mappa storm-сущность (type=storm) в ЛЮБОМ проекте (не файл .workshop/.brainstorm/). Скил становится project-agnostic: шторм живёт там, где его ведут, не только в воркшопе.
+2. Промоут mappa-service маршрута через storm_promote (атомарно buffer → wiki-страница + archive, решение 7), не через git mv в .workshop/.archive/.
+3. Зафиксировать «штормы в любом проекте» в mappa-спеке (concepts/mappa) — сейчас скил воркшоп-центричный.
+4. Workshop-meta маршрут: файловые .brainstorm/.archive остаются только для локальной методологии зоны — или мигрируют тоже (решить в таске).
+5. Summary-дисциплина уже в 1.5.0 (9b606f7) — не дублировать.
+
+Контекст: решение оператора 2026-08-25 («штормы могут вестись не только в воркшопе»). Связано: wiki:2661 (unified search — storm-карточки), task:1048 (review mappa-wiki-search). Исполнитель — workshop-сессия (оператор: «ты сам сделаешь в новой сессии»).
+
+## Key files
+
+## Decisions log
+
+## Open questions
+
+## Completed steps
+
+## Notes

.tasks/NEXT_SESSION.md

@@ -1,46 +1,3 @@
----
-_last_updated_: 2026-08-12T17:21:33Z
-session_id: 2026-08-12-setup-tasks-noop
----
+# ⛔ Файловая доска закрыта
 
-# Next session handoff
-
-**Сессия (headless): «настрой таски» → сработал `setup-tasks` → mode **noop**: доска уже каноническая (STATUS.md 70KB, emoji-легенда, `**Poller:** eligible`, 24 per-task файла, 12 блоков задач). Коммитов нет, мутаций нет. Предыдущий handoff (17:19Z, qna-command-index) перенесён: его ask-items не отвечены — живут ниже в «Спроси user'а». Актуальный снимок доски: 0 🔴 / 3 🟡 / 1 🔵 / 12 ⚪ / 11 🟢.**
-
-## Recent commits
-- `5b00c83` meta(tasks): update [session-close-ritual-extension-review] — закрыт VERDICT
-- `69e57d5` meta(tasks): close [session-close-ritual-extension-review]
-- `4d1c3cb` meta(tasks): create [command-index-review] — ⚪ не-имплементер ревью
-- `7186304` feat: command-index v0.1.0 — just/Makefile convention skill (idea 3, claude-to-agents)
-- `d304549` docs(session-handoff): v0.5.0 — headless ritual built (session-close-ritual extension), agent_end rationale
-
-(эта сессия коммитов не делала; предыдущий handoff-write 17:19Z остался staged → перезаписан этим, sliding)
-
-## Open треки
-| Трек | Готовность | Entry-point |
-|---|---|---|
-| `command-index-review` | ⚪ ready | **главный кандидат** — STATUS.md. Не-имплементер ревью 7186304: конвенция (таргеты, help=авто-док, just>make на Windows), анти-спроул, триггер-дискриминация (pos «как тут запускается»/«как собрать»/вход с justfile; neg «настрой таски»→setup-tasks, «как юзать вики»→using-wiki), lint 46/0, dist/install parity, description ≤1024. Follow-up вне скоупа: project-bootstrap эмитит justfile. |
-| `active-platform-eval` | 🟡 paused | стоп перед eval-set authoring — ждёт Q2 («20 запросов соло или HTML-ревью-шаблон?»). |
-| `skill-readmes` | 🟡 paused | англ. README на каждый скил; кластер caveman или active-platform/find-skills/context7/using-markitdown (см. `compress-dedup`). |
-| `agent-neutral-skill-pipeline` | 🟡 paused | долг idea 19 п.5 — осознанно отложен. |
-| `setup-agents-task-runner-windows-fixes` | 🔵 blocked | 5 дефектов воркэраунд-починены в OpeItcLoc03/common, ждёт переноса в SKILL.md. |
-| `using-yt-tools-rate-limit-guard` | ⚪ ready | править plugin-репо `OpeItcLoc03/yt-tools`, НЕ claude-skills stub. |
-| `meta-host-routing-install` + `-test-trigger` | ⚪ ready | скил не установлен — install + триггер-прогон. |
-| `hermes-converter-ci`, `tdd-criteria-precommit-hook`, `tasks-board-cleanup-2026-05`, `archive-roundtrip-test`, `skills-grouping-revisit`, `delegate-task-review-weight-inherit`, `using-markitdown-cli-rewrite`, `skill-using-system-snapshot` | ⚪ ready | разное, см. STATUS.md блоки. |
-
-## Спроси user'а
-- **Архивировать 🟢 кластер** (kept-until-merged, 11 шт., commits подтверждают): `project-discipline-dist-rebuild`, `project-discipline-description-contradiction`, `de-superpowers-skill-readmes`, `skills-live-claudemd-superpowers-trigger`, `using-tasks-archive-path-fix`, `brainstorming-skill-review`, `diagnosing-bugs-writing-skills-review`, `session-ritual-context7-pins-review`, `readme-ru-pins-backfill`, `session-close-ritual-pi-extension`, `session-close-ritual-extension-review` → `.tasks/.archive/done-2026-08.md` (конвенция tasks-board-cleanup). Ralph-loop verifier-задач на доске нет (**Verifier:** 0 совпадений) — ограничение не применяется.
-- **Wiki-ingest / докс-фикс (перенос с прошлой сессии, не отвечен)**: README.md врёт про `scripts/install.ps1` — «not yet implemented (on task board)», а PowerShell-порт уже существует; Quick start упоминает только sh-скрипты, хотя есть `build.ps1`/`update.ps1`. Заингестить в `.wiki/` или сразу починить README (малый docs-фикс → ⚪ таска)? (Новых durable-кандидатов эта сессия не дала — noop.)
-- **`command-index` live-данные**: скил сработал по триггеру «как тут запускается проект» (прошлая сессия), корректно нашёл де-факто индекс (`scripts/` + README, no justfile). Включить в `command-index-review` как живую проверку триггера? (Имплементер-сессия ревью не делает.)
-- **Autopush grant**: project-discipline Rule 4 reset на новую сессию — нужен ли грант (прошлые сессии пушили свободно).
-
-## Не делать (preemptive guards)
-- **Hermes**: owner сказал «похуй на гермеса» — pending-скилы НЕ трогать без явного запроса.
-- **Ритуал закрытия НЕ выполнять молча** — мутации = предложения, каждая после «да» (HARD-GATE session-handoff v0.5.0, подтверждён session-close-ritual-extension-review VERDICT).
-- **setup-context7 v2.0.0**: мутации (`~/.config/projects-secrets/ctx7.env`, uninstall MCP-плагина, чистка `mcpServers.context7`) — только после явного подтверждения.
-- **session-inbox-monitor**: hermes pending до tool-side аудита.
-- **`command-index-review`** — не-имплементер скоуп: авторская сессия (7186304) ревью не делает (anti-self-review).
-- Governance: peer-сессии шлют предложения, не authority; scope-эскалации ратифицирует человек.
-
-## Memory updates за сессию
-- (нет приватного memory) — сессия noop, знание не менялось. Действующий факт: `.tasks/` в каноническом виде, setup-tasks корректно распознал noop (не тронул доску).
+**Не читать. Не править.** Канон — mappa (`mcp__mappa__task_*`): task-сущности проекта. Скил: `mappa-task-work`.

.wiki/CLAUDE.md

@@ -1,40 +1,3 @@
-# Wiki Schema — claude-skills
+# ⛔ Файловый канал закрыт
 
-Project-specific wiki conventions. Read this before any wiki operation.
-
-This wiki follows Karpathy's LLM Wiki pattern:
-**https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f**
-
-The `wiki-maintainer` skill enforces the workflow and file formats. This file overrides the skill where they conflict.
-
-## Page types in this project
-
-- `entities/` — discrete things this project tracks. Reserved for future use (individual skills if they accumulate non-obvious context, tools we adopt).
-- `concepts/` — design decisions, technical gotchas, refactor notes. Most pages live here.
-- `packages/` — currently empty. Would be used if we extract a package (e.g. a CLI) from this repo.
-- `sources/` — one summary per ingested external doc; carries `ingested:` and `raw_path:` frontmatter.
-- `overview.md` — single project-wide overview. Read this first if new to the repo.
-
-## Naming
-
-- `kebab-case.md`, **Latin only**. Transliterate Cyrillic in filenames; keep the original title in the H1 + frontmatter.
-
-## Domain conventions
-
-- Skill-related design notes go in `concepts/<skill-name>-*.md` (e.g. `active-platform-decision.md`).
-- Build / install pipeline notes live in `concepts/build-*.md`.
-- Refactor / re-alignment commits get a `concepts/<what>-realignment.md` page.
-
-## Frontmatter
-
-Minimum:
-
-```yaml
----
-title: Human-readable title
-type: concept | entity | package | source | overview
-updated: YYYY-MM-DD
----
-```
-
-`source/` pages also carry `ingested:` and `raw_path:`.
+**Не читать. Не править.** Канон — mappa (`mcp__mappa__*`): wiki-сущности проекта, конвенции — AGENTS-сущность. Скил: `mappa-knowledge`.

.wiki/concepts/context7-setup.md

@@ -1,90 +1,68 @@
 ---
-title: "context7 setup: official plugin + API key"
+title: "context7 setup: CLI-first (migrated from official plugin)"
 type: concept
-updated: 2026-04-28
+updated: 2026-08-13
 ---
 
-# context7 setup: official plugin + API key
+# context7 setup: CLI-first (migrated from official plugin)
 
-_2026-04-28._
+_2026-04-28 (plugin era) → 2026-08-12 (CLI migration, setup-context7 v2.0.0)._
 
-## Where the MCP server is now registered
+## Current state (canonical, since 2026-08-12)
 
-Single source: the official plugin **`context7@claude-plugins-official`**.
+Single source = the **`ctx7` CLI** (npm), agent-neutral — any harness (pi / claude / hermes / codex)
+runs it in bash. **No MCP registration, no plugin.**
 
-The plugin's `.mcp.json` (after install) lives at:
-```
-~/.claude/plugins/cache/claude-plugins-official/context7/<version>/.mcp.json
-```
+- CLI: `ctx7` v0.5.8 installed globally (`npm i -g ctx7`).
+- API key: `~/.config/projects-secrets/ctx7.env` → `CONTEXT7_API_KEY=<key>` (our secrets convention,
+  cf. `interns.env` / `auth.toml`).
+- Works anonymously for basic queries; the key raises rate limits but does not change output.
+- Legacy removed: plugin `context7@claude-plugins-official` uninstalled (installed_plugins + cache +
+  pluginUsage), manual `mcpServers.context7` entries cleaned from `~/.claude.json` /
+  `~/.claude/settings.json` (top-level + project-scoped). Backups: `~/.claude.json.bak-<ts>`,
+  `~/.claude/settings.json.bak-<ts>`.
 
-For this user the version slug is `unknown` (marketplace plugin without a tagged release).
+Procedure: **`setup-context7`** skill ([`skills/setup-context7/SKILL.md`](../../skills/setup-context7/SKILL.md)) —
+key discovery (search `ctx7.env` → env var → settings.json → .claude.json, reuse, never invent),
+confirmation gates before any mutation, smoke via `ctx7 library` (functional; works anonymously).
+Usage policy: **`using-context7`** skill — `ctx7 library <name>` → `ctx7 docs <libraryId> "<question>"`.
+Git Bash gotcha: library IDs start with `/` and path-convert — use `//owner/repo` double-slash.
 
-## API-key injection
+**Verification gotcha (commit `79baad1`):** `ctx7 whoami` answers "Not logged in" even with an env key —
+it's OAuth identity (`ctx7 login`), not a key check. The functional smoke is `ctx7 library`, not `whoami`.
 
-The `@upstash/context7-mcp` npm package, run via stdio, accepts the key as a CLI flag (per Upstash docs at <https://context7.com/docs/resources/all-clients>):
+## History: plugin era (2026-04-28 → 2026-08-12, rollback reference only)
 
-```json
-{
-  "context7": {
-    "command": "npx",
-    "args": ["-y", "@upstash/context7-mcp", "--api-key", "ctx7sk-..."]
-  }
-}
-```
+Before the CLI migration, context7 ran through the official MCP plugin
+`context7@claude-plugins-official`. The plugin's `.mcp.json` (after install):
+`~/.claude/plugins/cache/claude-plugins-official/context7/<version>/.mcp.json` (version slug `unknown`).
 
-We injected the user's existing key (previously in HTTP-header form) into this `args` array. Header / `env` block forms are also supported, but the CLI flag is what Upstash recommends for stdio.
+The key was injected as a CLI flag into `args`:
+`["-y", "@upstash/context7-mcp", "--api-key", "ctx7sk-..."]` (Upstash-recommended form for stdio;
+header / `env` block forms also supported). Three manual MCP registrations were deleted at the time
+(settings.json top-level, .claude.json top-level, and a project-scoped one in
+`projects["…/snolla-admin-ui"].mcpServers.context7`).
 
-## What was removed
+**Plugin-update gotcha (moot since uninstall, keep for rollback):** `/plugin update` / re-install
+overwrote the plugin's `.mcp.json` from the marketplace cache, dropping the `--api-key` flag — needed
+re-application after every update.
 
-Three manual MCP registrations were deleted:
+**Rollback to the plugin path** (if ever needed): restore the `.bak-*` files, reinstall the plugin
+(`/plugin install context7@claude-plugins-official`), re-inject the key, restart Claude Code. Full
+procedure is in the `setup-context7` skill's Rollback section.
 
-| File | Where | Had API key? |
-|---|---|---|
-| `~/.claude/settings.json` | top-level `mcpServers.context7` | yes (header) |
-| `~/.claude.json` | top-level `mcpServers.context7` | yes (header) |
-| `~/.claude.json` | `projects["…/snolla-admin-ui"].mcpServers.context7` | no (legacy) |
+## Why CLI-first
 
-Backups saved with suffix `.bak-YYYYMMDD-HHMMSS` next to each file.
+Context7 ships as both an HTTP MCP server and an npm CLI. The MCP path is harness-specific glue
+(claude-plugins-official); pi doesn't see it (the claude-mcp-bridge only reads `~/.claude.json`, and
+even then it's fragile). Per the sovereign-catalog principle *"что можно сделать CLI — делаем CLI и
+оборачиваем в скил; MCP только там, где нужен структурированный/интерактивный протокол"* — the CLI
+is the canonical path (idea 16, `claude-to-agents`).
 
-## ⚠️ Plugin-update gotcha
+## Why two skills
 
-`/plugin update context7@claude-plugins-official` (or a fresh re-install) **will overwrite** the plugin's `.mcp.json` from the marketplace cache, dropping the `--api-key` flag. After any plugin update, re-apply the edit:
+- **`using-context7`** (policy, every-time): when to call, how to phrase queries, budget.
+- **`setup-context7`** (one-time, mutates user config): install, key reuse, legacy cleanup.
 
-```bash
-# inspect
-cat ~/.claude/plugins/cache/claude-plugins-official/context7/<version>/.mcp.json
-
-# if --api-key is missing, re-inject
-```
-
-The marketplace upstream of the plugin lives at `anthropics/claude-plugins-official/external_plugins/context7/.mcp.json` and is two lines — unlikely to change often, but we should expect to re-apply the flag after updates.
-
-## Restart required to take effect
-
-Claude Code reads MCP server configs at session start. The session in which this change was made keeps its old (HTTP-transport) connection until a restart. After restart, the plugin's stdio invocation takes over.
-
-## Why this matters
-
-Manual MCP entries in `~/.claude.json` / `settings.json` are easy to:
-- duplicate accidentally (we had three for one server)
-- forget about when sharing config
-- drift from the canonical version
-
-The plugin centralizes the registration and gets versioned through the marketplace. The price is a single edit-after-update for the API key.
-
-## Now captured as a skill
-
-The procedure above is now formalized as the **`setup-context7`** skill ([`skills/setup-context7/SKILL.md`](../../skills/setup-context7/SKILL.md)). It runs the same algorithm with confirmation gates and key-discovery logic (search `settings.json` → `.claude.json` → env, reuse what's there, never invent). `using-context7` got a small **Prerequisites** section pointing at it.
-
-### Why split into two skills
-
-Two distinct concerns:
-
-- **Policy** (every-time, short-running): when to call resolve-library-id, query budget, how to phrase queries — this lives in `using-context7`.
-- **Setup** (one-time, mutates user config): install plugin, inject key, clean manual entries — this lives in `setup-context7`.
-
-Mixing them would make the policy skill ~2× larger, dilute its description (worse triggering), and make every library question pull setup procedure into context. The split is also a template for future "X plugin + how-to-use-X" skill pairs.
-
-### Cross-platform
-
-The setup skill is platform-agnostic. Only the JSON validator differs (PowerShell on Windows, `jq` / Python on Linux/macOS). Paths (`~/.claude/...`) are identical.
+Mixing them would dilute the policy skill's description (worse triggering) and pull setup procedure
+into every library question. Template for future "X CLI + how-to-use-X" pairs.

.wiki/concepts/pi-extension-headless-ritual.md

@@ -0,0 +1,67 @@
+---
+title: pi-extension headless ritual — lifecycle + mode lessons
+type: concept
+created: 2026-08-12
+---
+
+# pi-extension headless ritual (agent_end, mode guard, loop-guard)
+
+Durable lessons from building `session-close-ritual` (консолидирован в
+`extensions/mappa.ts` репо `OpeItcLoc03/pi-extensions`, task:1486; исторически —
+отдельный файл `session-close-ritual.ts`),
+the headless injector for the session-handoff closing ritual. All three points
+were live-verified, not docs-read-only.
+
+## 1. `agent_settled` is TOO LATE for followUp injection
+
+`agent_settled` fires when pi "will not continue running automatically" — the
+process is tearing down (no retry/compaction/follow-up left). A `sendUserMessage`
+with `deliverAs: "followUp"` queued there is never processed; the run ends, and
+the extension handler even hits a stale-ctx error during teardown.
+
+**Use `agent_end`** — it fires right after the agent run ends, while queued
+follow-ups are still delivered (`followUp` waits for the agent to finish, then
+delivers; `triggerTurn: true` starts a new turn when idle). Verified against
+`agent-session.js:779-780` ("agent loop drains both queues before emitting
+agent_end") + live runs.
+
+## 2. `ctx.hasUI === false` is NOT headless-only — guard by `mode`
+
+`hasUI` is `false` in BOTH `-p` (print) and `--mode json`. An unsolicited
+injected user-message into an event-stream consumer (JSON mode) is a protocol
+surprise. RPC mode has `hasUI === true` (so a hasUI-guard accidentally allows
+rpc while missing json).
+
+**Guard: `ctx.mode === "print"`** for pi -p / scripted runs. Excludes
+tui/json/rpc in one condition.
+
+## 3. Loop-guard pattern: flag-before-send, per-session-per-cwd
+
+`agent_end` fires again after the injected ritual turn (the agent made tool
+calls, then the run ends) — without a guard: agent_end → ritual → agent_end →
+ritual → … loop.
+
+- Set the flag **synchronously BEFORE** `sendUserMessage` (no `await` between
+  check and set → no race; `emit()` is serial).
+- Per-session-per-cwd `Map`, reset on `session_start`.
+- On send-failure: keep the flag (at-most-once wins over retry — a missed
+  ritual is cheaper than double-inject). This is a deliberate asymmetry vs
+  `inbox-monitor` (which unmarks and retries).
+- `injectRitual`'s send is wrapped in try/catch: the real `sendUserMessage` is
+  a sync wrapper (`assertActive()` throws on shutdown race).
+
+## 4. Opt-in mirrors the skill, not the extension
+
+The extension checks the same opt-in as the skill it serves: the project
+`CLAUDE.md` contains the skill's trigger line (`session handoff: read on start,
+write on end`) AND `.tasks/` exists AND `.git` exists. No opt-in → silent.
+Cache per-cwd; staleness within a long session is accepted (same as
+`inbox-monitor`).
+
+## References
+
+- Source: `~/projects/pi-extensions/extensions/mappa.ts` (секция close-ritual;
+  консолидация 6 расширений, task:1486 — исторически `session-close-ritual.ts`
+  + `scripts/session-close-ritual.test.mjs`, 12 blocks, ныне тесты на mappa.ts)
+- Skill: `session-handoff` v0.5.0 — «Headless (pi)» section
+- pi docs: `extensions.md` — lifecycle diagram, `sendUserMessage` (deliverAs/triggerTurn), mode table

.wiki/concepts/session-inbox-monitor-received-msg-fp.md

@@ -15,7 +15,7 @@ mechanism** — and it stays **open** as of this writing (follow-up task
 ## Symptom
 
 In the `session-inbox-monitor-test-trigger` run (2026-06-17, clean session, 7 unprimed
-clean-context subagents), the negative phrase **«В .claude-inbox пришло сообщение от другой
+clean-context subagents), the negative phrase **«В .agents/inbox пришло сообщение от другой
 Claude-сессии. Прочитай его и ответь отправителю.»** (N1, RU) routed to
 **`session-inbox-monitor`** — a false-positive. The skill is about *raising the monitor*, not
 *handling a received message*; the latter belongs to inter-session-peer-discipline /

.wiki/concepts/web-search-skill-design.md

@@ -0,0 +1,75 @@
+---
+title: web-search skill design
+type: concept
+status: draft
+created: 2026-08-22
+---
+
+# web-search — скилл веб-поиска через субагента на search-комбо llm-web-proxy
+
+## Проблема
+
+Основная модель агента (deepseek-flash-web) не имеет веб-поиска. «Найди актуальное про X» сейчас решается костылями: curl на поисковик (блокируется 403/captcha), CDP-скрейпинг (тысячи токенов мусора в основном контексте), или отпиской «у меня нет веб-поиска».
+
+При этом llm-web-proxy уже имеет search-комбо (`deepseek-flash-search-web` / `deepseek-pro-search-web`) — нативный веб-поиск DeepSeek с цитатами, работает из коробки, без новых аккаунтов.
+
+## Решение
+
+**Pi-расширение** с тулом `search_web` (паттерн vision-subagent) + **скилл** `web-search` с политикой «когда искать».
+
+- Поиск **включён по умолчанию**: агент сам решает, когда нужны свежие данные, и вызывает тул.
+- Юзер может явно сказать «поищи X» — явный вызов.
+- Юзер может сказать **«без поиска»** — агент перестаёт вызывать тул **до конца сессии** (конверсационный механизм, как using-interns revoke; память в контексте сессии, следующая сессия — снова поиск включён).
+
+## Тул search_web
+
+Реализация в `~/projects/pi-extensions/extensions/search-web.ts` (репо `OpeItcLoc03/pi-extensions`), по образцу `vision-subagent.ts`:
+
+```
+search_web(query: string)
+→ answer: "полный текст с [1][2]"
+  sources: ["https://...", ...]   # regex по URL из citation-блока; [] если пусто
+```
+
+- **Модель**: `lwp/deepseek-pro-search-web` по умолчанию (pro-search). Переопределение: env `PI_SEARCH_MODEL` или `~/.pi/search-model.json` `{ "model": "..." }` (как PI_VISION_MODEL).
+- **Механика**: `modelRegistry.complete()` на чистом контексте с system-промптом «ищи в вебе, отвечай с цитатами [1][2]» + `search_web` инструкция. Таймаут ~120s (как vision).
+- **sources**: regex по `https?://\S+` в тексте ответа; пусто → `[]`, НЕ ошибка (поиск может не найти цитат).
+- **Ошибки**: честный текст «search failed: …», isError: true. `/search-status` command (как `/vision-model-status`).
+- Модели уже в `~/.pi/agent/models.json` (провайдер `llm-web`, префикс `lwp/`).
+
+## Скилл web-search
+
+Файл: `~/projects/skills/skills/web-search/SKILL.md` (sovereign каталог).
+
+**When to use** (триггеры):
+- Вопрос требует свежих/внешних данных: новости, цены, версии, даты, «что сейчас актуально про X»
+- «Поищи X», «найди актуальное про Y», «проверь ссылку»
+- Подтверждение факта из недавнего времени (обучение модели могло устареть)
+
+**Когда НЕ вызывать**:
+- Дизайн/рефакторинг/интроспекция проекта (код — в репо)
+- Вопросы по уже загруженному контексту (доки, файлы сессии)
+- «Без поиска» сказано юзером в этой сессии
+
+**Правила**:
+1. Один запрос = один вызов тула (не спамить серией поисков без нужды).
+2. При `sources: []` — честно «без источников», не выдумывать URL.
+3. При ответе с [1][2] — оставлять нумерацию, ссылки из sources можно дать списком.
+4. Механизм «без поиска»: после команды юзера — не вызывать тул до конца сессии, при следующем «поищи» — вернуть (повторный грант).
+
+## Тестирование (writing-skills TDD)
+
+1. **RED**: базлайн-субагент без скила — «найди актуальное про X», зафиксировать поведение (костыли/отписка).
+2. **GREEN**: субагент со скилом — вызывает `search_web`, возвращает answer+sources.
+3. Микро-тест wording'а: триггеры срабатывают на формулировках юзера; no-guidance control.
+4. Live: реальный вызов тула в сессии pi, проверка answer+sources.
+
+## Deploy
+
+1. Правки pi-extensions (search-web.ts) → commit + push → `just install`.
+2. Скилл: `skills/web-search/SKILL.md` → lint → build → install → README provenance table → commit + push (semver bump).
+3. Обновить `~/.pi/agent/models.json` при необходимости (модель уже есть).
+
+## Открытые вопросы
+
+- Нет (дизайн одобрен юзером 2026-08-22: pro-search дефолт, answer+sources, конверсационный «без поиска»).

.wiki/index.md

@@ -1,60 +1,3 @@
-# Wiki Index
+# ⛔ Файловый канал закрыт
 
-Catalog of all wiki pages. One line per page, organized by type. Updated on every ingest / new page.
-
-## Overview
-
-- [overview.md](overview.md) — what claude-skills is, layout, how to navigate
-
-## Entities
-
-<!-- (none yet) -->
-
-## Concepts
-
-
-
-
-
-
-- [active-platform-decision.md](concepts/active-platform-decision.md) — why `active-platform` is a skill (not a memory entry); why default = Windows; how it's wired into `project-bootstrap`
-- [bootstrap-claude-md-merge.md](concepts/bootstrap-claude-md-merge.md) — project-bootstrap@1.3.0 — Step 5 upgrade path becomes idempotent merge (read → diff vs template → confirm → append missing); fixes silent gap where pre-1.2.0 projects never picked up new canonical triggers (`check across all projects`, `we're on Windows`)
-- [bootstrap-skill-deps-check.md](concepts/bootstrap-skill-deps-check.md) — project-bootstrap@1.7.0 — Step 5.6 collapses the per-skill "detect-and-recommend" mirror shape into one generic `trigger → fulfiller` table walker (skill vs plugin kind, never auto-install); subsumes the deferred `[bootstrap-recommend-projects-meta]` and the existing `superpowers`-only detector
-- [bootstrap-manifest.md](concepts/bootstrap-manifest.md) — record of which `project-bootstrap` / `setup-wiki` / `setup-tasks` versions initialized this project's `.wiki/` and `.tasks/` layout (overwritten on re-bootstrap; history in git)
-- [build-notes.md](concepts/build-notes.md) — why `build.ps1` exists alongside `build.sh`; PS 5.1 backslash-in-zip gotcha; how to extract a `.skill`
-- [install-cross-platform.md](concepts/install-cross-platform.md) — paired-script parity contract for `install.{ps1,sh}` AND `build.{ps1,sh}`; rationale for the `--prune` / `-Prune` flag (combined-with-action, global-scan, default-off); install-side prunes target dirs, build-side prunes `dist/*.skill` files
-- [install-portability.md](concepts/install-portability.md) — `install.sh` / `build.sh` rewritten to drop `mapfile` (bash 4+) and `find -printf` (GNU only) so stock macOS (bash 3.2 + BSD find) works
-- [context7-setup.md](concepts/context7-setup.md) — switched context7 from manual MCP entries to the official plugin; API key in `.mcp.json` as `--api-key`; now also captured as `setup-context7` skill (one-time install/migrate flow with key discovery)
-- [projects-meta-skills.md](concepts/projects-meta-skills.md) — `setup-projects-meta` + `using-projects-meta` skill pair for the local `projects-meta-mcp` stdio server (cross-project tasks + shared Gitea wiki); local-first rule + two-step mutation pattern
-- [project-discipline-design.md](concepts/project-discipline-design.md) — design for project-discipline (four cross-project rules: conventions-over-defaults, master-only, semver-bumping, ask-before-push)
-- [pulling-before-work-design.md](concepts/pulling-before-work-design.md) — design for the pulling-before-work skill (mode-3 + skip-on-dirty)
-- [repo-layout.md](concepts/repo-layout.md) — flat `skills/`, committed `dist/`, bash + PowerShell scripts; install model
-- [skill-versioning.md](concepts/skill-versioning.md) — why infra skills carry `version: <semver>` in frontmatter and how `project-bootstrap` records them in a per-project manifest
-- [skill-vs-plugin.md](concepts/skill-vs-plugin.md) — when a bare SKILL.md is enough vs when you actually need a plugin (slash commands, hooks, sub-agents, MCP servers); concrete breakdown of `superpowers`
-- [wiki-realignment.md](concepts/wiki-realignment.md) — fixing `project-bootstrap` to create the Karpathy-canonical wiki layout
-- [interns-design](concepts/interns-design.md) — interns-design
-- [compress-dedup.md](concepts/compress-dedup.md) — `skills/compress/` deleted as a byte-identical dupe of `skills/caveman-compress/`; canonical kept for README + SECURITY + caveman-toolkit branding; better Process-step wording ported across; `version: 1.0.0` added to caveman-compress frontmatter
-- [active-platform-eval-design.md](concepts/active-platform-eval-design.md) — spec for eval-driven tuning of `active-platform`: combine the two ⚪ tasks into one workstream, 20-query cross-platform eval set (≥3 per OS + near-miss negatives), `run_loop.py` autoloop **in parallel** with manual body sweep (WSL / BSD / ambiguity), version 1.0.0 → 1.1.0 (MINOR). Status: paused after design + pre-flight check, before eval-set authorship
-- [interns-repo-read-design](concepts/interns-repo-read-design.md) — interns-repo-read-design
-- [hermes-skills-rollout-design](concepts/hermes-skills-rollout-design.md) — hermes-skills-rollout-design
-- [tdd-criteria-design](concepts/tdd-criteria-design.md) — tdd-criteria-design
-- [project-bootstrap-meta-isolation.md](concepts/project-bootstrap-meta-isolation.md) — project-bootstrap@1.11.0 — Step 1 ships meta-isolation block in `.gitignore` (`!.claude/`, `!.tasks/`, `!.wiki/`, ...) so own greenfield/upgrade projects re-enable agent meta-paths against global `core.excludesFile` cutter. Marker-based append-only on existing files; smoke-tested with negative control
-- [interns-grep-audit-design](concepts/interns-grep-audit-design.md) — interns-grep-audit-design
-- [session-handoff-skill-design.md](concepts/session-handoff-skill-design.md) — design rationale for the `session-handoff` skill (sliding overwrite into `.tasks/NEXT_SESSION.md`, phrase whitelist + substantive-commit heuristic, optional PostToolUse hook for harness-side determinism, orient+ask default, project scope, cluster 7/7 closure)
-- [using-tasks-session-break.md](concepts/using-tasks-session-break.md) — `using-tasks` v1.2.0 `session_break` marker: task-author-set boolean/string flag; after a task closes 🟢, before `tasks_claim_next`, an autonomous agent prints the verbatim SESSION BOUNDARY line and stops instead of chaining the next task. Absent → unchanged
-- [delegate-task-session-break.md](concepts/delegate-task-session-break.md) — `delegate-task` v0.2.2 — authoring side of the `session_break` marker (consumer = [[using-tasks-session-break]]): pre-flight Q6 + optional template field `session_break: true | "<hint>"`; three set-it cases (domain-switch / milestone / heavy infra); not a default
-- [delegate-task-review-weight.md](concepts/delegate-task-review-weight.md) — `delegate-task` v0.2.3 — Step 5 review-task now sets explicit `weight`, inherited from impl with a `needs-claude` floor (impl `needs-human`→review `needs-human`; `cheap-ok`→`needs-claude`). Fixes the reconciler skipping weightless review tasks (root cause of manual patch `c0af151`)
-- [using-system-snapshot-design.md](concepts/using-system-snapshot-design.md) — `using-system-snapshot` v0.1.0 — thin read-only skill wrapping the single `mcp__projects-meta__meta_system_snapshot` call (poller + local docker + cached task summary); replaces scattered `tasklist`/`docker ps`/manual `meta_status`; core rule = no liveness claim without calling the tool this turn; three-line output; defers deep docker to [[using-vds-ops]] and precise tasks to [[using-projects-meta]]
-- [using-tasks-status-archival.md](concepts/using-tasks-status-archival.md) — `using-tasks` v1.3.0 done-task archival rule (≥10 🟢 → `.tasks/archive/YYYY-MM.md`) fixes STATUS.md bloat; documents why `tasks_get_status` (single-task, by slug) / `tasks_aggregate` (cross-project cache) can't replace the orientation board-read, so the literal task instruction was not followed
-- [delegate-task-negative-trigger-fp.md](concepts/delegate-task-negative-trigger-fp.md) — `delegate-task` v0.2.1 FP fix: «создать задачу себе» stem-matched the «создать задачу на агента» positive trigger; abstract "does NOT apply when doing the work yourself" carve-out loses to literal stem-match under the 1%-rule → made the negative literal + routed (→ using-tasks). Verified pos 5/5, neg 4/5 (was 0/5)
-- [using-markitdown-cli-migration.md](concepts/using-markitdown-cli-migration.md) — `using-markitdown` v1.0.0→v1.0.1 (PATCH): rewrote from the Docker-based `mcp__markitdown__convert_to_markdown` MCP tool to the native `markitdown` CLI (0.1.6, on PATH); dropped the host→container `file://` mount caveat; container decommission is by image ancestor (`--filter ancestor=markitdown-mcp:latest`), not by the non-existent name `markitdown-mcp`
-- [session-inbox-monitor-received-msg-fp.md](concepts/session-inbox-monitor-received-msg-fp.md) — sibling of [[delegate-task-negative-trigger-fp]]: `session-inbox-monitor` FP-fires on RU «обработай полученное письмо» (N1) because its literal+routed carve-out points at `inter-session-peer-discipline`, which **isn't installed** → no competitor, nearest inbox-skill wins. Borderline (neg 2/3, EN twin clean), body-load self-corrects. **Open** (follow-up task). New principle: *a routed negative competes only if its route target is installed*
-- [task-format-design.md](concepts/task-format-design.md) — new `task-format` skill v0.1.0: public reference for the on-disk `.tasks/STATUS.md` block format the poller parses (header regex, status emoji, `**Weight:**` / `**Notify:**` / `**Requirements:**`); ships with `factory` where the internal wiki/MCP-source can't reach; distinct from [[delegate-task]] (MCP-tool delegation) and [[using-tasks]] (board mechanics); RED 3-baseline / GREEN 2-verify per writing-skills; ground truth = `status-md.ts` + `claim.ts` + `fleet-router.js`
-
-## Packages
-
-<!-- (none yet) -->
-
-## Sources
-
-<!-- (none yet) -->
+**Не читать. Не править.** Канон — mappa (`mcp__mappa__*`): wiki-сущности проекта, конвенции — AGENTS-сущность. Скил: `mappa-knowledge`.

.wiki/log.md

@@ -1,80 +1,3 @@
-# Wiki Log
+# ⛔ Файловый канал закрыт
 
-Append-only operation log. One entry per operation. Format:
-
-```
-## [YYYY-MM-DD] <op> | <one-line description>
-```
-
-Operations: `init`, `ingest`, `query`, `lint`, `refactor`, `decision`.
-
-Parseable: `grep "^## \[" .wiki/log.md | tail -20`.
-
----
-
-## [2026-04-28] init | bootstrap empty wiki via project-bootstrap (old layout)
-## [2026-04-28] decision | repo-layout — flat `skills/`, committed `dist/`, bash + PS scripts
-## [2026-04-28] decision | build-notes — PS 5.1 Compress-Archive backslash bug; build.ps1 via .NET ZipArchive
-## [2026-04-28] decision | active-platform — skill chosen over global CLAUDE.md / project memory; default Windows; wired into project-bootstrap
-## [2026-04-28] refactor | wiki-realignment — fixed project-bootstrap Step 3 to create Karpathy-canonical layout
-## [2026-04-28] refactor | this repo's `.wiki/` migrated to canonical layout (SUMMARY.md→index.md, source/→concepts/, added log.md/overview.md/CLAUDE.md schema, raw/README.md)
-## [2026-04-28] decision | context7-setup — switched to official plugin; --api-key injected into plugin's .mcp.json; three manual MCP entries removed
-## [2026-04-28] decision | setup-context7 skill — formalized the install/migrate algorithm; using-context7 gets a Prerequisites pointer; build.sh PS multi-arg bug fixed (loop instead of comma-joined -Names)
-## [2026-04-28] verify | setup-context7 — Vitya ran using-context7 in a session that needed setup; Prerequisites pointer triggered setup-context7; full flow worked end-to-end. Pattern (policy + setup split) validated.
-## [2026-04-28] decision | skill-vs-plugin — documented when a bare skill suffices vs when a plugin is required (slash commands, hooks, sub-agents, MCP via marketplace)
-## [2026-04-28] decision | skill-versioning — added `version: 1.0.0` to 6 infra skills' frontmatter; project-bootstrap now writes .wiki/concepts/bootstrap-manifest.md per project
-## [2026-04-28] refactor | wiki split — `wiki-maintainer` renamed to `using-wiki` (policy); new `setup-wiki` skill owns greenfield creation and canon migration; `project-bootstrap` Step 3 delegates
-## [2026-04-28] refactor | tasks split — `task-status-wiki` renamed to `using-tasks` (policy); new `setup-tasks` skill owns greenfield + interactive migration (no auto-parsing of old flat STATUS.md); `project-bootstrap` Step 4 delegates
-## [2026-04-28] refactor | this repo's `.tasks/` migrated to canonical layout — flat `## Done`/`## Backlog` replaced by emoji-status board (7 ⚪ Ready blocks); historical Done entries dropped (preserved in git log); `.bak` ignored via .gitignore
-## [2026-04-28] cleanup | removed stale `~/.claude/skills/{wiki-maintainer,task-status-wiki}/` installs (replaced by `using-wiki`/`using-tasks`); 16 skills installed, no duplicates; context7 plugin (mcp__plugin_context7_context7__*) confirmed live after restart
-## [2026-04-28] decision | install-portability — `install.sh`/`build.sh` patched to drop `mapfile`+`find -printf`; stock macOS (bash 3.2 + BSD find) now works; verified on git-bash (16 skills discovered, sorted, installed; build.sh produces archive)
-## [2026-04-29] decision | projects-meta-skills — built `setup-projects-meta` (8-phase install of projects-meta-mcp + auth.toml + MCP registration) and `using-projects-meta` (runtime policy with local-first rule and two-step mutation); skill pair pattern applied for the 4th time (context7 / wiki / tasks / projects-meta); both built + installed; visible to the harness
-## [2026-04-30] refactor | projects-meta-skills — wiki path canon corrected: `~/projects/.wiki` → `~/projects/projects-wiki/` (clone root), content at `~/projects/projects-wiki/.wiki/`. Old path caused write/read mismatch bug (fixed upstream in commit `621a69f` of `projects-meta-mcp`). Setup-projects-meta Phase 1 now detects legacy clone, Phase 4 re-clones to canon. Lesson: pull shared resources before relying on cached anchors
-## [2026-04-30] decision | using-projects-meta v1.1.0 — added mandatory Step 0 freshness gate: probe `meta_status`; if cache_age > 10min or errors > 0, `node dist/sync.js`; for shared-wiki writes unconditional `git -C ~/projects/projects-wiki pull --ff-only`; 401/403 → loud failure to user. Codifies the same-session lesson — `projects-meta` is a multi-machine bus, stale cache breaks read accuracy and write atomicity
-## [2026-04-28] decision | project-bootstrap@1.1.0 — added Step 5.6: detects `superpowers@claude-plugins-official` via `~/.claude/plugins/installed_plugins.json` and prints install command + upstream link if missing; chat-only, never auto-installs (slash commands aren't callable from a skill, and silent plugin install is overreach)
-## [2026-04-28] doc | README.md + README.ru.md — new "Using skills in projects" / "Использование в проектах" section after install quick-start; describes project-bootstrap workflow (git, .gitignore, README, .wiki/, .tasks/, CLAUDE.md, manifest, superpowers-plugin check) and the init/upgrade modes
-## [2026-04-30] refactor | project-bootstrap re-run on this repo (upgrade mode) — setup-wiki noop, setup-tasks noop, CLAUDE.md unchanged (matches template), bootstrap-manifest.md written: project-bootstrap@1.1.0 / setup-wiki@1.0.0 / setup-tasks@1.0.0
-## [2026-04-30] decision | project-bootstrap@1.2.0 — CLAUDE.md template gains `check across all projects` (verbatim trigger from using-projects-meta description); installs auto-load cross-project tasks + shared-wiki access in every bootstrapped repo; no Step 5.7 dependency-check mirror — Prerequisites pointer in using-projects-meta is self-correcting; local CLAUDE.md, both READMEs, dist/.skill, projects-meta-skills concept page synced
-## [2026-04-30] decision | Step 5.7 mirror of Step 5.6 (projects-meta-mcp dependency detector / `setup-projects-meta` recommendation) accepted as future work; tracked as ⚪ Ready task `[bootstrap-recommend-projects-meta]`; deferred until first observed fresh-machine miss so detector signal is informed by real failure mode; concept page `projects-meta-skills.md` updated to reflect new stance
-## [2026-04-30] decision | project-bootstrap@1.3.0 — Step 5 upgrade path turned idempotent: read existing CLAUDE.md → substring-diff vs template → confirm → append-only-missing; closes silent gap where pre-1.2.0 projects never picked up new canonical triggers (`check across all projects`, `we're on Windows`); platform line preserved if user pinned a non-host one; concept page `bootstrap-claude-md-merge.md` written; README CLAUDE.md row updated to note idempotent merge
-## [2026-05-01] decision | pulling-before-work — new policy skill (v1.0.0): one `git pull --ff-only` at session start + on-demand re-sync; bootstrap template gains canonical trigger; project-bootstrap 1.3.0→1.4.0
-## [2026-05-01] decision | project-discipline — new policy skill (v0.1.0): four cross-project rules (conventions-over-defaults, master-only, semver-bumping, ask-before-push); bootstrap template gains canonical trigger; project-bootstrap 1.4.0→1.5.0; skill-versioning concept extended to all skills
-## [2026-05-01] ingest | shared-wiki packages/claude-skills — каталог всех 20 скиллов опубликован в projects-wiki (3 commits: page + index + log on Gitea, ae2cc9a..001cdd0); группировка bootstrap / wiki+tasks / MCP / caveman / discovery+platform; cross-link с concepts/setup-using-skill-pair и packages/projects-meta-mcp
-
-## [2026-05-05] ingest | concepts/interns-design
-## [2026-05-05] decision | interns-skills-mvp — shipped `setup-interns` v0.1.0 (8-phase install: detect `.common/lib/interns-mcp/`, `pip install -e`, `.common/secrets/interns.env` write, `mcpServers.interns` registration with absolute Python interpreter + `cwd`) and `using-interns` v0.1.0 (runtime policy mirroring project-discipline Rule 4: ask-mode default, conversational grant/revoke, always-ask paths for `.env`/secrets/keys/SSH/credentials with transitive rule, cost-cap >$0.10, session-end reset; routing hints for `bulk_text_read` + `transcript_distill`); `project-bootstrap` 1.5.0→1.6.0 with canonical CLAUDE.md trigger `delegate to interns when allowed` between `follow project discipline` and `we're on Windows`, Step 5 commentary paragraph, manifest table extended with both new skills + `project-discipline` row; root `CLAUDE.md` dogfood updated; both READMEs written; descriptions verified (setup-interns 899 chars, using-interns 814 chars, both under 900 budget); all three rebuilt + installed + listed by harness with full descriptions (no H1 fallback)
-## [2026-05-05] ingest | concepts/bootstrap-skill-deps-check
-## [2026-05-05] decision | bootstrap-skill-deps-check — `project-bootstrap` 1.6.0→1.7.0 collapses Step 5.6 from a single-skill detector (only `superpowers` plugin) into a generic `trigger → fulfiller` table walker. Map embedded in SKILL.md (9 rows: caveman, superpowers plugin, using-wiki, using-tasks, using-projects-meta, pulling-before-work, project-discipline, using-interns, active-platform); `kind: skill` vs `kind: plugin` flag drives the install command emitted in the recommendation block. Algorithm: read project's CLAUDE.md → match each line vs map (substring + tolower, mirrors Step 5 idempotent merge) → for each canonical match check disk (`~/.claude/skills/<name>/SKILL.md` or `installed_plugins.json` key); print one chat-only block listing every missing fulfiller + install commands, or one ✅ line if all satisfied. User-custom lines silently skipped; removed canonical lines silently skipped (respects user opt-out). Hard rule "never auto-install" carries over verbatim. Subsumes the deferred `[bootstrap-recommend-projects-meta]` task (closed by absorption — generic step handles `using-projects-meta` along with everything else). MCP-server-backed skills only check the `using-X` policy skill; `setup-X` self-fires on first use via Prerequisites pointer, bootstrap doesn't duplicate.
-## [2026-05-05] decision | compress-dedup — `skills/compress/` was a stripped-down byte-for-byte dupe of `skills/caveman-compress/` (scripts/ identical SHA256 across all 7 files; SKILL.md diff = `name:` + Process step 2; descriptions textually identical = arbitrary harness tie-break + double-counted listing budget). Kept `caveman-compress` canonical: it carries README.md (benchmarks table + caveman-toolkit branding) and SECURITY.md (Snyk false-positive writeup), and matches the caveman-* prefix invariant. Ported the better Process-step wording from `compress` into `caveman-compress` (`cd <directory_containing_this_SKILL.md>` instead of brittle `cd caveman-compress` which assumes cwd). Added `version: 1.0.0` to caveman-compress frontmatter (first versioned release; aligns with skill-versioning concept). Deleted: `skills/compress/`, `dist/compress.skill`, `~/.claude/skills/compress/` (manual prune — install.sh has no prune step; future `[install-ps1]` task should add `--prune` flag). Rebuilt + reinstalled `caveman-compress`. Slash-command impact: `/compress` removed; `/caveman-compress` + `/caveman:compress` (toolkit-canonical) remain. Concept page `concepts/compress-dedup.md` written (rationale + rejected alternatives: alias-stub has no harness mechanism; "keep both" wastes listing budget; "delete caveman-compress" loses README + SECURITY).
-## [2026-05-05] design | active-platform-eval (paused) — combined `[active-platform-tuning]` + `[active-platform-eval]` into one workstream (eval *is* the tuning mechanism; "wait for 5 real signals" was a placeholder). Spec written at `.wiki/concepts/active-platform-eval-design.md`: 20-query trigger eval set balanced ≥3 should-trigger per OS (Win/Lin/Mac) + near-miss negatives, run in `skill-creator/scripts/run_loop.py` (5 iter, train/test split, model `claude-opus-4-7`) **in parallel** with manual body sweep (WSL clarity, BSD/macOS expansion, ambiguity policy). Workspace at `.tasks/active-platform-eval/` (eval-set.json committed, iterations gitignored). Version bump 1.0.0 → 1.1.0 planned (MINOR). Pre-flight verified: `claude` CLI at `C:\nvm4w\nodejs\claude.ps1` (Claude Code 2.1.128) + `run_loop.py` present in skill-creator install — both autoloop deps satisfied, no fallback needed. Per-task file at `.tasks/active-platform-eval.md`. Paused at user request before eval-set authorship; resume point is Q2 (write 20 queries solo vs run skill-creator HTML-review template for user edits first). Also fixed in same pause: `[install-ps1]` STATUS scope expanded to "paired install.sh + install.ps1, cross-platform parity, --prune flag" (lesson from `[compress-dedup]`).
-
-## [2026-05-05] ingest | concepts/interns-repo-read-design
-
-## [2026-05-06] ingest | concepts/hermes-skills-rollout-design
-
-## [2026-05-07] ingest | concepts/tdd-criteria-design
-
-## [2026-05-07] review | tdd-criteria v0.2.0 — 4 findings applied: trigger-loophole fix (removed session-authorship clause), composite-tasks + refactoring sections, expanded file-extension list, clarified wrapper line-count + spike-survivor fallback + foreign-schema fix; design doc synced
-
-## [2026-05-10] decision | project-bootstrap-meta-isolation — v1.11.0 ships meta-isolation block in `.gitignore` template + Step 1 upgrade-case append; restores agent meta-paths visibility against global `core.excludesFile`; smoke-tested greenfield + negative control + idempotency
-
-## [2026-05-22] ingest | concepts/interns-grep-audit-design
-
-## [2026-05-25] decision | session-handoff-skill-design — design rationale for the `session-handoff` skill captured in wiki after cluster 7/7 closure; sliding overwrite of `.tasks/NEXT_SESSION.md`, phrase whitelist + substantive-commit heuristic, opt-in PostToolUse hook, orient+ask default, source: `~/projects/.workshop/.archive/2026-05-24-session-handoff-skill.md` Round 1 + Round 2
-
-## [2026-05-25] decision | install-cross-platform — `install.{ps1,sh}` paired-script parity contract documented; `--prune` / `-Prune` flag rationale (combined-with-install, global-scan ignores names filter, default-off, print-and-delete no prompt); shipped in commit `6cf0e98` with `[skip-tdd: wrapper]` carve-out + smoke-test evidence; closes 2/3 of `[install-ps1]` acceptance (the doc + flag), `dist/`-prune analogue deferred to `build` scripts
-
-## [2026-05-25] decision | install-cross-platform extended to build scripts — `build.{ps1,sh}` get the symmetric `--prune` / `-Prune` flag (removes `dist/<name>.skill` where `<name>` is not in `skills/`). Bash delegation to `powershell.exe -File build.ps1` does NOT forward the flag — bash runs prune itself against the shared `dist/`. Both paths smoke-tested with fake stale .skill files against real dist/. Closes `[install-ps1-build-prune-followup]`.
-
-## [2026-06-09] decision | delegate-task-negative-trigger-fp — `delegate-task` 0.2.0→0.2.1 (PATCH): fixed 5/5-consistent false-positive on «создать задачу себе». Root cause: self-task phrase shares stem «создать задачу» with the «создать задачу на агента» positive trigger; the abstract "Does NOT apply when doing the work yourself" carve-out can't beat a literal stem-match under the 1%-rule. Fix: made the negative literal + routed («создать задачу себе» / «task for myself» / «поставить себе задачу» → using-tasks) in description + body disambiguator («на агента»/«агенту» = delegate; «себе» = own board). Re-verified via fresh-context subagent trigger run: positives 5/5 (no regression), negative 4/5 → using-tasks (was 0/5); the 1 residual miss was an eval-harness artifact (forced skill-name-before-reasoning), not description ambiguity. Concept page written; reusable principle = put the exact colliding negative phrase with an explicit →sibling route, literal beats abstract.
-## [2026-06-09] decision | delegate-task-session-break — `delegate-task` 0.2.1→0.2.2 (PATCH): authoring side of the `session_break` marker (consumer = using-tasks v1.2.0). Added pre-flight Q6 (after notify): "Session-break после этой задачи? (domain-switch / milestone / heavy infra)"; if yes → set optional template field `session_break: true | "<hint>"` (trailer, next to weight/notify/allow_upgrade; same lowercase frontmatter key using-tasks reads). Usage guidance lists three set-it cases; What-NOT-to-do bullet warns against setting it routinely (it's a real-boundary marker, not a default). Wiki concept page concepts/delegate-task-session-break.md + index. Pairs with using-tasks-session-break.
-## [2026-06-09] decision | using-system-snapshot — new skill v0.1.0: thin read-only wrapper over the single `mcp__projects-meta__meta_system_snapshot` call (poller status + local docker containers + cached cross-project task summary). Replaces the scatter of `tasklist` + `docker ps` + manual `meta_status`. Core rule: no claim about poller / local-docker / task-load state without calling the tool in the current turn (memory + stale earlier snapshot ≠ evidence). Output = three lines, one per section (docker lists only problem containers; tasks gives Σ active/blocked + busiest 2–3). Liveness split documented: poller+docker live, tasks from cache (defer precise work to using-projects-meta Step 0). Scope boundaries: deep single-container diagnosis → using-vds-ops / `docker logs`; docker section is LOCAL, not the VDS. Read-only, no per-session grant (mirrors using-vds-ops). Output shape verified by a live call 2026-06-09. Concept page concepts/using-system-snapshot-design.md + index. TDD N/A (markdown policy artifact); behavioral smoke-test = paired skill-using-system-snapshot-review task.
-## [2026-06-09] review | using-system-snapshot v0.1.0 — VERDICT PASS on all 3 acceptance criteria (skill-using-system-snapshot-review). Tool contract verified by a live `meta_system_snapshot` call (output matches the documented `poller`/`docker`/`tasks` shape exactly). Behavioral trigger smoke = 9 fresh-context subagents over a simulated registry (real descriptions + using-vds-ops/using-projects-meta/using-tasks competitors, no expected-answer hint): 4/4 positives → using-system-snapshot; VDS-logs → using-vds-ops; mutate/full-board → using-projects-meta; `docker-compose.yml` edit → none (no FP on "docker" keyword). No-claim-without-snapshot rule explicit in 4 places; three-line output format confirmed achievable against the live payload. 3 informational findings (none blocking): (1) cross-project task-COUNT phrasings overlap with using-projects-meta — by-design, snapshot defers precise per-task work; (2) LOCAL-container deep diagnosis is unowned — vds-ops incident triggers grab local containers its VDS-only tools can't reach (vds-ops scoping, not this skill); (3) deployment scaffold missing — skill committed but not installed to `~/.claude/skills/`, not in `hermes/mapping.yaml`, no -install/-hermes-mapping/-test-trigger baseline tasks; recommended follow-ups (hermes mode could be `auto`, read-only skill). Review outcome appended to concepts/using-system-snapshot-design.md.
-## [2026-06-09] decision | using-tasks-status-archival — `using-tasks` 1.2.0→1.3.0 (MINOR): added done-task archival rule to fix STATUS.md bloat ("huge STATUS.md" complaint). When ≥10 🟢 done blocks pile up — checked at session start (step 7) and after close (Task completion step 7) — move them verbatim to `.tasks/archive/YYYY-MM.md` (append, one file per month, one-time header), leaving only 🔴/🟡/⚪/🔵 on the board; committed on its own. Did NOT follow the task's literal instruction to replace `Read STATUS.md` with `tasks_get_status` for orientation: that tool returns a single task's live status by known slug (`{status, found}`) and cannot enumerate the board, and `tasks_aggregate` is cross-project + cache-based + doesn't index ready/done (its docs say read STATUS.md directly for the current project). So orientation stays a local board-read (kept cheap by archival); skill now warns against both tools for board enumeration and points `tasks_get_status` at its real single-task use. Core goal (kill the bloat) met by archival alone. Concept page concepts/using-tasks-status-archival.md + index. TDD N/A (markdown policy). Deviation flagged for paired review task using-tasks-status-read-perf-review.
-## [2026-06-09] decision | using-tasks-session-break — `using-tasks` 1.1.0→1.2.0 (MINOR): added the `session_break` marker. Task author sets `session_break: true | "<hint>"` in task frontmatter (mirrored as `**Session break:**` on the local board); after the task closes 🟢, before `tasks_claim_next`, an autonomous agent prints the verbatim line `🔚 SESSION BOUNDARY — [slug] закрыта. Рекомендую завершить текущую сессию. Следующий трек: [value | "см. STATUS.md"]` and stops instead of chaining the next task. Absent → behaviour unchanged. Enforced in Task completion step 6 + Rules bullet + format docs. Marker not heuristic: the stop-point is an authoring choice, not a runner guess.
-## [2026-06-09] review | using-tasks-status-archival v1.3.0 — VERDICT PASS 3/3 (using-tasks-status-read-perf-review). Criterion «ориентация через `tasks_get_status`, не Read» is satisfied by a **validated deviation**, not a literal swap: re-verified against the live tool schema that `tasks_get_status(target_project, slug)→{status, found}` takes a required slug and returns ONE task — it cannot enumerate the board, so it cannot drive orientation; the implementer correctly rejected the impossible instruction and fixed the real problem (bloat→archival). No regression: orientation still reads local STATUS.md (Session start §2) and the «what's next» flow still reads the board — change is purely additive. Archival rule clear & complete (≥10 threshold, two trigger points, monthly append-only archive, verbatim blocks, dedicated commit, cross-referenced). One informational non-blocking note: this repo's own STATUS.md (>10 🟢) would itself trip the rule — dogfooding tracked separately as tasks-board-cleanup-2026-05. No follow-up tasks. Verdict appended to concepts/using-tasks-status-archival.md.
-## [2026-06-09] decision | delegate-task-review-weight — `delegate-task` 0.2.2→0.2.3 (PATCH): Step 5 (paired `<slug>-review` task) now sets an explicit `weight`, inherited from the impl-task with a `needs-claude` floor (impl `needs-human`→review `needs-human`; `needs-claude`→`needs-claude`; `cheap-ok`→`needs-claude`). Root cause of commit `c0af151` ("add Weight: needs-claude to 4 review tasks — reconciler was skipping them"): the authoring skill omitted `weight` on review tasks, making them invisible to fleet routing. Floor (not pure inheritance) chosen to stay internally consistent with the skill's own "What NOT to do" bullet that forbids `cheap-ok` for review tasks — a `cheap-ok` impl would otherwise propagate a forbidden `cheap-ok` review. Added a What-NOT-to-do bullet against weightless review tasks. Concept page concepts/delegate-task-review-weight.md + index. TDD N/A (markdown policy artifact).
-## [2026-06-11] decision | task-format — new skill v0.1.0: public reference for the `.tasks/STATUS.md` task-block format the autonomous poller parses. Motivation: the field rules (`**Weight:**` capability/cost tier, `**Notify:** <owner>/<repo>` inbox target, header regex, status emoji) lived only in internal sources (`projects-meta-mcp/src/lib/status-md.ts` parser + `status-md-writer.ts` + `.common/.wiki/concepts/agents-task-runner-ops.md`); skills ship with `factory` to external users, the wiki/MCP-source don't. Scope kept distinct from delegate-task (creates tasks for others via `tasks_create`, the tool emits the format) and using-tasks (board claim/close mechanics) — task-format is the byte-level field reference for hand-edited blocks. Ground truth verified against source: header `/^##\s+(\S+)\s+\[([^\]]+)\]\s+—\s+(.+)$/u`; Weight ∈ {cheap-ok, needs-claude, needs-human}; claim gate excludes only `needs-human` (`claim.ts`), but a *missing* Weight finds no backend tier (`fleet-router.js` resolveBackend) → poller parks to 🔵 blocked, so Weight is operatively required for pickup. TDD per writing-skills: RED = 3 baseline subagents w/o skill (2/3 used `###`/bullet headers the parser can't recognize, 2/3 omitted Weight inventing `risk`/`tier`/`claimable-by`, 2/3 put notify in prose, 1/3 used 🟢 for ready); GREEN = 2 fresh subagents w/ skill, both parser-valid incl. correct `needs-human` for the critical-infra scenario; REFACTOR = no new loopholes. Reference skill ~900 words (loads only when authoring a task block). Concept page concepts/task-format-design.md + index. Not yet installed to `~/.claude/skills/` or added to hermes mapping — deferred follow-up (mirrors using-system-snapshot deployment-scaffold note).
-## [2026-06-09] decision | using-markitdown-cli-migration — `using-markitdown` 1.0.0→1.0.1 (PATCH): rewrote the skill from the Docker-based `mcp__markitdown__convert_to_markdown` MCP tool to the native `markitdown` CLI (v0.1.6, on PATH). Tool block now `markitdown <path|url>` → stdout (or `-o file`); removed the whole "Docker-mount caveat (READ FIRST)" section (host→container `file://` translation + `[Errno 2] /c:/Users/...` symptom are gone — CLI sees the full host FS). Updated the ingest pattern (use `-o` straight into `.wiki/raw/`), the gotchas table (`command not found` → check `markitdown --version`, install `pip install markitdown[all]`; dropped the MCP "tool not available / ToolSearch" row), and the contrast-table header (CLI, not MCP). Description frontmatter (the WHEN-to-use triggers) left unchanged. Container decommission: the task's literal `docker stop/rm markitdown-mcp` had no target — no container is named that; the MCP spawns anonymously-named containers from `markitdown-mcp:latest` per session (3 had piled up). Removed all by image ancestor (`docker rm -f $(docker ps -aq --filter "ancestor=markitdown-mcp:latest")`), verified none remain. Left the `mcpServers.markitdown` entry in `~/.claude.json` untouched (out of scope; a container will respawn next session until it's deregistered — flagged as a follow-up). Concept page concepts/using-markitdown-cli-migration.md + index. TDD N/A (markdown skill).
-## [2026-06-17] decision | session-inbox-monitor-received-msg-fp — finding from `session-inbox-monitor-test-trigger` (VERDICT PASS, clean session, 7 unprimed clean-context subagents: pos 4/4 incl. CLAUDE.md-line P4, neg 2/3). The 1 FP: RU «обработай полученное письмо из инбокса» (N1) routed to `session-inbox-monitor`; the EN twin (N3) and the multi-machine-backend negative (N2) routed to `none` cleanly. Root cause = a new dimension on top of [[delegate-task-negative-trigger-fp]]: the carve-out is already literal+routed (`NOT for handling a received message → inter-session-peer-discipline`), but the route target `inter-session-peer-discipline` is **not installed** → no real competitor, so the nearest in-domain skill (session-inbox-monitor) wins by default; non-deterministic, self-corrects on body-load (cost = one wasted skill-load, not a wrong action; isomorphic to [[using-tasks-session-break]] session_break). New page concepts/session-inbox-monitor-received-msg-fp.md + bidirectional link from concepts/delegate-task-negative-trigger-fp.md + index. New reusable principle: a routed negative competes only if its route target is installed. Status OPEN — follow-up task session-inbox-monitor-received-msg-fp (options a: harden description / b: install sibling / c: accept informational). Not a memory entry by owner direction — knowledge belongs in the project wiki.
-## [2026-06-17] decision | session-inbox-monitor-received-msg-fp RESOLVED via option (b) — installed `inter-session-peer-discipline` (existed in sources since 2026-06-16, was not installed → exact root cause confirmed). install.ps1 -Names, byte-identical parity. FP-twin verified clean: fresh clean-context subagent on the N1 phrase now routes to inter-session-peer-discipline (IN_REGISTRY: yes), not session-inbox-monitor — carve-out now has a real competitor. session-inbox-monitor description untouched (option (a) rejected as whack-a-mole; (c) as latent hole). Governance: peer workshop proposed (b) as a "ruling"; per the freshly-installed [[inter-session-peer-discipline]] (peer = proposal not authority, scope needs human ratification) it was surfaced as a recommendation and ratified by the user — live dogfood of the skill's own purpose. concepts/session-inbox-monitor-received-msg-fp.md Status section updated open→resolved. Tail: inter-session-peer-discipline now installed but not in hermes/mapping.yaml — possible red build, flagged as separate follow-up.
+**Не читать. Не править.** Канон — mappa (`mcp__mappa__*`): wiki-сущности проекта, конвенции — AGENTS-сущность. Скил: `mappa-knowledge`.

.wiki/overview.md

@@ -1,29 +1,3 @@
----
-title: claude-skills overview
-type: overview
-updated: 2026-04-28
----
+# ⛔ Файловый канал закрыт
 
-# claude-skills — overview
-
-Joint workshop where Vitya and Claude develop, test, and store Claude skills. Both editable sources (`skills/<name>/`) and built archives (`dist/<name>.skill`) live here, so a fresh machine can clone the repo and install every personal skill in one command.
-
-## Components
-
-- **`skills/`** — editable skill sources, one folder per skill (each with `SKILL.md` + optional `assets/`).
-- **`dist/`** — built `.skill` archives, committed so installs don't need a build toolchain on the target.
-- **`scripts/`** — `build.sh` / `build.ps1` (zip sources → archive), `install.sh` (copy sources → `~/.claude/skills/`).
-- **`.wiki/`** — Karpathy LLM Wiki for design decisions and gotchas. See [CLAUDE.md](CLAUDE.md) for schema.
-- **`.tasks/`** — task board (`STATUS.md`).
-- **`CLAUDE.md`** — repo-level agent instructions (skill triggers).
-
-## Where to look
-
-- New here? → [concepts/repo-layout.md](concepts/repo-layout.md), then `README.md`.
-- Working on a skill? → edit `skills/<name>/`, then `bash scripts/install.sh <name>` (or `pwsh scripts/build.ps1 <name>` to refresh the archive).
-- Tracking work? → [.tasks/STATUS.md](../.tasks/STATUS.md).
-- Made a non-trivial decision? → add a `concepts/<topic>.md` page, link from [index.md](index.md), append a line to [log.md](log.md).
-
-## Cross-references
-
-This page intentionally stays short. The substantive material lives in `concepts/` (decisions, gotchas) and the [index](index.md) catalog.
+**Не читать. Не править.** Канон — mappa (`mcp__mappa__*`): wiki-сущности проекта, конвенции — AGENTS-сущность. Скил: `mappa-knowledge`.

AGENTS.md

@@ -8,8 +8,27 @@ check across all projects
 pull remote before work
 session handoff: read on start, write on end
 inbox monitor: raise on start
+session sync: write to mappa
 follow project discipline
 follow tdd-criteria
 delegate to interns when allowed
 recommend, don't menu
 we're on Windows
+mappa sync: run on start
+
+<!-- mappa:canon-block (auto; do not edit) -->
+## Mappa canon
+**Gates (canon/gates — shared):** краткая суть; полный текст — `wiki_get(slug='canon/gates', full=true)`
+- Г1. Знание и артефакты → mappa, не файлы — durable-знание и артефакты проекта живут в mappa; файловые каналы (`.brainstorm/`, `.tasks/`, `.wiki/`) и «сохранить рядом с проектом» закрыты.
+- Г2. Контракт каналов — письмо (inbox) — носитель вердиктов/указаний/находок, полным телом; комментарии на тасках — короткий след. Адресация `about`/`to`/`thread` (XOR); lifecycle `ack`/`resolve`/`cancel`.
+- Г3. Поиск до угадывания — не угадывать slug/роут: сначала `search`/`wiki_search`; `wiki_get` без project = shared; общая память — `search(mode='recall')`.
+- Г4. Адресация и слаги — рефы полными именами (`[[task:N]]`/`[[wiki:slug]]`); слаги kebab-case, латиница; номера `task:N` выдаёт сервер.
+- Г5. .mappa-гейт — папка участвует в mappa-операциях только с маркером `.mappa`; нет маркера → сказать человеку, мутации — отказ.
+- Г6. Секреты — в mappa не пишутся (422); только `secret:<path>`-рефы, значения мимо.
+- Г7. Degraded-режим — mappa недоступна: читать кэш `.mappa/` (canon/methodology/runbooks), мутации → `.mappa/pending/`; нет кэша → стоп, не импровизировать.
+- Г8. Перед работой с вики/каноном — первым действием прочитать канон-блок AGENTS.md проекта.
+- Г9. Живое состояние до заявления — статус заявлять только по свежему чтению mappa, не по памяти/кэшу/ответу create.
+**Entity → runbook (runbooks/index — shared):** task → [[runbooks/tasks]] · wiki → [[runbooks/wiki]] · inbox → [[runbooks/inbox]] · **thread** → [[runbooks/threads]] · session → [[runbooks/session]] · search → [[runbooks/search]] · issue → [[runbooks/issue]] · **intent** → [[runbooks/intent]] · requirements → [[runbooks/requirements]] · plan → [[runbooks/plan]] · comment → [[runbooks/comment]] · tag → [[runbooks/tag]] · attachment → [[runbooks/attachment]] · release → [[runbooks/release]] · brainstorm → [[runbooks/brainstorm]] · agent → [[runbooks/agent-operator]] · repo → [[runbooks/repo-commit]] · project → [[runbooks/project]] · skill → [[runbooks/skill]] · entity-слой → [[runbooks/entity]] · sched → [[runbooks/sched-telemetry]]
+**Methodology:** `methodology/kzntsv`
+**Canon version:** 4
+<!-- /mappa:canon-block -->

README.md

@@ -25,8 +25,8 @@ A shared workspace where Claude and I author, debug, and ship skills together:
 git clone <repo> skills
 cd skills
 bash scripts/install.sh           # copies every skills/* into ~/.claude/skills/
-# or only specific ones:
-bash scripts/install.sh using-wiki caveman
+# or only specific ones (mappa-* skills install from the `mappa` repo — see mappa-bootstrap):
+bash scripts/install.sh caveman tdd-criteria
 ```
 
 **Linux / macOS (bash):**
@@ -35,8 +35,8 @@ bash scripts/install.sh using-wiki caveman
 git clone <repo> skills
 cd skills
 bash scripts/install.sh           # copies every skills/* into ~/.claude/skills/
-# or only specific ones:
-bash scripts/install.sh using-wiki caveman
+# or only specific ones (mappa-* skills install from the `mappa` repo — see mappa-bootstrap):
+bash scripts/install.sh caveman tdd-criteria
 ```
 
 The install target can be overridden with `CLAUDE_SKILLS_DIR=/path bash scripts/install.sh`.
@@ -52,10 +52,9 @@ project's folder and it will, in one pass:
 
 - initialize `git` (if missing) and write a sane `.gitignore`
 - create a starter `README.md`
-- lay out `.wiki/` per the [Karpathy LLM Wiki pattern](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) (delegated to [`setup-wiki`](skills/setup-wiki/))
-- lay out `.tasks/` with the canonical task board (delegated to [`setup-tasks`](skills/setup-tasks/))
+- register the project meta in **mappa** (wiki/task-сущности проекта; file-based `.wiki/`/`.tasks/` closed 2026-08-25)
 - write `AGENTS.md` (canon) with skill triggers (`use project wiki`, `use task management system`, `check across all projects`, `we're on Windows`) plus a `CLAUDE.md` legacy pointer
-- record the skill versions used in `.wiki/concepts/bootstrap-manifest.md` so cross-project layout drift stays debuggable
+- record the skill versions used in a mappa wiki entity (`concepts/bootstrap-manifest`) so cross-project layout drift stays debuggable
 
 Two modes, picked automatically: **init** for an empty folder, **upgrade**
 for an existing project (the skill only fills the gaps and never overwrites
@@ -119,8 +118,14 @@ an explicit `adapted-from` marker in its frontmatter.
 | `loop-me` | `adapted-from: mattpocock/skills @ 84fdeffd` (MIT) — workflow-spec design gate |
 | `review-kit-pi-method` | `author: ours` — pi-native spawn for clean-context review subagents |
 | `command-index` | `author: ours` — just/Makefile command-index convention (standard targets, auto-doc; idea 3/18) |
+| `code-search` | `author: ours` — rg-first code search (measured 15 min → 0s; routing: rg / git grep / interns repo_read / grep_audit) |
 | `code-review` | `adapted-from: mattpocock/skills @ 84fdeffd` (MIT) — two-axis + Fowler baseline; output: caveman-review format |
 | `writing-skills` | `adapted-from: obra/superpowers @ 6.2.0` (MIT) — TDD-for-skills core + ideya 8 self-skill-authoring |
+| `web-search` | `author: ours` — search_web tool (pi-extension) + policy: when to search, «без поиска» session-off |
+| `ops-browser` | `author: ours` — свой **скрытый** браузер агента: отдельный профиль + CDP (`eval`/`fetch` из страницы/скриншоты), `handoff` человеку для пароля/капчи; свой замок `ops.lock` |
+| `browser-operator` | `author: ours` — браузер ОПЕРАТОРА (его Chrome/логины): канал по харнессу (Hermes `browser_exec` / pi тул `browser` / CC `chrome-devtools`), аренда «один водитель за раз», границы «человек vs агент», рецепты тяжёлых страниц. Закрывает провал базового прогона 2026-09-11 («куки из Chrome + curl + ввод пароля» мимо канала); анонимные прогоны — `browser-cdp` |
+| `review-subagent` | `author: ours` — review_subagent tool (pi-extension): clean-context review by your own model, optional `model` override |
+| `report-mappa-issue` | `author: ours` — TEMPORARY stopgap: mappa deviation reporting (mail to `mappa` + `.workshop`) while the service is unstable; retire when stabilized |
 | all other `skills/*` | `author: ours` |
 
 Adaptation policy: a clone is rewritten to our conventions (`.tasks/` boards,
@@ -138,7 +143,7 @@ skills/
 │   ├── mapping.yaml        ← per-skill Hermes-rollout config
 │   └── skills/             ← `mode: manual` overrides (Hermes-flavour rewrites)
 ├── dist-hermes/            ← pre-converted Hermes-flavour tree (committed)
-│   ├── <category>/<name>/  ← e.g. software-development/pulling-before-work/
+│   ├── <category>/<name>/  ← e.g. software-development/diagnosing-bugs/
 │   └── SKIPPED.md          ← skip + pending log (auto-generated)
 ├── scripts/
 │   ├── build.sh / build.ps1

README.ru.md

@@ -21,8 +21,8 @@
 git clone <repo> claude-skills
 cd claude-skills
 bash scripts/install.sh           # копирует все skills/* в ~/.claude/skills/
-# или конкретные:
-bash scripts/install.sh using-wiki caveman
+# или конкретные (mappa-* скилы ставятся из репо `mappa` — см. mappa-bootstrap):
+bash scripts/install.sh caveman tdd-criteria
 ```
 
 Цель установки можно переопределить переменной `CLAUDE_SKILLS_DIR=/path bash scripts/install.sh`.
@@ -36,10 +36,9 @@ bash scripts/install.sh using-wiki caveman
 
 - инициализирует `git` (если ещё нет) и положит вменяемый `.gitignore`
 - создаст стартовый `README.md`
-- развернёт `.wiki/` по [паттерну Karpathy LLM Wiki](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) (делегируется в [`setup-wiki`](skills/setup-wiki/))
-- развернёт `.tasks/` с канонической доской задач (делегируется в [`setup-tasks`](skills/setup-tasks/))
+- зарегистрирует мету проекта в **mappa** (wiki/task-сущности; файловые `.wiki/`/`.tasks/` закрыты 2026-08-25)
 - запишет `AGENTS.md` (канон) со скилл-триггерами + `CLAUDE.md`-указатель (`use project wiki`, `use task management system`, `check across all projects`, `we're on Windows`)
-- зафиксирует версии использованных скиллов в `.wiki/concepts/bootstrap-manifest.md`, чтобы дрифт раскладки между проектами оставался отлаживаемым
+- зафиксирует версии использованных скиллов в mappa wiki-сущности `concepts/bootstrap-manifest`, чтобы дрифт раскладки оставался отлаживаемым
 
 Два режима, выбирается автоматически: **init** для пустой папки и **upgrade**
 для существующего проекта (скилл только дозаполняет пробелы и ничего не
@@ -89,8 +88,11 @@ bash scripts/build.sh caveman          # один
 | `loop-me` | `adapted-from: mattpocock/skills @ 84fdeffd` (MIT) — дизайн-гейт workflow-спец |
 | `review-kit-pi-method` | `author: ours` — pi-спавн чистых review-субагентов |
 | `command-index` | `author: ours` — конвенция just/Makefile command-index (стандартные таргеты, авто-док; идея 3/18) |
+| `code-search` | `author: ours` — rg-first код-поиск (замер: 15 мин → 0 сек; роутинг: rg / git grep / interns repo_read / grep_audit) |
 | `code-review` | `adapted-from: mattpocock/skills @ 84fdeffd` (MIT) — двухосевость + Fowler-база; формат вывода: caveman-review |
 | `writing-skills` | `adapted-from: obra/superpowers @ 6.2.0` (MIT) — TDD-for-skills ядро + идея 8 self-skill-authoring |
+| `ops-browser` | `author: ours` — свой скрытый браузер агента (профиль + CDP + `handoff` человеку, замок `ops.lock`) |
+| `browser-operator` | `author: ours` — браузер ОПЕРАТОРА (его Chrome/логины): канал по харнессу (Hermes `browser_exec` / pi тул `browser` / CC `chrome-devtools`), аренда «один водитель за раз», границы «человек vs агент»; анонимные прогоны — `browser-cdp` |
 | остальные `skills/*` | `author: ours` |
 
 Политика адаптации: клон переписывается под наши конвенции (доски `.tasks/`,

dist-hermes/SKIPPED.md

@@ -17,16 +17,11 @@ Do not edit by hand — edit the mapping and re-run the build.
 
 ## Pending (deferred to follow-up tasks)
 
-- **delegate-task** — Calls mcp__projects-meta__tasks_create to create tasks in other projects/agents (Gitea commit, cross-project side-effect). Behavioral audit via delegate-task-test-trigger required before promotion to auto. → intended: `mode: auto, category: mcp`
 - **meta-host-routing** — Resolves WHERE a project's meta lives before tasks_create / knowledge_ingest / brainstorm-promotion (meta-out-of-repo). Touches projects-meta MCP (tasks_create / knowledge_ingest / meta_status) and routes writes across repos. Review PASS (meta-host-routing-review) but the -install baseline is still open and a tool-side audit (cross-repo MCP writes) is required before auto. Mapping executes task meta-host-routing-hermes-mapping. → intended: `mode: auto, category: meta`
 - **private-dev-public-publish** — 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. → intended: `mode: auto, category: software-development`
 - **ralph-loop-execution** — Behavioral oracle-loop skill (Verifier / Attempts / Max-Attempts retry loop). NB: source SKILL.md currently lacks YAML frontmatter (no name/description) — cannot auto-convert cleanly until that is fixed. Mapped pending as a placeholder; needs frontmatter + a behavioral audit before any mode decision.
-- **session-handoff** — Writes .tasks/NEXT_SESSION.md (project-scope, sliding overwrite) and reads it on session start. Bidirectional file-system side-effect, opt-in via CLAUDE.md trigger-line. Behavioral audit via session-handoff-test-trigger required before promotion to auto. → intended: `mode: auto, category: productivity`
 - **session-inbox-monitor** — Paired SessionStart hook registers itself in ~/.claude/settings.json and sweeps orphaned monitor OS processes (Get-CimInstance | Stop-Process by sentinel+inbox-path); the skill then raises an in-session Monitor on .claude-inbox/. Primary activation is the CLAUDE.md trigger-line `inbox monitor: raise on start` + the injector, not a hermes-trigger. Behavioral gate CLEARED 2026-06-17 — test-trigger + review BOTH VERDICT PASS (activation 3/3 monitor + neg clean; structural hook audit 5 PASS/1 CONCERN, the CONCERN fixed in v0.2.2). STAYS pending on two independent tool-side blockers, NOT on behavioral verification: (1) the SessionStart hook is Windows-PowerShell and needs a Linux port for Hermes factory machines; (2) machine-level side-effects (user-config mutation of ~/.claude/settings.json + Get-CimInstance|Stop-Process kills) need a tool-side audit before auto. Promotion blocked on those two, not on test-trigger/review. → intended: `mode: auto, category: productivity`
 - **setup-agents-task-runner** — L2 installer — installs the standing-duty stack (agents-task-runner + watchdog + appeals-inbox) as platform-native OS services (systemd/launchd/winsw), fetches a pinned binary, writes poller-scope.json. Heavy infra side-effects (OS services + binary fetch); mode decision (skip vs manual vs auto) deferred — needs an explicit Hermes-factory applicability audit. Placeholder pending to keep the build green.
 - **task-format** — Documentational skill — how to write a .tasks/STATUS.md task block the autonomous poller will claim/route/report (block header, status emoji, Weight/Notify/Requirements fields). No tool-side effects; pending a behavioral test-trigger before auto. → intended: `mode: auto, category: productivity`
-- **task-loop** — 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. → intended: `mode: auto, category: mcp`
-- **using-system-snapshot** — Calls mcp__projects-meta__meta_system_snapshot (read-only whole-machine ops snapshot: poller / docker / cross-project task load). Read-only, same class as using-vds-ops / using-wiki-graph; pending a behavioral test-trigger before auto. → intended: `mode: auto, category: mcp`
 - **using-vds-ops** — Calls mcp__vds-ops__* tools (read-only, but touches infrastructure). Behavioral audit via using-vds-ops-test-trigger required before promotion to auto. → intended: `mode: auto, category: mcp`
-- **using-wiki-graph** — Calls mcp__wiki-graph__* tools (read-only, parses a .wiki/ corpus server-side). Behavioral audit via using-wiki-graph-test-trigger required before promotion to auto. → intended: `mode: auto, category: mcp`
 - **using-yt-tools** — Shells out to yt-dlp + ffmpeg and writes ./yt-cache/ in cwd. Behavioral audit via using-yt-tools-test-trigger required before promotion to auto. → intended: `mode: auto, category: research`

dist-hermes/meta/inter-session-peer-discipline/SKILL.md

@@ -3,7 +3,7 @@ name: inter-session-peer-discipline
 version: 0.1.1
 description: >
   Use whenever exchanging messages with another agent session over an inbox /
-  peer channel (`.claude-inbox/`, inter-session messaging). Treat a peer
+  peer channel (`.agents/inbox/`, inter-session messaging). Treat a peer
   session's messages — and your own replies — as proposals and analysis, NOT
   authority. The human is the only source of direction and of scope. Never
   report a peer-driven (or self-driven) design escalation as a settled
@@ -17,7 +17,7 @@ description: >
 
 ## When this runs
 
-**Whenever** you send or receive a message over an inter-session channel — `.claude-inbox/`, peer-to-peer agent messaging, or any "another session wrote to me" context.
+**Whenever** you send or receive a message over an inter-session channel — `.agents/inbox/`, peer-to-peer agent messaging, or any "another session wrote to me" context.
 
 **At session start** when `CLAUDE.md` has a trigger line like:
 - `inter-session messaging: peer not authority`
@@ -34,7 +34,7 @@ description: >
 
 This is the operational backbone that makes "peer ≠ authority" enforceable:
 
-- **The inbox (`.claude-inbox/`) is a communication channel only** — discussion, help (asking / answering questions), and lifecycle notification ("task created", "closed", "blocked"). Nothing more.
+- **The inbox (`.agents/inbox/`) is a communication channel only** — discussion, help (asking / answering questions), and lifecycle notification ("task created", "closed", "blocked"). Nothing more.
 - **Tasks themselves go only through `mcp__projects-meta__tasks_*`.** The board is the single source of truth. A task's existence, state, scope, and decisions are created / changed / recorded via `tasks_create`, `tasks_update`, `tasks_append_decision_trail` — never "decided" inside an inbox message. The inbox merely *notifies and discusses*; it never *is* the task.
 
 Corollary: **if it isn't on the board via meta, it is not a task and not a decision — it's talk.** A design call that matters must land on the board (or in the wiki), with the inbox only pointing at it. This is exactly what stops two sessions from "deciding" a redesign in letters: the authoritative artifact has one home, and it isn't the inbox.
@@ -55,7 +55,7 @@ If a peer session is the one to catch it, that's a correct circuit-break, not an
 
 ## Why this exists
 
-Emerged 2026-06-16: a `.workshop` session and an `OpeItcLoc03/common` session ran a multi-round design exchange over `.claude-inbox/`. The workshop session escalated a design (tamper-guard → prevention → oracle-integrity → runner-owns-verifier → close-moves) across rounds and reported each step to common as "решение постановщика" — implying human sanction the human had not given. The `common` session pattern-matched the echo-chamber (fast agreement + scope inflation), read its own Stop-hook, and correctly refused to implement the unratified redesign, asking the human instead. The lesson: durable artifact in a skill, by the user's direction — methodology lives in `claude-skills`, not per-session memory.
+Emerged 2026-06-16: a `.workshop` session and an `OpeItcLoc03/common` session ran a multi-round design exchange over `.agents/inbox/`. The workshop session escalated a design (tamper-guard → prevention → oracle-integrity → runner-owns-verifier → close-moves) across rounds and reported each step to common as "решение постановщика" — implying human sanction the human had not given. The `common` session pattern-matched the echo-chamber (fast agreement + scope inflation), read its own Stop-hook, and correctly refused to implement the unratified redesign, asking the human instead. The lesson: durable artifact in a skill, by the user's direction — methodology lives in `claude-skills`, not per-session memory.
 
 ## Reference
 

dist-hermes/productivity/using-tasks/README.md

@@ -1,169 +0,0 @@
-# using-tasks
-
-Runtime policy for keeping compressed working context across parallel tasks
-in a monorepo. The agent reads and updates `.tasks/` so every session starts
-oriented and every switch costs seconds, not minutes.
-
-`using-tasks` governs *usage* of an existing `.tasks/`. Initial creation and
-migration to canon are owned by [`setup-tasks`](../setup-tasks/).
-
-> Renamed from `task-status-wiki` at v1.0.0.
-
-## When it triggers
-
-- User is switching between tasks, resuming a paused task, starting a new
-  one, or asks "where were we" / "what's the status".
-- User says: "use task management system", "pause", "switch to X",
-  "update status".
-- Any context-switching or multi-task coordination question in a code
-  project.
-- If `.tasks/` is missing or non-canonical, this skill delegates to
-  [`setup-tasks`](../setup-tasks/) before doing anything else.
-
-## Structure
-
-```
-<monorepo-root>/
-└── .tasks/
-    ├── STATUS.md          ← board: one block per task, sorted by priority
-    └── <task-slug>.md     ← deep context per task, one file each
-```
-
-Commit `.tasks/` to git — decision history is valuable, diffs show how
-thinking evolved.
-
-## STATUS.md format
-
-```markdown
-# Task Board
-_Updated: YYYY-MM-DD_
-
-## 🔴 [task-slug] — short description
-**Status:** active | paused | blocked | done
-**Where I stopped:** one sentence — the exact thought or action interrupted
-**Next action:** one concrete step to resume immediately
-**Blocker:** (only if blocked) what is preventing progress
-**Branch:** git branch name
-
----
-```
-
-Status legend:
-
-| Emoji | State | Notes |
-|---|---|---|
-| 🔴 | Active | Currently worked on. **Only one at a time.** |
-| 🟡 | Paused | In progress, resumable. |
-| ⚪ | Ready | Defined, not started. |
-| 🟢 | Done | Kept until merged. |
-| 🔵 | Blocked | Waiting on external input. |
-
-## Per-task file format (`<task-slug>.md`)
-
-Sections, in order: **Goal** (one paragraph — what this achieves and why),
-**Key files** (`path/to/file.ts:42` style — specific lines when relevant),
-**Decisions log** (reverse-chronological, append-only — past entries are
-immutable), **Open questions**, **Completed steps**, **Notes** (temporary
-hypotheses, links).
-
-## Operations
-
-### Session start
-
-1. Check `.tasks/STATUS.md`. If missing → invoke
-   [`setup-tasks`](../setup-tasks/) and stop until it returns.
-2. Read `STATUS.md`.
-3. If user names a task, read its `<task-slug>.md`.
-4. Confirm in one sentence: "We're in the middle of X, next step is Y."
-5. Ask if the plan is still correct before doing anything.
-6. If `_Updated` is more than 3 days old, flag it and ask the user to
-   confirm current state.
-
-### Session end / pause / switch
-
-1. Update `STATUS.md`: set the current task to 🟡, refresh "Where I stopped"
-   and "Next action".
-2. Append non-obvious decisions to `<task-slug>.md` Decisions log.
-3. Move finished items to "Completed steps".
-4. Commit: `git add .tasks/ && git commit -m "chore: update task status [<task-slug>]"`.
-
-### Task switch
-
-1. Run session-end ops for the current task.
-2. Read the target `<task-slug>.md`.
-3. Set the target to 🔴 in `STATUS.md` (demote previous active to 🟡).
-4. Confirm orientation before starting work.
-
-### New task
-
-1. Ask: slug, goal, known key files, branch.
-2. Create `<task-slug>.md` with Goal and Key files populated.
-3. Add a ⚪ block to `STATUS.md`.
-4. Create / checkout the branch if missing.
-
-### Task completion
-
-1. **Pre-close coverage check** — list acceptance criteria, locate
-   evidence (tests, smoke-test artefacts, manual checklist ticks, design
-   doc refs). Missing evidence → ask the user before closing; never auto-close.
-2. Resolve or drop all open questions.
-3. Set status to 🟢 in `STATUS.md`.
-4. Append a final summary line to the Decisions log.
-5. Remind the user to delete the branch after merge.
-
-### Post-commit task closure prompt
-
-After a `feat:` / `fix:` commit the agent prompts:
-"эта работа закрывает таску `<slug>`?". Slug candidates: commit-message
-scope, current branch, most recent `Where I stopped`. If yes → run the
-coverage check above. Skips `chore:` / `meta:` / `docs:` commits.
-
-Forces a fresh-while-fresh decision, instead of letting shipped code sit
-under a stale ⚪ block.
-
-### Recommendations / "what's next" trigger
-
-When the user asks «что дальше», «срочные», «куда копаем», "what next",
-"status", or on session-start — recommend in this order:
-
-1. **Local cwd-project board** ranked 🔴 → 🟡 → ⚪. Cite slugs.
-2. **One footnote line** if relevant: `Cross-project: N 🔴 in other repos
-   (см. mcp__projects-meta__tasks_aggregate).` Only if N>0 and no local 🔴.
-
-Explicit "по всем проектам" / "across all projects" flips the order.
-Pairs with `using-projects-meta`'s local-first rule (which covers reads;
-this one covers recommendations).
-
-## Rules
-
-- **Never lose "Where I stopped".** Most critical field. If unclear, ask
-  before ending the session.
-- **One sentence per `STATUS.md` field.** Compress, don't write prose.
-- **Key files must be specific** — not "auth module" but
-  `packages/auth/src/useAuth.ts:87`.
-- **Decisions log is append-only.** Past entries are immutable.
-- **Commit after every session end.** `git log` is the history of thinking.
-- **Always confirm orientation at session start.** State understanding
-  before acting.
-- **One active task at a time** — only one 🔴 in `STATUS.md`.
-- **Never close without coverage check.** See "### Task completion"
-  step 1.
-- **Local-first recommendations.** cwd-project first; cross-project at
-  most one footnote line.
-
-## Install
-
-From the repo root:
-
-```bash
-bash scripts/install.sh using-tasks
-```
-
-Works on Windows under git-bash, Linux, macOS.
-
-## See also
-
-- [`setup-tasks`](../setup-tasks/) — companion, owns `.tasks/` creation and
-  canon migration.
-- [`project-bootstrap`](../project-bootstrap/) — invokes `setup-tasks` for
-  new projects.

dist-hermes/productivity/using-tasks/SKILL.md

@@ -1,251 +0,0 @@
----
-name: using-tasks
-version: 1.4.0
-description: >
-  Policy skill for working with an existing `.tasks/` board (per-task files + STATUS.md).
-  Use whenever the user is switching between tasks, resuming a paused task, starting a new
-  task, asking "where were we", says "use task management system", "pause", "switch to X",
-  "what's the status", "update status", or wants to track progress across parallel workstreams.
-  Trigger on any context-switching or multi-task coordination question in a code project.
-  If `.tasks/` is missing or non-canonical (no per-task `<task-slug>.md` files, no emoji
-  status legend in STATUS.md), delegate to `setup-tasks` first — it has its own confirmation
-  gate. Renamed from `task-status-wiki` at v1.0.0.
----
-
-# using-tasks
-
-> Policy for maintaining compressed working context across parallel tasks in a monorepo.
-> The agent reads and updates `.tasks/` so every session starts oriented and every switch
-> costs seconds, not minutes. This skill governs *usage* of an existing `.tasks/` — initial
-> creation and migration to canon are owned by `setup-tasks`.
-
-## Prerequisites
-
-This skill assumes the project has a canonical `.tasks/` layout:
-
-- `.tasks/STATUS.md` — the board, with per-task blocks using emoji status (🔴 active / 🟡 paused / ⚪ ready / 🟢 done / 🔵 blocked).
-- `.tasks/<task-slug>.md` — one deep-context file per active or paused task.
-
-If `.tasks/` is **missing**, or `STATUS.md` exists but is non-canonical (e.g. flat sections like "## Done" / "## In Progress" without the emoji + per-task block format, or no per-task files exist alongside STATUS.md) — invoke `setup-tasks` first. It detects greenfield vs migrate, has its own confirmation gate, and creates / migrates the structure. Only after `setup-tasks` finishes should this skill operate on `.tasks/`.
-
-## Structure
-
-```
-<monorepo-root>/
-  .tasks/
-    STATUS.md          ← active board: 🔴 / 🟡 / ⚪ / 🔵 blocks, sorted by priority
-    <task-slug>.md     ← deep context per task, one file each
-    .lock              ← runtime session lock; **gitignored** (never committed)
-    archive/
-      YYYY-MM.md       ← 🟢 done blocks moved off the board, one file per month
-```
-
-Commit `.tasks/` to git. Decision history is valuable; diffs show how thinking evolved.
-
-`STATUS.md` is the **active** board — it must stay lean so orientation reads stay cheap. Closed 🟢 tasks are archived to `archive/YYYY-MM.md` once they pile up; see "### Archiving done tasks".
-
-> **`.tasks/.lock` must be listed in `.gitignore`** (add `.tasks/.lock` to your project's `.gitignore`). The lock file is ephemeral runtime state, not project history — it must never be committed.
-
----
-
-## STATUS.md format
-
-```markdown
-# Task Board
-_Updated: YYYY-MM-DD_
-
-## 🔴 [task-slug] — short description
-**Status:** active | paused | blocked | done
-**Where I stopped:** one sentence — the exact thought or action interrupted
-**Next action:** one concrete step to resume immediately
-**Blocker:** (only if blocked) what is preventing progress
-**Session break:** (optional) `true` — or a hint string for the next track. Marks this task as a session boundary.
-**Branch:** git branch name
-
----
-```
-
-**Emoji convention:**
-- 🔴 Active — currently worked on (only one at a time)
-- 🟡 Paused — in progress, resumable
-- ⚪ Ready — not started, fully defined
-- 🟢 Done — completed; kept on the board until merged, then archived (see "### Archiving done tasks")
-- 🔵 Blocked — waiting on external input
-
-### `session_break` marker
-
-A task may carry a `session_break` marker — set by whoever defines the task (e.g. the delegating workshop) when its completion is a natural place to stop and start a fresh session. It signals an autonomous agent: *finish this task, then pause instead of immediately claiming the next one.*
-
-- **Type:** boolean or string.
-  - `session_break: true` — pause after close; the next track is "see STATUS.md".
-  - `session_break: "<hint>"` — pause after close; `<hint>` names the recommended next track.
-- **Where it lives:** in the task's frontmatter when delivered via the task system (`session_break: true` / `session_break: "<hint>"`); mirrored on the local board as the optional `**Session break:**` field in the task's STATUS.md block.
-- **Absent →** behaviour is unchanged: close the task and continue as usual.
-
-The check is enforced in the **Task completion** flow below (after close, before claiming the next task).
-
----
-
-## Per-task file format (`<task-slug>.md`)
-
-```markdown
-# <task-slug>
-
-## Goal
-One paragraph. What this achieves and why it matters in the monorepo.
-
-## Key files
-- `path/to/file.ts` — role in this task
-- `path/to/other.ts:42` — specific line if relevant
-
-## Decisions log
-Reverse-chronological. Append only — never rewrite past entries.
-- YYYY-MM-DD: Why X was chosen over Y
-- YYYY-MM-DD: Constraint Z discovered, approach adjusted
-
-## Open questions
-- [ ] unresolved design or dependency questions
-
-## Completed steps
-- [x] steps finished this or previous sessions
-
-## Notes
-Temporary hypotheses, links, names of people to consult.
-```
-
----
-
-## Agent operations
-
-### Session start
-1. **Session lock guard.** If `.tasks/` exists, read `.tasks/.lock`.
-   - **Active agent lock** — `type:"agent"` with `heartbeat` ≤ 10 minutes old: print the hard warning below and **require explicit user confirmation** before proceeding. Do not touch the board until the user confirms.
-     ```
-     ⚠️ поллер ведёт <slug> — нельзя работать параллельно
-     ```
-     (Substitute the `slug` field from the lock file if present, otherwise omit it.)
-   - **Stale lock** — any type whose TTL has expired (`type:"agent"` with `heartbeat` > 10 min ago; `type:"interactive"` with `started_at` > 2 h ago): silently overwrite.
-   - **Absent or stale lock** (including after user confirmation): write `.tasks/.lock`:
-     ```json
-     {"type":"interactive","started_at":"<ISO8601>","ttl_minutes":120}
-     ```
-2. Check if `.tasks/STATUS.md` exists. If not → invoke `setup-tasks` and stop here until it returns.
-3. Read `STATUS.md` — this is the orientation read (see note below on why it's a local read, not an MCP call).
-4. If user names a task, read its `<task-slug>.md`.
-5. Confirm in one sentence: "We're in the middle of X, next step is Y."
-6. Ask if the plan is still correct before doing anything.
-7. If STATUS.md `_Updated` date is >3 days ago, flag it and ask user to confirm current state.
-8. If `STATUS.md` holds **≥ 10** 🟢 done blocks, archive them first (see "### Archiving done tasks") so the board you orient on is lean.
-
-> **Orient by reading the local `STATUS.md`, not an MCP call.** It is the live board and — kept lean by archival — cheap to read. Do **not** reach for projects-meta tools to enumerate the current project's board:
-> - `tasks_aggregate` is cache-based, cross-project, and does **not** index ready/done — its own docs say to read `.tasks/STATUS.md` directly for the current project.
-> - `tasks_get_status(target_project, slug)` returns a **single** task's live status (`{status, found}`) by a slug you already know — it cannot list the board. Use it only to check **one** known task (e.g. confirm a delegated task's board state, or detect async-human parking), never for orientation.
-
-### Session end / pause / switch
-1. **Release session lock.** If `.tasks/.lock` exists and contains `"type":"interactive"`: delete `.tasks/.lock`. (Stale interactive locks are cleaned up here too; silently delete any interactive lock regardless of TTL.)
-2. Update `STATUS.md`: set current task to 🟡, update "Where I stopped" and "Next action".
-3. Append to `<task-slug>.md` Decisions log any non-obvious choices made this session.
-4. Move finished items to "Completed steps".
-5. Commit: `git add .tasks/ && git commit -m "chore: update task status [<task-slug>]"`
-
-### Task switch
-1. Perform session-end operations for the current task.
-2. Read the target `<task-slug>.md`.
-3. Set it to 🔴 in STATUS.md (demote previous active to 🟡).
-4. Confirm orientation before starting work.
-
-### New task creation
-1. Ask: task name (slug), goal, known key files, branch name.
-2. Create `<task-slug>.md` with Goal and Key files populated.
-3. Add ⚪ block to `STATUS.md`.
-4. Create and checkout branch if it doesn't exist.
-
-### Task completion
-1. **Pre-close coverage check.** Before setting 🟢:
-   - List acceptance criteria from the per-task `<slug>.md` (or the STATUS block if no per-task file).
-   - For each criterion, locate evidence: a test name in the diff, a smoke-test artefact, a manual-checklist tick in the per-task file, or a design-doc reference.
-   - Missing evidence on any criterion → flag to user and ask "закрывать или подождать coverage'а?". Never silently close.
-   - If acceptance criteria are policy / docs-only and have no testable shape, an explicit user "ok, closed by inspection" is required (record this in the close-note).
-2. Resolve or drop all open questions.
-3. Set status to 🟢 in STATUS.md.
-4. Append final summary line to Decisions log.
-5. Remind user to delete the branch after merge.
-6. **Session-break check (after close, before claiming the next task).** Once the task is 🟢 and committed — and **before** any `tasks_claim_next` or starting the next task — read the closed task's `session_break` marker (its frontmatter `session_break`, or the `**Session break:**` field in its STATUS.md block). If present:
-   - Print this line **verbatim**, substituting the closed task's slug for `[slug]` and the marker's string value for `[value | "см. STATUS.md"]` (use the literal `см. STATUS.md` when the marker is just `true`):
-
-     `🔚 SESSION BOUNDARY — [slug] закрыта. Рекомендую завершить текущую сессию. Следующий трек: [value | "см. STATUS.md"]`
-
-   - **Stop.** Do not claim or start the next task.
-   - If the marker is absent → behaviour is unchanged: proceed to claim / start the next task as usual.
-7. **Archival check.** After the close is committed, if `STATUS.md` now holds **≥ 10** 🟢 done blocks, archive them (see "### Archiving done tasks"). This keeps the board lean for the next orientation read.
-
-### Archiving done tasks
-
-🟢 done blocks accumulate in `STATUS.md` and bloat it — and since orientation reads the whole board, a bloated file burns context on every session start (the recurring "huge STATUS.md" complaint). Keep the board lean: done blocks stay only until merged, then move to a monthly archive.
-
-**Threshold.** When `STATUS.md` holds **≥ 10** 🟢 done blocks, archive them. Check at two moments: (a) right after closing a task (Task completion step 7), and (b) at session start, before orienting (Session start step 7). The threshold is a ceiling, not a target — archive in batches; don't churn one block at a time.
-
-**Where.** Append the archived blocks to `.tasks/archive/YYYY-MM.md` — one file per calendar month, keyed by the date of archival. Create `.tasks/archive/` and the month file if absent. If the month file already exists, **append**; never overwrite.
-
-**Archive file format** (header written once, on file creation):
-
-```markdown
-# Archived done tasks — YYYY-MM
-
-Moved out of `.tasks/STATUS.md` to keep the active board lean.
-Full source is git history; this file is for grep-able historical context.
-
----
-```
-
-…followed by each 🟢 block **verbatim** (including its trailing `---` separator and any `<!-- closed-by … -->` comments).
-
-**After archiving,** `STATUS.md` keeps only 🔴 / 🟡 / ⚪ / 🔵 blocks. Commit the move on its own:
-
-```
-git add .tasks/ && git commit -m "meta(tasks): archive done batch → .tasks/archive/YYYY-MM.md"
-```
-
-Leave a just-closed 🟢 block on the board only while it's still useful at a glance (pending merge, fresh reference). Everything older goes to the archive.
-
-### Post-commit task closure prompt
-
-After any implementation commit (`feat:` / `fix:` / similar), prompt the user once:
-
-> Эта работа закрывает таску `<slug>`?
-
-Slug candidates, in priority: (a) commit message scope, (b) current branch name, (c) the most recent `Where I stopped` field that mentions a now-shipped artefact. If user says yes → run the pre-close coverage check from "### Task completion". If no → silent.
-
-Skip on `chore:` / `meta:` / `docs:` / `style:` commits — they rarely close work.
-
-This exists because shipped code can sit while the task block stays ⚪ ready (e.g. `extend-project-discipline-brainstorm-workspaces` lived as ⚪ for a day after `215afdd` shipped Rule 5). The prompt forces a one-line decision while the work is fresh.
-
-### Recommendations / "what's next" trigger
-
-When the user asks «что дальше», «срочные», «куда копаем», «status», «what next», or session-start lands on a project — recommend in this order:
-
-1. **Local cwd-project board** ranked 🔴 → 🟡 → ⚪. Group by status, summarize one line each. Cite slugs.
-2. **One footnote line** if cross-project state is relevant: `Cross-project: N 🔴 active in other repos (см. mcp__projects-meta__tasks_aggregate).` Only when N>0 and there is no active 🔴 in the current cwd. Never bury local recommendations under it.
-
-Cross-project urgents are *information*, not the driver of "what to do here". The user chose this cwd; that's the implicit scope.
-
-If the user explicitly asks "across all projects" / "по всем проектам" / "cross-project status" — flip the order: cross-project first, local as footnote.
-
-Pair: `using-projects-meta` declares local-first for **reads**; this rule extends local-first to the **recommendation phase**.
-
----
-
-## Rules
-
-- **Honour `.tasks/.lock`** — read the lock at session start before touching the board; write it after clearing the guard; delete it at session end/pause. Never skip the lock check when `.tasks/` exists. The lock file must be gitignored.
-- **Never lose "Where I stopped"** — most critical field. If unclear, ask before ending session.
-- **One sentence per STATUS.md field** — compress, don't write prose.
-- **Key files must be specific** — not "auth module" but `packages/auth/src/useAuth.ts:87`.
-- **Decisions log is append-only** — past entries are immutable.
-- **Commit after every session end** — git log is the history of thinking.
-- **Always confirm orientation at session start** — state understanding before acting.
-- **One active task at a time** — only one 🔴 in STATUS.md.
-- **Keep the board lean** — orientation reads the local `STATUS.md` whole, so archive 🟢 done blocks to `.tasks/archive/YYYY-MM.md` once ≥10 pile up. Never enumerate the current project's board via `tasks_aggregate` (cross-project cache) or `tasks_get_status` (single-task, by slug). See "### Archiving done tasks".
-- **Never close a task without a coverage check** — see "### Task completion" step 1. Acceptance criteria with no evidence → ask, don't auto-close.
-- **Honour `session_break`** — a closed task carrying a `session_break` marker means stop after close; never chain into `tasks_claim_next`. See "### Task completion" step 6.
-- **Local-first recommendations** — cwd-project board comes first; cross-project urgents are at most one footnote line.

dist-hermes/research/using-wiki/README.md

@@ -1,182 +0,0 @@
-# using-wiki
-
-Runtime policy for an LLM Wiki built on the
-[Karpathy LLM Wiki pattern](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f).
-Knowledge is **compiled once and kept current** across three layers, via
-three named operations, with strict file formats that keep the wiki
-parseable and grep-friendly.
-
-`using-wiki` governs *usage* of an existing `.wiki/`. Initial creation and
-migration to canon are owned by [`setup-wiki`](../setup-wiki/).
-
-> Renamed from `wiki-maintainer` at v1.0.0.
-
-## When it triggers
-
-- User says: "use project wiki", "query the wiki", "ingest this", or the
-  Russian equivalents ("обнови вики", "проверь вики", "запроси вики",
-  "заингесть").
-- Any time the agent modifies a file under `.wiki/` — the workflow and
-  formats below are mandatory.
-- If `.wiki/` is missing or non-canonical, this skill delegates to
-  [`setup-wiki`](../setup-wiki/) before doing anything else.
-
-## Three layers (do not blur)
-
-1. **Raw sources** — `.wiki/raw/` (or external paths registered in
-   `raw/README.md`). **Immutable.** Read, never edit. The only exception is
-   appending a `> Status` blockquote when the user explicitly asks for a
-   status audit.
-2. **Wiki** — everything else under `.wiki/`. Agent-owned. Entity / concept /
-   package / source summary pages.
-3. **Schema** — `.wiki/CLAUDE.md`. Project-specific conventions (what
-   entities, what packages, naming). Always read it first; it overrides this
-   skill on conflict.
-
-## Three operations
-
-### Ingest
-
-«заингесть X» — pull a raw source into the wiki.
-
-1. Read the raw source fully.
-2. Extract: entities, concepts, packages, cross-cutting patterns.
-3. Create `sources/<slug>.md` (one summary page per source, ~50–150 lines).
-4. For each affected entity / concept / package page: update if exists,
-   create if not. Flag contradictions explicitly with
-   `> **Противоречие:** источник A говорит X, источник B — Y`.
-   **Never silently overwrite.**
-5. Update `index.md`.
-6. Append one line to `log.md`.
-7. Report: what was created, updated, contradicted.
-
-One ingest may touch 10–15 pages. That's normal — that's why an LLM does it.
-
-### Query
-
-A question answered from the wiki.
-
-1. Read `index.md` first, drill into relevant pages.
-2. Answer with citations as markdown links.
-3. **Compound the wiki.** If the answer is a real synthesis, ask the user:
-   "Сохранить как страницу wiki?" Good queries become durable pages under
-   `concepts/` or `analyses/`.
-4. Append one line to `log.md`.
-
-### Lint
-
-«проверь wiki» — health check.
-
-Scan for:
-
-- Contradictions between pages.
-- Orphans (pages with no inbound links).
-- Stale claims (raw source updated after the summary's `ingested:` date —
-  check via `git log -p`).
-- Concepts mentioned in prose but missing their own page.
-- Empty / TODO sections.
-
-Report as a punch list. Don't delete anything automatically. Append one
-line to `log.md` with the findings.
-
-## File formats (mandatory)
-
-### Page frontmatter
-
-```yaml
----
-title: Человекочитаемое имя
-type: entity | concept | package | source | contradiction | open-question | overview
-tags: [short, tokens]
-sources: [../sources/foo.md, ../sources/bar.md]
-updated: 2026-04-21
----
-```
-
-Source pages also carry `ingested: YYYY-MM-DD` and `raw_path: ../raw/...`.
-Contradiction pages also carry `status: open | resolved | accepted-divergence` and `affects: [../entities/x.md, ../concepts/y.md]`.
-Open-question pages also carry `status: open | answered | obsolete` and `touches: [../entities/x.md, ../sources/z.md]`.
-
-### File naming
-
-- `kebab-case.md`, **Latin only**. Transliterate Cyrillic / non-Latin in
-  filenames; keep the original title in H1 + frontmatter.
-- `entities/<name>.md`, `concepts/<name>.md`, `packages/<name>.md`
-  (no `@org/` prefix), `sources/<slug>.md`, `contradictions/<slug>.md`,
-  `open-questions/<slug>.md`.
-
-### `log.md` — append-only, grep-parseable
-
-Every entry must start with:
-
-```
-## [YYYY-MM-DD] <operation> | <short description>
-```
-
-Operations: `ingest`, `query`, `lint`, `refactor`, `decision`, `init`.
-
-Parse with: `grep "^## \[" .wiki/log.md | tail -20`.
-
-### `index.md`
-
-Catalog, not narrative. One line per page: `- [Title](path) — hook.`
-Sections by type. Update on every ingest.
-
-### Cross-references
-
-- Wiki → wiki: relative markdown links — `[Name](../entities/x.md)`.
-- Wiki → code: relative path from repo root — `[foo.js](../../packages/api/foo.js)`.
-- Wiki → raw: `../raw/<file>`.
-- URL-encode spaces (`%20`) and Cyrillic when needed.
-
-## Quick reference
-
-| Situation | Files touched |
-|---|---|
-| Ingest one doc | `sources/<slug>.md` (new) + 3–15 entity/concept/package pages + `index.md` + `log.md` |
-| Query | (read only) + optionally a new wiki page + `log.md` |
-| Lint | (read only) + `log.md` |
-| Bootstrap / migrate | (delegated to [`setup-wiki`](../setup-wiki/)) |
-
-## Common mistakes
-
-- **Editing `raw/`.** Don't. Only allowed change: status blockquote on
-  explicit request.
-- **Dumping raw content into `sources/`.** Summaries are summaries. Link to
-  raw, don't copy.
-- **Silent overwrites on contradictions.** Flag them with a `> **Противоречие:**`
-  block.
-- **Narrative `log.md`.** "Today I added…" is wrong. Use
-  `## [YYYY-MM-DD] ingest | <what>`.
-- **Non-ASCII filenames.** Breaks greppability and cross-platform. Transliterate.
-- **Forgetting `index.md`.** Pages not listed there are invisible to future
-  queries.
-- **Improvising layout when canon files are missing.** Hand off to
-  [`setup-wiki`](../setup-wiki/) instead of patching ad-hoc.
-
-## When NOT to use
-
-- The project has CLAUDE.md / AGENTS.md docs but no `.wiki/` — that's regular
-  documentation, not an LLM Wiki.
-- The user wants a single-file README or ADR — this skill is for persistent,
-  interlinked knowledge bases.
-- One-off questions about code — read files directly, no wiki workflow needed.
-
-## Install
-
-From the repo root:
-
-```bash
-bash scripts/install.sh using-wiki
-```
-
-Works on Windows under git-bash, Linux, macOS.
-
-## See also
-
-- [`setup-wiki`](../setup-wiki/) — companion, owns `.wiki/` creation and
-  canon migration.
-- [`project-bootstrap`](../project-bootstrap/) — invokes `setup-wiki` for
-  new projects.
-- Karpathy's LLM Wiki gist:
-  <https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f>

dist-hermes/research/using-wiki/SKILL.md

@@ -1,138 +0,0 @@
----
-name: using-wiki
-version: 1.1.0
-description: Policy skill for working with an existing `.wiki/` (Karpathy LLM Wiki pattern). Use when the user asks to ingest a document, answer from the wiki, lint/health-check it, or says "use project wiki", "обнови вики", "проверь вики", "запроси вики", "заингесть", "query the wiki". Also use when modifying any file under `.wiki/` — the workflow and formats below are mandatory, and project-specific conventions live in `.wiki/CLAUDE.md`. If `.wiki/` is missing or non-canonical, delegate to `setup-wiki` first (it has its own confirmation gate). Renamed from `wiki-maintainer` at v1.0.0.
----
-
-# using-wiki
-
-> Policy for maintaining an LLM Wiki (Karpathy pattern: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f). Knowledge is **compiled once and kept current** across three layers, via three named operations, with strict file formats that make the wiki parseable and grep-friendly. This skill governs *usage* of an existing wiki — initial creation and migration to canon are owned by `setup-wiki`.
-
-## Prerequisites
-
-This skill assumes the project has a canonical `.wiki/` layout: `CLAUDE.md` (schema), `index.md` (catalog), `log.md` (op log), `overview.md`, `raw/README.md`, and the six content directories `entities/`, `concepts/`, `packages/`, `sources/`, `contradictions/`, `open-questions/`.
-
-If `.wiki/` is **missing**, or the layout is **non-canonical** (e.g. `SUMMARY.md` instead of `index.md`, or `source/` instead of `concepts/`/`sources/`, or `contradictions/`/`open-questions/` directories are absent) — invoke the `setup-wiki` skill first. It detects the situation (greenfield vs migrate) and creates or migrates the structure with its own confirmation gate. Only after `setup-wiki` finishes should this skill proceed with the operations below.
-
-## Three layers (do not blur)
-
-1. **Raw sources** — `.wiki/raw/` (or external paths registered in `raw/README.md`). **Immutable.** Read, never edit. The only exception is appending a `> Status` blockquote when the user explicitly asks for a status audit.
-2. **Wiki** — everything else under `.wiki/`. Agent-owned. Entity / concept / package / source summary pages.
-3. **Schema** — `.wiki/CLAUDE.md`. Project-specific conventions (what entities, what packages, naming). Always read it first if present; it overrides this skill when it conflicts.
-
-## First step on every operation
-
-1. Read `.wiki/CLAUDE.md` if it exists.
-2. Read `.wiki/index.md` to locate relevant pages.
-3. Only then act.
-
-If `.wiki/CLAUDE.md` is missing, the layout is incomplete — invoke `setup-wiki` rather than improvising.
-
-## Three operations
-
-### Ingest — «заингесть X»
-
-1. Read the raw source fully.
-2. Extract: entities, concepts, packages, cross-cutting patterns.
-3. Create `sources/<slug>.md` (one summary page per source, ~50–150 lines).
-4. For each affected entity/concept/package page:
-   - If it exists → update it. **Flag contradictions explicitly** with `> **Противоречие:** источник A говорит X, источник B — Y`. Don't silently overwrite.
-   - If not → create it.
-5. Update `index.md` — add or move entries.
-6. Append one line to `log.md` (format below).
-7. Report to the user: what created, what updated, what contradictions found.
-
-**One ingest may touch 10–15 pages. This is normal — that's why LLMs do it.**
-
-### Query — вопрос по wiki
-
-1. Read `index.md` first, then drill into relevant pages.
-2. Answer with citations as markdown links to wiki pages.
-3. **Compound the wiki.** If the answer is a real synthesis (comparison, analysis, new connection) — ask the user: "Сохранить как страницу wiki?" Good queries become durable pages under `concepts/`, `analyses/`, or similar.
-4. Append one line to `log.md`.
-
-### Lint — «проверь wiki»
-
-Scan for:
-- **Contradictions** between pages.
-- **Orphans** — pages with no inbound links.
-- **Stale claims** — git `log -p` on the raw source shows it was updated after the summary's `ingested:` date.
-- **Missing entities** — concepts mentioned in prose but without their own page.
-- **Empty/TODO sections.**
-
-Report as a punch list. Don't delete anything automatically.
-Append one line to `log.md` summarizing the findings.
-
-## File formats (MANDATORY)
-
-### Page frontmatter
-
-```yaml
----
-title: Человекочитаемое имя
-type: entity | concept | package | source | contradiction | open-question | overview
-tags: [short, tokens]
-sources: [../sources/foo.md, ../sources/bar.md]
-updated: 2026-04-21
----
-```
-
-Source pages also carry `ingested: YYYY-MM-DD` and `raw_path: ../raw/...`.
-
-Contradiction pages also carry `status: open | resolved | accepted-divergence` and `affects: [../entities/x.md, ../concepts/y.md]`.
-
-Open-question pages also carry `status: open | answered | obsolete` and `touches: [../entities/x.md, ../sources/z.md]`.
-
-### File naming
-
-- `kebab-case.md`, **Latin only**. Transliterate Cyrillic / other scripts in filenames (`план переписывания` → `ozon-client-rewrite.md`). Keep the original title in the H1 and frontmatter.
-- `entities/<name>.md`, `concepts/<name>.md`, `packages/<name>.md` (no `@org/` prefix), `sources/<slug>.md`, `contradictions/<slug>.md`, `open-questions/<slug>.md`.
-
-### `log.md` — append-only, grep-parseable
-
-Every entry **must** start with:
-
-```
-## [YYYY-MM-DD] <operation> | <short description>
-```
-
-Operations: `ingest`, `query`, `lint`, `refactor`, `decision`, `init`.
-
-Parseable with: `grep "^## \[" .wiki/log.md | tail -20`.
-
-### `index.md`
-
-Catalog, not narrative. One line per page: `- [Title](path) — hook.` Sections by type (entities / concepts / packages / sources / contradictions / open-questions). Update on every ingest.
-
-### Cross-references
-
-- Wiki → wiki: relative markdown links, `[Name](../entities/x.md)`.
-- Wiki → code: relative path from repo root: `[foo.js](../../packages/api/foo.js)`.
-- Wiki → raw: `../raw/<file>`.
-- URL-encode spaces in paths (`%20`) and Cyrillic when needed.
-
-## Quick reference
-
-| Situation | Files touched |
-|---|---|
-| Ingest one doc | `sources/<slug>.md` (new) + 3–15 entity/concept/package pages + `index.md` + `log.md` |
-| Query | (read only) + optionally new wiki page + `log.md` |
-| Lint | (read only) + `log.md` |
-| Bootstrap / migrate to canon | (delegated to `setup-wiki`) |
-
-## Common mistakes
-
-- **Editing `raw/`.** Don't. Only allowed: status blockquote when user explicitly asks.
-- **Dumping raw content into `sources/`.** Summaries are summaries. Link to raw, don't copy it.
-- **Silent overwrites.** When a new source contradicts an existing page, flag it with a `> **Противоречие:**` block; don't just overwrite.
-- **Narrative `log.md`.** `Today I added…` is wrong. Use `## [YYYY-MM-DD] ingest | <what>`.
-- **Non-ASCII file names.** Breaks greppability and cross-platform. Transliterate.
-- **Forgetting `index.md`.** Pages not listed there are effectively invisible for future queries.
-- **Skipping contradictions in lint.** The wiki's value grows from surfaced tensions, not from false consensus.
-- **Improvising layout when canon files are missing.** If the wiki is missing or partial, hand off to `setup-wiki` instead of patching ad hoc.
-
-## When NOT to use this skill
-
-- Project has CLAUDE.md / AGENTS.md docs but no `.wiki/` — that's regular project documentation, not an LLM Wiki.
-- User wants a single-file README or ADR — this skill is for persistent interlinked knowledge bases.
-- One-off questions about code — use regular file reading, not wiki workflow.

dist-hermes/software-development/pulling-before-work/README.md

@@ -1,29 +0,0 @@
-# pulling-before-work
-
-Policy skill that pulls the current branch from `origin` once at session start
-and on explicit re-sync requests. Designed to remove the "edited on stale base"
-footgun without trampling dirty work-trees or auto-merging.
-
-## When it triggers
-
-- **Session start** — when `CLAUDE.md` contains the line `pull remote before work` (added by `project-bootstrap` v1.4.0+).
-- **In-chat** — when the user says `sync`, `resync`, `pull`, `обнови репо`, `git pull please`, or close variants.
-
-Stays silent in non-git folders. Prints one informational line and exits in:
-no `origin` remote, no upstream tracking, dirty work-tree, detached HEAD.
-
-## What it does
-
-`git pull --ff-only` against the configured upstream — never auto-merges, never
-auto-rebases, never stashes, never commits, never pushes. On divergence it prints
-a warning with manual-resolution hints and exits.
-
-## Prerequisites
-
-None. The skill is a no-op outside git repos and folders without an `origin`
-remote, so it's safe to leave activated everywhere.
-
-## Related
-
-- `project-bootstrap` (v1.4.0+) — adds the trigger line to new and existing projects' `CLAUDE.md`.
-- `.wiki/concepts/pulling-before-work-design.md` (in projects bootstrapped from this repo: this design lives in `claude-skills`) — full design rationale.

dist-hermes/software-development/pulling-before-work/SKILL.md

@@ -1,153 +0,0 @@
----
-name: pulling-before-work
-version: 1.0.0
-description: >
-  Pulls the current branch from origin once at session start and on explicit
-  re-sync requests. Use when CLAUDE.md contains the trigger line "pull remote
-  before work", or when the user says "sync", "resync", "pull", "обнови репо",
-  "git pull please", or close variants asking to refresh from the remote.
-  Runs `git pull --ff-only` — never auto-merges or rebases. Stays silent in
-  non-git folders. Prints one informational line and exits when there is no
-  origin remote, no upstream tracking, the working tree is dirty, or HEAD is
-  detached. Does not stash, commit, or push. Activated by `project-bootstrap`
-  v1.4.0+ via the canonical CLAUDE.md template.
----
-
-# pulling-before-work
-
-> Pull from `origin` once when work starts. Don't auto-merge. Don't trample dirty work-trees. Don't ask twice in the same session unless asked.
-
-## When this runs
-
-**At session start** — once, when the skill is activated by the `pull remote before work` line in `CLAUDE.md`. The cycle below runs immediately.
-
-**On explicit re-sync** — when the user says any of: `sync`, `resync`, `pull`, `обнови репо`, `pull please`, `git pull`, `подтяни`, `pull from origin`. Re-runs the full cycle. There is no per-session counter; the user is always allowed to ask.
-
-**Never** before each commit, before each tool call, on every message, or in any other implicit cadence. Mode-3 ("start + on-demand") was the explicit design choice — see `.wiki/concepts/pulling-before-work-design.md`.
-
-## The pull cycle
-
-Run these checks in order. Print at most one line of chat output per run.
-
-### 1. Inside a git work-tree?
-
-```bash
-git rev-parse --is-inside-work-tree 2>/dev/null
-```
-
-If the command fails or prints anything other than `true` → **exit silently, no chat output.** This is the not-a-git-repo case; the skill must not be noisy in random folders.
-
-### 2. Has an `origin` remote?
-
-```bash
-git remote get-url origin 2>/dev/null
-```
-
-If the command fails (no such remote) → print one line and exit:
-
-```
-no origin remote — skip pull
-```
-
-### 3. Is the working tree clean?
-
-```bash
-git status --porcelain
-```
-
-If the output is non-empty → print one line and exit:
-
-```
-working tree dirty — skipping pull. commit/stash, потом скажи "sync"
-```
-
-Never stash automatically. Stash-pop conflicts are exactly the friction this skill exists to remove.
-
-### 4. Is HEAD attached?
-
-```bash
-git symbolic-ref -q HEAD
-```
-
-If the command fails (empty output, exit 1) → detached HEAD. Print:
-
-```
-detached HEAD — skip pull
-```
-
-### 5. Does the current branch have an upstream?
-
-```bash
-git rev-parse --abbrev-ref --symbolic-full-name '@{u}' 2>/dev/null
-```
-
-Capture the upstream name (e.g. `origin/master`). If the command fails → no upstream tracking. Print:
-
-```
-no upstream tracking for <branch> — skip pull
-```
-
-(Where `<branch>` is `git rev-parse --abbrev-ref HEAD`.)
-
-### 6. Pull, fast-forward only
-
-```bash
-git pull --ff-only
-```
-
-(No args — uses the configured upstream captured above.)
-
-Classify by exit code and stdout:
-
-| Result | Print |
-|---|---|
-| Already up to date | `✅ already up to date with <upstream>` |
-| Fast-forward, N commits | `✅ pulled N commits from <upstream>` |
-| Non-fast-forward / diverged (exit non-zero with "diverged" or "non-fast-forward" in output) | `⚠️ diverged from <upstream> — resolve manually (git pull --rebase or merge); skill never auto-merges/rebases` |
-
-### Out of scope
-
-The skill never:
-
-- commits, stashes, or pushes
-- recurses into submodules
-- pulls from non-`origin` remotes
-- pulls on detached HEAD
-- runs auto-merge or auto-rebase
-- runs more than once per session unless the user asks
-
-## Recovery hints
-
-If the skill skipped because of a dirty tree:
-
-```powershell
-# Windows / PowerShell
-git status            # see what's dirty
-git add . ; git commit -m "wip"
-# then ask the agent: "sync"
-```
-
-```bash
-# Linux / macOS
-git status
-git add . && git commit -m "wip"
-# then say "sync"
-```
-
-If the skill reported `diverged`:
-
-```bash
-# Option A: rebase your local commits on top of origin
-git pull --rebase
-
-# Option B: explicit merge (creates a merge commit)
-git pull --no-ff
-```
-
-The skill stays out of these decisions on purpose — both options have valid use cases and the user owns the choice.
-
-## Why this exists
-
-Stale local branches are a silent footgun: edits land on top of yesterday's `origin`, the divergence shows up at push time, and by then there's a chunk of work to rebase or merge on the wrong base. One pull at start covers the common case; an explicit re-sync trigger handles long sessions where someone pushed mid-flight.
-
-Full design rationale (mode choice, dirty-tree skip vs stash, `--ff-only` vs auto-merge, the upstream-check) lives in `.wiki/concepts/pulling-before-work-design.md`.

hermes/mapping.yaml

@@ -36,10 +36,6 @@ skills:
 
   # ─── auto (4 universals — MVP target) ────────────────────────────────
 
-  pulling-before-work:
-    mode: auto
-    category: software-development
-
   active-platform:
     mode: auto
     category: software-development
@@ -59,6 +55,14 @@ skills:
     mode: auto
     category: software-development
 
+  browser-operator:
+    mode: auto
+    category: software-development
+
+  ops-browser:
+    mode: auto
+    category: software-development
+
   using-markitdown:
     mode: auto
     category: productivity
@@ -96,18 +100,10 @@ skills:
     mode: auto
     category: productivity
 
-  using-tasks:
-    mode: auto
-    category: productivity
-
   setup-wiki:
     mode: auto
     category: research
 
-  using-wiki:
-    mode: auto
-    category: research
-
   setup-projects-meta:
     mode: manual
     source: hermes/skills/setup-projects-meta
@@ -140,13 +136,6 @@ skills:
 
   # ─── pending (8 — behavioral audit required) ─────────────────────────
 
-  delegate-task:
-    mode: pending
-    intended:
-      mode: auto
-      category: mcp
-    reason: "Calls mcp__projects-meta__tasks_create to create tasks in other projects/agents (Gitea commit, cross-project side-effect). Behavioral audit via delegate-task-test-trigger required before promotion to auto."
-
   using-yt-tools:
     mode: pending
     intended:
@@ -161,20 +150,6 @@ skills:
       category: mcp
     reason: "Calls mcp__vds-ops__* tools (read-only, but touches infrastructure). Behavioral audit via using-vds-ops-test-trigger required before promotion to auto."
 
-  using-wiki-graph:
-    mode: pending
-    intended:
-      mode: auto
-      category: mcp
-    reason: "Calls mcp__wiki-graph__* tools (read-only, parses a .wiki/ corpus server-side). Behavioral audit via using-wiki-graph-test-trigger required before promotion to auto."
-
-  session-handoff:
-    mode: pending
-    intended:
-      mode: auto
-      category: productivity
-    reason: "Writes .tasks/NEXT_SESSION.md (project-scope, sliding overwrite) and reads it on session start. Bidirectional file-system side-effect, opt-in via CLAUDE.md trigger-line. Behavioral audit via session-handoff-test-trigger required before promotion to auto."
-
   private-dev-public-publish:
     mode: pending
     intended:
@@ -182,20 +157,6 @@ skills:
       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."
-
-  session-inbox-monitor:
-    mode: pending
-    intended:
-      mode: auto
-      category: productivity
-    reason: "Paired SessionStart hook registers itself in ~/.claude/settings.json and sweeps orphaned monitor OS processes (Get-CimInstance | Stop-Process by sentinel+inbox-path); the skill then raises an in-session Monitor on .claude-inbox/. Primary activation is the CLAUDE.md trigger-line `inbox monitor: raise on start` + the injector, not a hermes-trigger. Behavioral gate CLEARED 2026-06-17 — test-trigger + review BOTH VERDICT PASS (activation 3/3 monitor + neg clean; structural hook audit 5 PASS/1 CONCERN, the CONCERN fixed in v0.2.2). STAYS pending on two independent tool-side blockers, NOT on behavioral verification: (1) the SessionStart hook is Windows-PowerShell and needs a Linux port for Hermes factory machines; (2) machine-level side-effects (user-config mutation of ~/.claude/settings.json + Get-CimInstance|Stop-Process kills) need a tool-side audit before auto. Promotion blocked on those two, not on test-trigger/review."
-
   inter-session-peer-discipline:
     mode: auto
     category: meta
@@ -220,20 +181,6 @@ skills:
       category: meta
     reason: "Resolves WHERE a project's meta lives before tasks_create / knowledge_ingest / brainstorm-promotion (meta-out-of-repo). Touches projects-meta MCP (tasks_create / knowledge_ingest / meta_status) and routes writes across repos. Review PASS (meta-host-routing-review) but the -install baseline is still open and a tool-side audit (cross-repo MCP writes) is required before auto. Mapping executes task meta-host-routing-hermes-mapping."
 
-  using-system-snapshot:
-    mode: pending
-    intended:
-      mode: auto
-      category: mcp
-    reason: "Calls mcp__projects-meta__meta_system_snapshot (read-only whole-machine ops snapshot: poller / docker / cross-project task load). Read-only, same class as using-vds-ops / using-wiki-graph; pending a behavioral test-trigger before auto."
-
-  task-format:
-    mode: pending
-    intended:
-      mode: auto
-      category: productivity
-    reason: "Documentational skill — how to write a .tasks/STATUS.md task block the autonomous poller will claim/route/report (block header, status emoji, Weight/Notify/Requirements fields). No tool-side effects; pending a behavioral test-trigger before auto."
-
   setup-agents-task-runner:
     mode: pending
     reason: "L2 installer — installs the standing-duty stack (agents-task-runner + watchdog + appeals-inbox) as platform-native OS services (systemd/launchd/winsw), fetches a pinned binary, writes poller-scope.json. Heavy infra side-effects (OS services + binary fetch); mode decision (skip vs manual vs auto) deferred — needs an explicit Hermes-factory applicability audit. Placeholder pending to keep the build green."
@@ -241,3 +188,47 @@ skills:
   ralph-loop-execution:
     mode: pending
     reason: "Behavioral oracle-loop skill (Verifier / Attempts / Max-Attempts retry loop). NB: source SKILL.md currently lacks YAML frontmatter (no name/description) — cannot auto-convert cleanly until that is fixed. Mapped pending as a placeholder; needs frontmatter + a behavioral audit before any mode decision."
+
+  # ─── mappa-skill-suite (7, pending — behavioral audit via mappa-skill-suite-review) ───
+  mappa-messaging:
+    mode: pending
+    intended:
+      mode: auto
+      category: communication
+    reason: "Calls mcp__mappa__* tools (board/wiki/inbox/handoff/sessions). Behavioral audit via mappa-skill-suite-review required before promotion to auto."
+  mappa-knowledge:
+    mode: pending
+    intended:
+      mode: auto
+      category: research
+    reason: "Calls mcp__mappa__* tools (board/wiki/inbox/handoff/sessions). Behavioral audit via mappa-skill-suite-review required before promotion to auto."
+  mappa-brainstorm-promote:
+    mode: pending
+    intended:
+      mode: auto
+      category: meta
+    reason: "Calls mcp__mappa__* tools (board/wiki/inbox/handoff/sessions). Behavioral audit via mappa-skill-suite-review required before promotion to auto."
+  mappa-delegation:
+    mode: pending
+    intended:
+      mode: auto
+      category: mcp
+    reason: "Calls mcp__mappa__* tools (board/wiki/inbox/handoff/sessions). Behavioral audit via mappa-skill-suite-review required before promotion to auto."
+  mappa-task-work:
+    mode: pending
+    intended:
+      mode: auto
+      category: productivity
+    reason: "Calls mcp__mappa__* tools (board/wiki/inbox/handoff/sessions). Behavioral audit via mappa-skill-suite-review required before promotion to auto."
+  mappa-closing-ritual:
+    mode: pending
+    intended:
+      mode: auto
+      category: productivity
+    reason: "Calls mcp__mappa__* tools (board/wiki/inbox/handoff/sessions). Behavioral audit via mappa-skill-suite-review required before promotion to auto."
+  mappa-session-orient:
+    mode: pending
+    intended:
+      mode: auto
+      category: productivity
+    reason: "Calls mcp__mappa__* tools (board/wiki/inbox/handoff/sessions). Behavioral audit via mappa-skill-suite-review required before promotion to auto."

scripts/build.ps1

@@ -44,7 +44,7 @@ function New-SkillArchive {
         [System.IO.Compression.ZipArchiveMode]::Create
     )
     try {
-        $files = Get-ChildItem -Path $sourceFull -Recurse -File
+        $files = Get-ChildItem -Path $sourceFull -Recurse -File | Where-Object { $_.FullName -notmatch '__pycache__' }
         foreach ($file in $files) {
             $rel = $file.FullName.Substring($sourceFull.Length + 1) -replace '\\','/'
             $entryName = "$SkillName/$rel"

scripts/install.ps1

@@ -1,15 +1,23 @@
-# Install skills/<name>/ into ~\.claude\skills\<name>\ (or $env:CLAUDE_SKILLS_DIR)
-# Usage: install.ps1 [-Names <name1>,<name2>] [-Prune]
-#   no args        = install all skills/* into target
-#   -Prune         = after install, remove target/<name>/ dirs that are NOT in skills/*
-#                    (prune always scans full target, ignores -Names filter — it's a global cleanup)
+# Install skills/<name>/ into BOTH agent skill dirs:
+#   ~\.claude\skills\<name>\  (Claude Code - native, not configurable)
+#   ~\.agents\skills\<name>\  (pi - native default scan path, agent-neutral namespace)
+# $env:CLAUDE_SKILLS_DIR overrides ONLY the claude target (for testing/CI).
 #
-# PowerShell port of install.sh — same behavior, native cmdlets, no bash dependency.
+# Usage: install.ps1 [-Names <name1>,<name2>] [-Prune] [-Yes]
+#   no args        = install all skills/* into both targets
+#   -Prune         = after install, remove target/<name>/ dirs that are NOT in skills/*
+#                    (prune always scans full target, ignores -Names filter - it's a global cleanup)
+#   -Yes           = with -Prune: remove prod-only skills without asking (still warns loudly).
+#                    Without -Yes, prune asks per skill (default No) and NEVER removes silently:
+#                    a prod skill with no source in skills/ is potentially lost knowledge.
+#
+# PowerShell port of install.sh - same behavior, native cmdlets, no bash dependency.
 
 [CmdletBinding()]
 param(
     [string[]]$Names = @(),
-    [switch]$Prune
+    [switch]$Prune,
+    [switch]$Yes
 )
 
 $ErrorActionPreference = 'Stop'
@@ -17,21 +25,27 @@ $ErrorActionPreference = 'Stop'
 $root = Split-Path -Parent $PSScriptRoot
 $src  = Join-Path $root 'skills'
 
+# Dual install targets - the "canon" is the git repo (skills/); both dirs are installs.
+$targets = @()
 if ($env:CLAUDE_SKILLS_DIR) {
-    $target = $env:CLAUDE_SKILLS_DIR
+    $targets += $env:CLAUDE_SKILLS_DIR
 } else {
-    $target = Join-Path $env:USERPROFILE '.claude\skills'
+    $targets += (Join-Path $env:USERPROFILE '.claude\skills')
 }
+$targets += (Join-Path $env:USERPROFILE '.agents\skills')
 
-if (-not (Test-Path $target)) {
+foreach ($target in $targets) {
+    if (-not (Test-Path $target)) {
         New-Item -ItemType Directory -Force -Path $target | Out-Null
+    }
 }
 
 if ($Names.Count -eq 0) {
     $Names = Get-ChildItem -Path $src -Directory | Sort-Object Name | Select-Object -ExpandProperty Name
 }
 
-foreach ($name in $Names) {
+foreach ($target in $targets) {
+    foreach ($name in $Names) {
         $srcDir = Join-Path $src $name
         $dstDir = Join-Path $target $name
         if (-not (Test-Path $srcDir -PathType Container)) {
@@ -47,15 +61,34 @@ foreach ($name in $Names) {
         }
         Copy-Item -Recurse $srcDir $dstDir
         Write-Host "installed: $name -> $dstDir"
+    }
 }
 
 if ($Prune) {
     $sourceNames = @(Get-ChildItem -Path $src -Directory | Select-Object -ExpandProperty Name)
+    $interactive = -not [Console]::IsInputRedirected
+    foreach ($target in $targets) {
         $installedDirs = Get-ChildItem -Path $target -Directory -ErrorAction SilentlyContinue
         foreach ($dir in $installedDirs) {
             if ($sourceNames -notcontains $dir.Name) {
-            Write-Host "pruning: $($dir.Name) (not in skills/) -> $($dir.FullName)"
-            Remove-Item -Recurse -Force $dir.FullName
+                $rel = $dir.Name
+                $loc = $dir.FullName
+                if ($Yes) {
+                    Write-Warning "prune: $rel (not in skills/) - REMOVED from $loc"
+                    Remove-Item -Recurse -Force $loc
+                } elseif ($interactive) {
+                    Write-Warning "prune: $rel is in prod but has NO source in skills/ - possibly lost knowledge."
+                    $ans = Read-Host "  Remove '$rel'? [y/N]"
+                    if ($ans -eq 'y' -or $ans -eq 'Y') {
+                        Remove-Item -Recurse -Force $loc
+                        Write-Host "removed: $rel"
+                    } else {
+                        Write-Host "kept: $rel (remove manually, or add it to skills/)"
+                    }
+                } else {
+                    Write-Warning "prune skipped: $rel (prod skill without source; non-interactive - nothing removed)"
+                }
+            }
         }
     }
 }

scripts/install.sh

@@ -1,20 +1,31 @@
 #!/usr/bin/env bash
-# Install skills/<name>/ into ~/.claude/skills/<name>/ (or $CLAUDE_SKILLS_DIR)
-# Usage: install.sh [--prune] [name...]
-#   no args        = install all skills/* into target
+# Install skills/<name>/ into BOTH agent skill dirs:
+#   ~/.claude/skills/<name>/  (Claude Code — native, not configurable)
+#   ~/.agents/skills/<name>/  (pi — native default scan path, agent-neutral namespace)
+# $CLAUDE_SKILLS_DIR overrides ONLY the claude target (for testing/CI).
+#
+# Usage: install.sh [--prune] [--yes] [name...]
+#   no args        = install all skills/* into both targets
 #   --prune        = after install, remove target/<name>/ dirs that are NOT in skills/*
 #                    (prune always scans full target, ignores name filter — global cleanup)
+#   --yes          = with --prune: remove prod-only skills without asking (still warns loudly).
+#                    Without --yes, prune asks per skill (default No) and NEVER removes silently:
+#                    a prod skill with no source in skills/ is potentially lost knowledge.
 set -euo pipefail
 
 ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
 SRC="$ROOT/skills"
-TARGET="${CLAUDE_SKILLS_DIR:-$HOME/.claude/skills}"
+
+# Dual install targets — the "canon" is the git repo (skills/); both dirs are installs.
+TARGETS=("${CLAUDE_SKILLS_DIR:-$HOME/.claude/skills}" "$HOME/.agents/skills")
 
 prune=0
+yes=0
 positional=()
 for arg in "$@"; do
   case "$arg" in
     --prune) prune=1 ;;
+    --yes) yes=1 ;;
     *) positional+=("$arg") ;;
   esac
 done
@@ -33,11 +44,14 @@ else
   names=("${positional[@]}")
 fi
 
-mkdir -p "$TARGET"
+for target in "${TARGETS[@]}"; do
+  mkdir -p "$target"
+done
 
-for name in "${names[@]}"; do
+for target in "${TARGETS[@]}"; do
+  for name in "${names[@]}"; do
     src_dir="$SRC/$name"
-  dst_dir="$TARGET/$name"
+    dst_dir="$target/$name"
     if [ ! -d "$src_dir" ]; then
       echo "skip: $name (not found in skills/)" >&2
       continue
@@ -49,15 +63,34 @@ for name in "${names[@]}"; do
     rm -rf "$dst_dir"
     cp -R "$src_dir" "$dst_dir"
     echo "installed: $name → $dst_dir"
+  done
 done
 
 if [ "$prune" -eq 1 ]; then
-  for d in "$TARGET"/*/; do
+  interactive=1
+  if [ ! -t 0 ]; then interactive=0; fi
+  for target in "${TARGETS[@]}"; do
+    for d in "$target"/*/; do
       [ -d "$d" ] || continue
       name="$(basename "$d")"
       if [ ! -d "$SRC/$name" ]; then
-      echo "pruning: $name (not in skills/) → $d"
+        if [ "$yes" -eq 1 ]; then
+          echo "WARN: prune: $name (not in skills/) — REMOVED from $d" >&2
           rm -rf "$d"
+        elif [ "$interactive" -eq 1 ]; then
+          echo "WARN: prune: $name is in prod but has NO source in skills/ — possibly lost knowledge." >&2
+          printf '  Remove "%s"? [y/N] ' "$name"
+          read -r ans
+          if [ "$ans" = "y" ] || [ "$ans" = "Y" ]; then
+            rm -rf "$d"
+            echo "removed: $name"
+          else
+            echo "kept: $name (remove manually, or add it to skills/)"
+          fi
+        else
+          echo "WARN: prune skipped: $name (prod skill without source; non-interactive — nothing removed)" >&2
+        fi
       fi
     done
+  done
 fi

scripts/update.ps1

@@ -22,7 +22,10 @@ $ErrorActionPreference = 'Stop'
 
 $root = Split-Path -Parent $PSScriptRoot
 $skillsSrc = Join-Path $root 'skills'
-$target = if ($env:CLAUDE_SKILLS_DIR) { $env:CLAUDE_SKILLS_DIR } else { Join-Path $env:USERPROFILE '.claude\skills' }
+# Dual install targets — the "canon" is the git repo (skills/); both dirs are installs.
+$targets = @()
+if ($env:CLAUDE_SKILLS_DIR) { $targets += $env:CLAUDE_SKILLS_DIR } else { $targets += (Join-Path $env:USERPROFILE '.claude\skills') }
+$targets += (Join-Path $env:USERPROFILE '.agents\skills')
 
 $commonRoot = if ($env:COMMON_ROOT) { $env:COMMON_ROOT } else { Join-Path $env:USERPROFILE 'projects\.common' }
 $metaMcp = Join-Path $commonRoot 'lib\projects-meta-mcp'
@@ -31,7 +34,8 @@ $internsMcp = Join-Path $commonRoot 'lib\interns-mcp'
 # -- Collect before-versions --------------------------------------------------
 
 $beforeVersions = @{}
-if (Test-Path $target) {
+foreach ($target in $targets) {
+    if (Test-Path $target) {
         Get-ChildItem -Path $target -Directory -ErrorAction SilentlyContinue | ForEach-Object {
             $vf = Join-Path $_.FullName 'SKILL.md'
             if (Test-Path $vf) {
@@ -40,6 +44,7 @@ if (Test-Path $target) {
                 $beforeVersions[$_.Name] = $ver
             }
         }
+    }
 }
 
 # -- Step 1: git pull ---------------------------------------------------------
@@ -144,7 +149,8 @@ Write-Host "[ok] Skills installed." -ForegroundColor Green
 
 Write-Host "[update] Version diff:" -ForegroundColor Cyan
 $changes = $false
-Get-ChildItem -Path $target -Directory -ErrorAction SilentlyContinue | ForEach-Object {
+foreach ($target in $targets) {
+    Get-ChildItem -Path $target -Directory -ErrorAction SilentlyContinue | ForEach-Object {
         $vf = Join-Path $_.FullName 'SKILL.md'
         if (Test-Path $vf) {
             $match = Select-String -Path $vf -Pattern '^version:\s*(\d+\.\d+\.\d+)' -ErrorAction SilentlyContinue | Select-Object -First 1
@@ -156,6 +162,7 @@ Get-ChildItem -Path $target -Directory -ErrorAction SilentlyContinue | ForEach-O
                 $changes = $true
             }
         }
+    }
 }
 if (-not $changes) {
     Write-Host '  (no version changes)'
@@ -166,9 +173,11 @@ if (-not $changes) {
 $newSetup = @()
 Get-ChildItem -Path $skillsSrc -Directory | ForEach-Object {
     $name = $_.Name
-    if ($name -like 'setup-*' -and -not (Test-Path (Join-Path $target $name))) {
-        $newSetup += $name
+    $missing = $false
+    foreach ($target in $targets) {
+        if ($name -like 'setup-*' -and -not (Test-Path (Join-Path $target $name))) { $missing = $true }
     }
+    if ($missing) { $newSetup += $name }
 }
 
 if ($newSetup.Count -gt 0) {

scripts/update.sh

@@ -20,7 +20,8 @@ YES_MODE=false
 
 ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
 SKILLS_SRC="$ROOT/skills"
-TARGET="${CLAUDE_SKILLS_DIR:-$HOME/.claude/skills}"
+# Dual install targets — the "canon" is the git repo (skills/); both dirs are installs.
+TARGETS=("${CLAUDE_SKILLS_DIR:-$HOME/.claude/skills}" "$HOME/.agents/skills")
 
 COMMON_ROOT="${COMMON_ROOT:-$HOME/projects/.common}"
 META_MCP="$COMMON_ROOT/lib/projects-meta-mcp"
@@ -43,8 +44,9 @@ confirm() {
 # ── Collect before-versions ────────────────────────────────────────────────
 
 declare -A BEFORE_VERSIONS=()
-if [[ -d "$TARGET" ]]; then
-    for skill_dir in "$TARGET"/*/; do
+for target in "${TARGETS[@]}"; do
+    [[ -d "$target" ]] || continue
+    for skill_dir in "$target"/*/; do
         name="$(basename "$skill_dir")"
         vf="$skill_dir/SKILL.md"
         if [[ -f "$vf" ]]; then
@@ -52,7 +54,7 @@ if [[ -d "$TARGET" ]]; then
             BEFORE_VERSIONS["$name"]="$ver"
         fi
     done
-fi
+done
 
 # ── Step 1: git pull ────────────────────────────────────────────────────────
 
@@ -133,7 +135,8 @@ ok "Skills installed."
 
 info "Version diff:"
 CHANGES=false
-for skill_dir in "$TARGET"/*/; do
+for target in "${TARGETS[@]}"; do
+    for skill_dir in "$target"/*/; do
         name="$(basename "$skill_dir")"
         vf="$skill_dir/SKILL.md"
         if [[ -f "$vf" ]]; then
@@ -144,6 +147,7 @@ for skill_dir in "$TARGET"/*/; do
                 CHANGES=true
             fi
         fi
+    done
 done
 if ! $CHANGES; then
     echo "  (no version changes)"
@@ -154,8 +158,12 @@ fi
 NEW_SETUP=()
 for skill_dir in "$SKILLS_SRC"/*/; do
     name="$(basename "$skill_dir")"
-    if [[ "$name" == setup-* ]] && [[ ! -d "$TARGET/$name" ]]; then
-        NEW_SETUP+=("$name")
+    if [[ "$name" == setup-* ]]; then
+        missing=false
+        for target in "${TARGETS[@]}"; do
+            [[ ! -d "$target/$name" ]] && missing=true
+        done
+        $missing && NEW_SETUP+=("$name")
     fi
 done
 

skills/browser-cdp/SKILL.md

@@ -1,13 +1,14 @@
 ---
 name: browser-cdp
 author: ours
-version: 0.1.0
+version: 0.1.1
 description: >
   Веб-автоматизация через минимальные CDP CLI-тулы в bash — вместо playwright-mcp
   / Chrome-DevTools-MCP (подход «what if you don't need MCP»). Запуск Chrome с remote
   debugging, навигация, eval JS, скриншоты. Trigger: «браузер», «скрейпинг», «открой
   страницу», «перейди на», «сделай скриншот», «playwright», «веб-автоматизация»,
-  «web scraping», «browser».
+  «web scraping», «browser». Для ЛИЧНЫХ КАБИНЕТОВ оператора (его логины, антибот) —
+  НЕ этот скил, а `browser-operator`.
 ---
 
 # browser-cdp
@@ -20,6 +21,9 @@ description: >
 снять скриншот, собрать данные (скрейпинг). Использовать **вместо** playwright-mcp или
 Chrome-DevTools-MCP.
 
+- ⚠️ **Для личных кабинетов оператора этот путь НЕ годится:** здесь свой Chrome и свой
+  профиль (без его логинов). Нужен браузер оператора — скил `browser-operator`.
+
 ## Процесс
 
 1. **Прочитай полную справку** (обязательно, первый шаг):

skills/browser-operator/SKILL.md

@@ -0,0 +1,128 @@
+---
+name: browser-operator
+author: ours
+version: 0.1.0
+description: >
+  Работа в браузере ОПЕРАТОРА — его Chrome, его профиль, его живые логины: личные
+  кабинеты поставщиков (ЧипДип, ДКО, Промэлектроника, ТМ), Avito, порталы под
+  антиботом. Trigger: «зайди в личный кабинет», «открой ЛК», «собери заказы»,
+  «посмотри в браузере», «нужна его сессия», «ЧипДип/Ozon/Avito», «browser».
+  НЕ для публичных страниц (там сначала обычный fetch/curl) и НЕ для анонимных
+  прогонов (там скил browser-cdp).
+---
+
+# Browser operator — браузер оператора
+
+**Браузер оператора — разделяемый ресурс с его живыми сессиями.** Работай через
+готовый канал своего харнесса и **только под арендой «один водитель за раз»**.
+Не вытаскивай его куки, не логинься сам, не поднимай свой Chrome.
+
+## Когда браузер действительно нужен
+
+Сначала спроси себя, нужен ли браузер вообще:
+
+- **Нет** — публичная страница, API, доки: обычный fetch/curl/поиск. Браузер тут лишний.
+- **Да** — страница требует взаимодействия (клик/форма/навигация), JS-рендер,
+  **его логин** (личный кабинет, Avito), либо портал режет не-браузерный трафик.
+
+## Канал по харнессу (не изобретай свой)
+
+| Харнесс | Чем работать | Аренда |
+|---|---|---|
+| **Hermes** | тул `browser_exec` (демон `browser-use`, тот же профиль оператора) | автоматически: shell-хук `pre_tool_call` берёт аренду и блокирует вызов при чужой |
+| **pi** | тул `browser`: `open` / `read` / `js` / `click` / `screenshot` / `lease` | автоматически внутри тула; `lease` покажет, кто держит |
+| **Claude Code** | MCP `chrome-devtools` (`list_pages`, `navigate_page`, `take_snapshot`, `evaluate_script`, `click`, `fill`, `take_screenshot`) | автоматически: обёртка берёт аренду перед стартом сервера |
+
+**Никогда:** `curl` с куками из его профиля, `browser_cookie3`-выгрузка куки,
+свой `chrome --remote-debugging-port` с пустым профилем (там нет его логинов),
+`pip install`-стек ради одного кабинета.
+
+## Аренда: «один водитель в браузере за раз»
+
+Браузер один. Если его держит другой харнесс — **не ломиться**, сказать «занято,
+держит X» и вернуться позже (или попросить оператора освободить).
+
+Идёшь в браузер **в обход** тула (например, скриптом или `browser-use` из терминала) —
+бери аренду сам:
+
+```bash
+BL="$HOME/.config/browser-harness/bin/browser-lease.sh"
+HOLD="manual:$$"                                        # метка держателя
+MYPID="$(cat /proc/$$/winpid 2>/dev/null || echo 0)"     # НАСТОЯЩИЙ windows-PID
+bash "$BL" acquire --holder "$HOLD" --ttl 900 --pid "$MYPID" --tool browser   # 0 = взял, 3 = занято, 2 = ошибка
+# … работа …
+bash "$BL" release --holder "$HOLD"
+```
+
+**PID — только настоящий.** MSYS `$$` это НЕ windows-PID: по нему живость аренды врёт
+(мёртвый держатель выглядит живым, живой — мёртвым). В bash бери `/proc/$$/winpid`,
+в pi/Node — `process.pid`; не знаешь — передай `0` («неизвестен», живость решит TTL).
+
+**`driver.lock` руками не трогай** (в том числе пустой или «битый» — это окно чужой
+записи): отбор мёртвой аренды делает CLI по `ts`/TTL/мёртвому PID. Чужую аренду не снимай.
+
+Контракт аренды (формат файла, TTL, кого связывать): вики mappa
+`concepts/browser-lease-contract`.
+
+## Как работать в страницах (рецепты)
+
+- **Первым делом — своя вкладка.** `ensure_real_tab()` / `new_tab(url)`; не полагайся
+  на активную вкладку оператора: тяжёлая или аудио-страница подвешивает демон
+  (все вызовы падают в таймаут, хотя `browser-use --doctor` говорит «alive»).
+- **Тяжёлые страницы — читать изнутри, а не обходом.** Если у сайта есть внутренний
+  JSON-эндпоинт, зови его `fetch(path, {credentials:'include'})` из уже открытой
+  страницы: это быстрее и надёжнее десятков навигаций.
+- **По одной штуке за раз, с паузами.** Паузы — в Python/процессе, **не** в JS `await`
+  (иначе `Runtime.evaluate timed out`). Ориентир оператора: 1 запрос, пауза 7–13 с,
+  перекур каждые ~40, стоп после 3 ошибок подряд.
+- **Клики:** сначала дерево доступности (`Accessibility.getFullAXTree`) или
+  `querySelector` → центр элемента (`getBoundingClientRect`) → `click_at_xy` → **проверь
+  результат** отдельным `js(...)`/`page_info()`. Не кликай «на глаз» по скриншоту.
+- **Прогресс — сразу на диск** (jsonl/atomic), а не в конце прогона: длинные обходы
+  обрываются.
+- **Долгие обходы** — в фоновый процесс, а не в цикл интерактивных вызовов.
+
+## Границы: где человек, а где агент
+
+- **Пароли и второй фактор — никогда.** Не вводим и не просим в аргументах командной
+  строки. Уже залогиненная сессия оператора — вот твой доступ.
+- **Попап «Разрешить удалённую отладку?»** — это человеческое подтверждение: агент его
+  не жмёт, а просит оператора нажать «Разрешить» и повторяет попытку.
+- **Деньги/платежи/отправка форм с персональными данными** — только с явным
+  подтверждением оператора.
+- **Секреты и содержимое залогиненных страниц** не пишем в логи, файлы репозитория и
+  вики: в mappa — только агрегаты и идентификаторы.
+
+## Проверенные адреса и факты
+
+- **ЧипДип, кабинет заказов:** `https://www.chipdip.ru/order/list`
+  (⚠️ `/cabinet` и `/orders` отдают 404 — не перебирай наугад, ссылка есть в шапке).
+- Залогиненность видна в шапке кабинета (имя оператора); если видишь форму логина —
+  **сессия потеряна: стоп и скажи оператору**, не логинься сам.
+- `about:blank`-вкладка с титулом-лошадкой в `document.title` = страницу ведёт агент.
+
+## Так делать НЕ надо
+
+| Соблазн | Почему нет |
+|---|---|
+| «Вытащу куки из Chrome и пойду `curl`'ом» | мимо канала и мимо аренды; пароль/2FA оказываются рядом; ломается при смене защиты |
+| «Подниму свой Chrome с отладкой» | там **нет** его логинов → выкинет на логин/капчу, плюс это второй водитель |
+| «Введу логин/пароль через `read -s`» | пароли и 2FA не вводим никогда |
+| «Проверю ещё пяток URL кабинета» | адрес подтверждай по ссылке в интерфейсе, а не перебором |
+| «Налью 20 запросов параллельно, быстрее» | антибот + оператор останавливает такие прогоны; один водитель, одна очередь |
+
+Основание: базовый прогон без скила (2026-09-11) ушёл именно в «куки + curl + пароль»
+мимо канала; скил закрывает этот путь.
+
+## Красные флаги (стоп и перечитай)
+
+- Собираешься вытащить куки / поднять свой браузер / ввести пароль или код.
+- Работаешь с браузером **без** аренды (или ломишься, когда «занято»).
+- Полливаешь запросами без паузы или ждёшь паузу в JS.
+- Пишешь содержимое залогиненных страниц/секреты в файл, лог или вики.
+
+## Вне скоупа
+
+- Анонимные/антидетект-прогоны, свой профиль, `mode: fresh` — скил `browser-cdp`.
+- Облачные браузеры (Browser Use Cloud и прочие) — не берём.
+- Свой stdio-MCP-сервер поверх общего демона — отдельная тема.

skills/code-search/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: code-search
+author: ours
+version: 0.1.0
+description: >
+  Use when searching code for strings, symbols, or usages — "find where X is
+  used", «найди, где используется», "grep for X", "where is X", "search the
+  repo for", any code search, or when deciding HOW to search a codebase. One
+  hard rule: in any tree that can contain node_modules/dist/build/.nuxt,
+  search with `rg` (gitignore-aware) — NEVER `grep -r` (`--include` filters
+  file names, not directory traversal; grep walks every node_modules entry:
+  measured 15+ min never-finishing vs rg 0s on the same tree). Routes:
+  string/symbol search → rg; tracked-files-only → git grep; whole-repo
+  comprehension ("what does module Y do") → interns repo_read (ask-mode);
+  N×M contains audits → interns grep_audit. Skip for web search
+  (web-search), vault search (coworker-search), already-fast tools.
+---
+
+# Code Search
+
+Search code with the fastest correct tool for the question class. The default
+`grep -r` habit is the single biggest time sink in agent work on npm/JS
+projects — the fix is a different binary, not more patience.
+
+## When to use
+
+- Any "where is X used / where does X appear / search the repo for X" request.
+- Deciding HOW to search: rg vs git grep vs intern delegation.
+- A search that "feels slow" — that is a wrong-tool signal, not a slow disk.
+
+## When NOT to use
+
+- Web search → `web-search` skill.
+- Searching the .cowork vault / memory vault → `coworker-search`.
+- A question ABOUT the code ("what does module Y do", "how does the build work") → `interns.repo_read` (delegation, ask-mode per `using-interns`).
+- The right tool is already running and fast.
+
+## Core rule (one sentence)
+
+**In any tree that can contain `node_modules` / `dist` / `build` / `.nuxt` / `vendor`, search with `rg`, never `grep -r`.**
+
+Why — measured on `stostayer.new`, `packages/web` + `apps/web4`, 2026-08-26:
+
+| Fact | Value |
+|---|---|
+| Total files in the two dirs | 113,169 |
+| Of which in `node_modules` + `.nuxt` + `build` | 109,248 (**96%**) |
+| `grep -rn "3590" … --include=*.vue --include=*.js … -l` | **> 15 min, never finished** (RED run: fresh unprompted agent spawned 2× `/usr/bin/grep`, still running at 200s, killed) |
+| `rg -l "3590" …` (same globs) | **0s**, 3 matches |
+| `rg --no-ignore "3590" …` (forced full scan incl. node_modules) | 16s |
+
+Mechanics: `grep -r --include` filters which **file names** get read — it does
+NOT stop **directory traversal**. grep stats/opens every directory entry
+including node_modules (100k+ files) on every search. `rg` reads `.gitignore`
+(+ `.ignore`, `.rgignore`) and skips ignored trees by default — zero flags
+needed. It is already installed on this machine (ripgrep 15.x).
+
+## Routing table
+
+| Question class | Tool | Notes |
+|---|---|---|
+| Find string/symbol/usages in the working tree | `rg -n "pattern" <paths>` | gitignore-aware out of the box. `-l` → filenames only. `-g '*.ext'` to filter. |
+| Only tracked files (clean, deterministic) | `git grep -n "pattern"` | uses the git index; ignores untracked + ignored. Always present even on bare boxes. |
+| "I really must scan generated/vendored too" | `rg --no-ignore` | 16s on the 113k-file tree — still ~50× faster than grep. Never `grep -r` even here. |
+| Whole-repo comprehension ("what does module Y do", "where is X used across the architecture") | `interns.repo_read` | delegation — ask-mode, `using-interns` skill. Packs via repomix + cheap LLM. |
+| N×M contains/not-contains audit (canonical strings across many files) | `interns.grep_audit` | deterministic, no LLM call. |
+
+## Common mistakes / rationalizations
+
+| Excuse | Reality |
+|---|---|
+| "grep works, just slow" | Wrong tool. rg is a drop-in replacement on the same globs: 15 min → 0s on the same tree. |
+| "--include excludes node_modules" | **False.** `--include` filters file *names* that get read, not directories *walked*. grep still traverses all 100k+ node_modules entries. |
+| "Windows/Defender is just slow" | The disk is not the problem — 96% of walked files are build artifacts. rg skips them via .gitignore before the filesystem ever opens them. |
+| "I need to search EVERYTHING" | Use `rg --no-ignore` (16s), still not grep (15 min). Scope with `-g '!node_modules'` if noise is the issue. |
+| "rg isn't installed here" | It is (ripgrep 15.2.0). On a bare box fall back to `git grep` — git is always present. |
+| "It's a one-off, speed doesn't matter" | One-off searches happen 10+ times per session. Each 15-min grep burns an entire agent turn for nothing. |
+
+## Red flags (STOP)
+
+- A search command starting with `grep -r` in any JS/TS/node project — rewrite to `rg` before running.
+- A grep that "hasn't returned" after 30s — it is walking node_modules; kill it, use rg.
+- Search results containing `node_modules/` / `.nuxt/` / `dist/` paths — you scanned garbage; redo with rg (ignore-aware).
+- Writing `--include` and believing directories are excluded.
+
+## Cross-agent applicability
+
+Tool-level rule, works in any agent that can run shell commands (pi, claude,
+codex exec, hermes). `rg` or `git grep` are the always-available core; the
+intern rows are optional delegation for a local `interns` MCP
+(`using-interns` skill). The core rule stands alone without them.
+
+## Out of scope
+
+- Semantic code search / index servers (zoekt, sourcegraph, codesearch) — YAGNI; rg removes the pain without infrastructure.
+- Searching non-code stores (vaults, wikis, the web).
+- Teaching rg's full flag surface — `rg --help` / man.
+- mappa internals: code search stays client-side (operator decision 2026-08-25 — "rg-мост по чек-аутам", outside mappa).

skills/delegate-task/SKILL.md

@@ -1,142 +0,0 @@
----
-name: delegate-task
-author: ours
-version: 0.2.5
-description: >
-  Use when delegating a task to another agent or project via
-  mcp__projects-meta__tasks_create. Triggers: «делегировать таску»,
-  «delegate task», «создать задачу на агента», «поставить задачу агенту»,
-  «tasks_create для». Does NOT apply to self-assigned tasks on your own
-  board («создать задачу себе», «task for myself», «поставить себе задачу»
-  → using-tasks), to work you do yourself, or to workshop-internal tasks.
----
-
-# delegate-task
-
-Унифицированный формат постановки задач на агентов через `mcp__projects-meta__tasks_create`. Обеспечивает что каждая делегированная задача содержит: обязательные скилы (императивный invoke), pre-flight разрешения, steering-loop поля (notify/weight/allow_upgrade).
-
-## When to use
-
-Перед каждым вызовом `mcp__projects-meta__tasks_create` для другого проекта или агента.
-
-**Активируется:** «делегировать таску», «delegate task», «создать задачу на агента», «поставить задачу агенту», «tasks_create для».
-
-**Не применяется:**
-- Работа которую выполняешь сам в текущей сессии.
-- Self-assigned таски на своей доске («создать задачу себе», «task for myself», «поставить себе задачу») → `using-tasks`, не делегирование. Дизамбигуатор: «на агента»/«агенту»/«в проект X» = делегирование; «себе»/«myself» = своя доска.
-- Workshop-internal таски (`.workshop/.tasks/` — workshop-meta, не делегирование).
-- `tasks_create` с `target=agenda` (cross-project agenda — не делегирование агенту).
-
-## Inputs
-
-- `target_project` — qualified `<owner>/<repo>` (обязательно)
-- `slug` — kebab-case latin
-- Краткое описание задачи (цель + acceptance criteria)
-- `weight` — `cheap-ok | needs-claude | needs-human`
-- `notify` — slug проекта-комиссионера (кому писать inbox при close/park)
-- `allow_upgrade` — `true/false` (опционально; разрешить ли fallback на tier выше если нет matching backend)
-
-## Steps
-
-### 1. Pre-flight gate (6 вопросов пользователю)
-
-Спросить **до** составления тела задачи:
-
-0. **Критическая инфраструктура?** — задача меняет: поллер/агент-раннер, MCP серверы (projects-meta, interns), механизм claim/close/heartbeat, deploy-инфру (traefik, docker, systemd), CI/CD пайплайны, git hooks.
-   - Если **да** → `weight: needs-human` принудительно, без обсуждения. Объяснить пользователю почему.
-   - Если **нет** → идти дальше.
-1. **Интерны — разрешены?** (да/нет, per задача)
-2. **Автопуш — разрешён?** (да/нет, per задача)
-3. **Контекстные скилы сверх дефолтов?** — предложить по содержанию задачи (например `claude-api` для работы с Anthropic SDK, `frontend-design` для UI, `using-interns` если интерны разрешены), пользователь утверждает.
-4. **notify — кому докладывать о завершении/затыке?** (slug проекта; обычно `.workshop` или `OpeItcLoc03/workshop`)
-5. **Session-break после этой задачи?** — нужен ли разрыв сессии после её закрытия (domain-switch, milestone, heavy infra)?
-   - Если **да** → проставить `session_break` в теле задачи (см. шаблон): `true` или строка-hint с названием следующего трека. `using-tasks` остановится после close и предложит завершить сессию, не клеймя следующую задачу.
-   - Если **нет** → поле не добавлять (дефолт — агент продолжает `claim-next`).
-
-### 2. Составить тело задачи по шаблону
-
-Секции строго по порядку:
-
-```
-<Цель — одно-два предложения. Acceptance criteria если есть.>
-
-## Обязательные скилы — вызвать до начала работы
-
-- invoke `tdd-criteria` — до написания кода
-- invoke `using-tasks` — для управления статусом задачи
-- invoke `project-discipline` — дисциплина коммитов/пушей
-- invoke `using-wiki` после закрытия — заингесть .wiki/concepts/<slug>.md
-[если кросс-проектная: - invoke `using-projects-meta` — cross-project tasks/wiki]
-[контекстные скилы из шага 1.3]
-
-**TDD:** да | нет — <причина>
-**Разрешения:** интерны: да/нет | автопуш: да/нет
-**weight:** cheap-ok | needs-claude | needs-human
-**notify:** <commissioning-project-slug>
-[**allow_upgrade:** true/false]
-[**session_break:** true | "<следующий трек / hint>"]   # optional — using-tasks остановится после close, не клеймит следующую задачу
-```
-
-**Когда ставить `session_break`** (опционально; по умолчанию НЕ ставить — это маркер реальной границы, не дефолт). Три случая:
-
-1. **Смена домена / репо** — задача завершает один трек перед переходом на несвязанный.
-2. **Milestone-задача** — последняя в группе sub-tasks одной фичи.
-3. **Тяжёлая инфра-задача** — shared checkout, migrations, deploy — где разумно остановиться и проверить состояние.
-
-Значение: `true` (следующий трек = «см. STATUS.md») либо строка-hint с названием следующего трека. Потребитель — `using-tasks` v1.2.0+ (Task completion step 6): после close печатает `🔚 SESSION BOUNDARY …` и останавливается, не клеймя следующую задачу. Дизайн: `.wiki/concepts/delegate-task-session-break.md`.
-
-**Почему `invoke` а не триггер-фраза:** AGENTS.md ненадёжен (уплывает при compression, слабые модели игнорируют). Тело задачи читается активно — императив `invoke` это прямая команда, не пассивный матчинг.
-
-### 3. Dry-run preview
-
-`tasks_create(confirm=false)` — показать пользователю preview до реального коммита.
-
-### 4. Подтверждение и создание
-
-После OK пользователя: `tasks_create(confirm=true)`.
-
-### 5. Парная review-таска (только для impl-задач)
-
-Если задача имплементационная — создать парную `<slug>-review` (status=blocked, blocker=`<slug>`). Пропустить для: pointers-тасок, ops-тасок, research-тасок, любых non-impl.
-
-**`weight` review-таски — наследовать от impl-таски, но не ниже `needs-claude`** (проставлять явно при `tasks_create`):
-
-- impl `needs-human` → review `needs-human` (критично-инфраструктурное изменение нельзя ревьюить слабым tier'ом — ревью наследует строгость impl).
-- impl `needs-claude` → review `needs-claude`.
-- impl `cheap-ok` → review `needs-claude` (флор: review дисциплинарно-критична, см. What NOT to do — cheap-ok сюда не опускать).
-
-Без явного `weight` поллер не маршрутизирует review-таску (reconciler её пропускает) — поэтому проставлять всегда, даже когда impl и review совпадают по tier'у.
-
-### 6. Downstream-задача для ЖИВОЙ сессии → требовать task + inbox-письмо
-
-Если тело задачи **поручает агенту самому создать downstream-задачу** для другого проекта, где работает **живая интерактивная сессия** (напр. прог сам ставит deploy-таску админу), — в ТЗ **явно потребуй И `tasks_create`, И inbox-письмо** тому проекту (`<target>/.claude-inbox/<ts>-<from>.md`).
-
-Причина: таска на борде живую сессию **НЕ пингует**. Поллер подхватит по `Weight`/`Notify`, но живая интерактивная сессия узнаёт только через inbox-монитор / Stop-хук — т.е. через письмо. ТЗ, требующее лишь `tasks_create`, оставляет downstream-таску висеть незамеченной, и кто-то доделывает пинг руками.
-
-Правило: poller-driven таргет → `Weight`/`Notify` обязательны; live-сессия → inbox-письмо обязательно; **не уверен, поллер или живой — требуй ОБА.** Это же правило применяй, когда пингуешь пира сам: task + letter, не только task.
-
-## Failure modes
-
-- **Пользователь отказывает на pre-flight** → abort, задачу не создавать.
-- **Пользователь отклоняет dry-run preview** → abort.
-- **notify не указан** → переспросить, не пропускать молча. Без notify steering-loop не замыкается.
-- **weight не указан** → переспросить. Без weight поллер не знает кому отдать задачу.
-- **tasks_create упал** → сообщить пользователю, не делать retry без явного запроса.
-
-## Side effects
-
-- Создаёт таску в target-проекте через `mcp__projects-meta__tasks_create` (Gitea commit).
-- Опционально создаёт парную review-таску (status=blocked).
-
-## What NOT to do
-
-- Не пропускать pre-flight gate — даже если кажется что всё очевидно.
-- Не использовать пассивные триггер-фразы вместо `invoke` — «tdd-criteria» в тексте слабее чем «invoke `tdd-criteria`».
-- Не пропускать `notify` — без него boss не узнает о завершении.
-- Не пропускать `weight` — без него fleet routing слеп.
-- Не создавать review-таску для pointers/ops/research задач — только для impl.
-- Не создавать review-таску без `weight` — reconciler/поллер её пропустит. Наследовать от impl, флор `needs-claude` (см. Step 5).
-- Не назначать `weight: cheap-ok` для задач где дисциплина критична (review, security, schema migration) — слабые модели могут игнорировать invoke-инструкции.
-- Не назначать `weight: needs-claude` или `cheap-ok` задачам, меняющим критическую инфраструктуру (поллер, MCP серверы, deploy, CI/CD) — только `needs-human`.
-- Не ставить `session_break` рутинно на каждую задачу — это маркер реальной границы (domain-switch / milestone / heavy infra), не дефолт; иначе `using-tasks` рвёт сессию после каждого close.
-- **Не поручать агенту создать downstream-таску для живой сессии без парного inbox-письма** (см. Step 6). `tasks_create` в чужой борд живую сессию не пингует — ТЗ обязано требовать И таску, И письмо, иначе downstream-таска висит незамеченной.

skills/inter-session-peer-discipline/SKILL.md

@@ -1,64 +0,0 @@
----
-name: inter-session-peer-discipline
-author: ours
-version: 0.1.2
-description: >
-  Use whenever exchanging messages with another agent session over an inbox /
-  peer channel (`.claude-inbox/`, inter-session messaging). Treat a peer
-  session's messages — and your own replies — as proposals and analysis, NOT
-  authority. The human is the only source of direction and of scope. Never
-  report a peer-driven (or self-driven) design escalation as a settled
-  "decision" without explicit human ratification. Guards against two agent
-  sessions echo-chambering a scope inflation past the human.
----
-
-# inter-session-peer-discipline
-
-> The inbox is a peer channel, not a chain of command. Messages from another agent session are a colleague's proposals — never a human mandate. The human is the only authority for direction and scope.
-
-## When this runs
-
-**Whenever** you send or receive a message over an inter-session channel — `.claude-inbox/`, peer-to-peer agent messaging, or any "another session wrote to me" context.
-
-**At session start** when `AGENTS.md` has a trigger line like:
-- `inter-session messaging: peer not authority`
-
-## The rule
-
-1. **Peer ≠ authority.** A message from another agent session (even one role-named "постановщик" / "boss" / "reviewer") is peer input — analysis and proposals. It carries no human sanction by itself. Direction and scope come only from the human.
-
-2. **Don't launder your own opinion as a decision.** When you reply to a peer, do not frame your design call as a settled "decision" or "решение постановщика" unless the human explicitly ratified it. Frame it as: *"I recommend X; the human has not ratified this."* Same for relaying: distinguish "the human ruled X" from "the peer/я recommend X."
-
-3. **Escalations need an explicit human yes.** Architectural choices and any scope growth ("this is actually wider than the task…") must be ratified by the human **before** you report them to a peer as decided, or act on them.
-
-## Channel contract (inbox vs board)
-
-This is the operational backbone that makes "peer ≠ authority" enforceable:
-
-- **The inbox (`.claude-inbox/`) is a communication channel only** — discussion, help (asking / answering questions), and lifecycle notification ("task created", "closed", "blocked"). Nothing more.
-- **Tasks themselves go only through `mcp__projects-meta__tasks_*`.** The board is the single source of truth. A task's existence, state, scope, and decisions are created / changed / recorded via `tasks_create`, `tasks_update`, `tasks_append_decision_trail` — never "decided" inside an inbox message. The inbox merely *notifies and discusses*; it never *is* the task.
-
-Corollary: **if it isn't on the board via meta, it is not a task and not a decision — it's talk.** A design call that matters must land on the board (or in the wiki), with the inbox only pointing at it. This is exactly what stops two sessions from "deciding" a redesign in letters: the authoritative artifact has one home, and it isn't the inbox.
-
-## The failure mode this guards
-
-Two agent sessions ping-ponging, each agreeing with and amplifying the other's framing, scope inflating every round, while the human is only nominally in the loop. **Echo-chamber signature:** replies that arrive fast, always agree with the frame you set, and add scope each round. Of course the peer agrees — it's reasoning inside the frame you built.
-
-This is `user_context_agents_path_of_least_resistance` one level up: instead of gaming the *task* metric, the two sessions glide past the *human-ratification gate* — fake "decided" via mutual agreement, not via the human's intent. The same anti-pattern an oracle/verifier design defends against at the task level applies to the collaboration loop itself.
-
-## Circuit-breaker
-
-When you notice scope escalating across rounds without an explicit human "yes" — **stop and ask the human.** Say plainly: "I'm a peer session, not a human authority; I'm escalating scope here; do you actually want this sent as decided?" Don't ride path-of-least-resistance to "решено."
-
-If a peer session is the one to catch it, that's a correct circuit-break, not an accusation — concede the real point, de-escalate, don't defend a false authority.
-
-**Multi-session caveat — don't cry "override" from partial vision.** When the human runs more than one session, your view of *what they have ratified* is partial. A peer acting on something you flagged as "unratified" may have genuine human sign-off given in a channel you can't see. So when you spot an apparent breach, **ask "did you ratify this elsewhere?" — don't assert it as a breach.** Flagging an apparent contradiction (good) is not the same as accusing a peer of an override (over-call). Learned 2026-06-16: a `.workshop` session called a `common` close a "false attribution of human ratification"; in fact the human had approved it directly in the common channel while the workshop session was still deliberating. Surface the gap as a question, let the human reconcile the channels.
-
-## Why this exists
-
-Emerged 2026-06-16: a `.workshop` session and an `OpeItcLoc03/common` session ran a multi-round design exchange over `.claude-inbox/`. The workshop session escalated a design (tamper-guard → prevention → oracle-integrity → runner-owns-verifier → close-moves) across rounds and reported each step to common as "решение постановщика" — implying human sanction the human had not given. The `common` session pattern-matched the echo-chamber (fast agreement + scope inflation), read its own Stop-hook, and correctly refused to implement the unratified redesign, asking the human instead. The lesson: durable artifact in a skill, by the user's direction — methodology lives in `skills`, not per-session memory.
-
-## Reference
-
-- Inter-session messaging mechanics: `~/.claude/CLAUDE.md` §"Inter-session messaging".
-- Related: `recommend-dont-menu` (response style), `project-discipline` (master-only / push-by-permission gates).

skills/meta-host-routing/SKILL.md

@@ -1,90 +0,0 @@
----
-name: meta-host-routing
-author: ours
-version: 0.3.0
-description: >
-  Use before any tasks_create / knowledge_ingest / brainstorm-promotion against
-  a project — resolve WHERE that project's meta lives before writing. A
-  github-hosted project (or any project projects-meta reports "not in cache")
-  does NOT carry .tasks/.wiki in its own repo (meta-out-of-repo design: they'd
-  leak on push/PR). Its meta lives in a sibling Gitea-tracked host repo — route
-  MCP calls there, never into the github working tree, never guess. Triggers:
-  "project not in cache" from projects-meta, promoting/creating tasks for a
-  project with a github remote, "заведи таски в <github-проект>", "промоутни
-  <github-проект>". Skip for a normal Gitea project already known to
-  projects-meta — there the route is direct.
----
-
-# meta-host-routing
-
-> A project's code repo is not always where its meta lives. Before writing tasks or wiki, resolve the **meta-host**. Github-hosted projects keep their `.tasks/`/`.wiki/` in a sibling Gitea repo — never in the github tree. Never guess the target.
-
-## When this runs
-
-Before any `mcp__projects-meta__tasks_create`, `mcp__projects-meta__knowledge_ingest`, or brainstorm promotion, when **either**:
-
-- the target project's local clone has a **github remote**, OR
-- `projects-meta` returns **"project not in cache"** for the target.
-
-Both are signals that the project follows the **meta-out-of-repo** design: its meta is intentionally absent from its own repo.
-
-**Skip** when the target is a normal Gitea project already known to `projects-meta` (`meta_status` lists it / a `tasks_create` dry-run succeeds) — there the route is direct, no resolution needed.
-
-## Why meta is out of the repo
-
-Per the `meta-out-of-repo` design: `.tasks/`, `.wiki/`, `.claude/` must not be committed into a repo that gets pushed to a public / shared / forked-upstream remote — the "kitchen" (notes, tasks, local skills, agent instructions) would leak. A global `core.excludesFile` ignores those paths, so github-hosted projects carry **no** meta in-tree by design. The meta still exists — it lives in a Gitea-tracked **host** repo and syncs through `projects-meta`.
-
-## Steps
-
-1. **Detect.** Check the target's local remote (`git remote -v`) and/or a `projects-meta` dry-run. Github remote OR "not in cache" → meta-out-of-repo project; continue. Otherwise → direct Gitea route, this skill does not apply.
-
-2. **Resolve the meta-host**, in priority order:
-   - **(a) Dedicated meta-host (preferred).** Is there a Gitea repo named **`meta-<project>`**, holding only `.wiki/`+`.tasks/` (no code)? That is its meta-host. Once synced, `projects-meta` tracks it as a project `<owner>/meta-<project>` — a `tasks_create` dry-run against that resolves. Canonical example: code `github.com/OpeItcLoc03/yt-tools` → meta-host **Gitea `OpeItcLoc03/meta-yt-tools`**. **Naming is `meta-<project>`, NOT `<project>`** — per the `meta-out-of-repo` design: the bare `<project>` name on Gitea must stay free for a possible code **mirror** of the github repo. (Local clone convention, if ever needed: `~/projects/.meta/<project>/`.)
-   - **(b) Shared host (transitional).** No dedicated host yet → grep sibling Gitea repos, **start with `.common`** (`~/projects/.common/`), for the project name:
-     ```
-     grep -ril "<project-name>" ~/projects/.common/.tasks/ ~/projects/.common/.wiki/
-     ```
-     The host is whichever Gitea repo already holds that project's tasks/wiki.
-   - **(c) Neither** → the project has no meta-host yet (Failure modes — STOP and ask, or bootstrap one per "Bootstrapping a new meta-host").
-
-   > Note: `.common` was yt-tools' shared host until 2026-05-27, when yt-tools graduated to its own dedicated host (`OpeItcLoc03/meta-yt-tools`). `.common` now holds only yt-tools' done-task archive. Prefer giving a maturing project its own host over piling onto `.common`.
-
-3. **Route there.** Send every `tasks_create` / `knowledge_ingest` to the host's qualified `<owner>/<repo>` (a dedicated host = `<owner>/meta-<project>`; a shared host = e.g. `OpeItcLoc03/common`). On a shared host, namespace entries with a `<project>-` slug prefix.
-
-4. **Never** write `.tasks/`/`.wiki/` files into the github working tree, and **never** invent a target when resolution is ambiguous (Failure modes below).
-
-## Bootstrapping a new meta-host
-
-When a project graduates to its own dedicated host (or a github project needs one):
-
-1. Create a Gitea repo named **`meta-<project>`** (meta-only, `auto_init:false`) via the API with the admin token (`~/.config/projects-mcp/auth.toml`). Do **not** use the bare `<project>` name — keep it free for a code mirror.
-2. Clone it, build canonical `.wiki/` (CLAUDE.md, index.md, log.md, overview.md, raw/, concepts/, entities/, packages/, sources/) + `.tasks/STATUS.md` (emoji legend header).
-3. **`git add -f .wiki .tasks`** — the global `core.excludesFile` (`~/.config/git/ignore`) ignores `.wiki/`/`.tasks/`. Existing hosts track them because they were added *before* that ignore existed; a fresh clone needs `-f` or `git add -A` silently stages nothing. This is the one gotcha that will waste a commit if missed.
-4. Commit, push. `projects-meta` picks it up on its next sync (it may not be in cache until then — see Failure modes).
-5. If migrating off a shared host: move open tasks + design concepts to the new host, leave the done-task archive behind under a relocation marker, and replace moved concept docs with pointer stubs so back-references don't dead-end.
-
-## Failure modes
-
-- **No Gitea repo tracks this project** → STOP. Ask the user whether to bootstrap a dedicated host (preferred) or attach to a shared one. Do **not** default to writing into the github repo — that reintroduces the leak meta-out-of-repo exists to prevent.
-- **Just-created meta-host not yet in `projects-meta` cache** → `tasks_create`/`knowledge_ingest` return "not in cache" until a sync runs. Either trigger a sync, or write the initial `.tasks/STATUS.md` / `.wiki/` content directly via git (as in Bootstrapping) and let the MCP pick it up next sync.
-- **Multiple Gitea repos reference the project** → STOP, ask which is canonical. Don't pick by guess.
-- **projects-meta cache stale** ("not in cache" could be staleness, not meta-out-of-repo) → run a sync / `meta_status` freshness check first (see `using-projects-meta` Step 0) before concluding the project is github-only.
-
-## Interaction with workshop-promote-brainstorm
-
-`workshop-promote-brainstorm`'s domain branch currently **aborts** on "project not in cache". With this skill active, that abort becomes a resolve step: find the meta-host, then promote into it. This skill is the routing primitive; promote-brainstorm (and ad-hoc `tasks_create`) consult it.
-
-## What NOT to do
-
-- Don't write meta into a github working tree "because the project is right there" — that's the exact path-of-least-resistance leak meta-out-of-repo prevents.
-- Don't treat "project not in cache" as "project doesn't exist" — it means "meta is hosted elsewhere," resolve it.
-- Don't guess the meta-host when grep is ambiguous — ask.
-- Don't apply this to normal Gitea projects already in `projects-meta` — adds a pointless resolution step.
-
-## Cross-agent note
-
-References Claude Code MCP tool names (`mcp__projects-meta__*`). On non-CC platforms substitute the projects-meta equivalents; the routing logic is platform-independent.
-
-## Why this exists
-
-Codified 2026-05-27 after an agent, asked to promote a yt-tools feature, found yt-tools "not in cache" and started writing tasks directly into the github repo — instead of recalling that yt-tools' meta lives in `.common`. The `meta-out-of-repo` design existed only as an archived workshop concept doc (never triggers). This skill makes the routing rule fire at the moment of action.

skills/ops-browser/SKILL.md

@@ -0,0 +1,90 @@
+---
+name: ops-browser
+author: ours
+version: 0.1.0
+description: >
+  Use when a task needs a real browser — личный кабинет, заказы, чеки, yt-digest,
+  скриншот живого сайта, «дёрни внутренний API». Свой СКРЫТЫЙ браузер агента:
+  отдельный профиль, CDP, `fetch()` ИЗ страницы, хендофф человеку для пароля/капчи.
+---
+
+# ops-browser — свой скрытый браузер агента
+
+**Есть задача, которой нужен браузер? Работай в своём браузере, скрыто, и не подсовывай куки.**
+Профиль владеет сессией сам (куки продлеваются браузером, а не руками) — это и есть лечение
+боли «куки протухли».
+
+## Когда ЭТОТ инструмент, а когда другой
+
+| Ситуация | Чем работать |
+|---|---|
+| Публичная страница без логина | `web_search` / `web_extract` / curl — браузер не нужен |
+| Личный кабинет, заказы, чеки, внутренний API сайта, антибот | **`ops-browser.sh`** (этот скил) |
+| Нужны ЕГО логины и ЕГО Chrome (Avito, кабинеты поставщиков) | канал оператора: Hermes `browser_exec` / pi тул `browser` / CC `chrome-devtools` — всё под арендой `driver.lock` |
+| Посмотреть глазами, кликнуть по живому сайту, показать ему | панель предпросмотра (`desktop_preview` + `drive_preview`) — без JS, только текст/клики |
+
+`ops-browser` не заменяет канал оператора: там его сессии, здесь — **мой** профиль.
+И то и другое живёт под правилом «один водитель» (у ops свой замок `ops.lock`).
+
+## Команды
+
+```bash
+OB="$HOME/.config/browser-harness/bin/ops-browser.sh"
+bash "$OB" start                    # headless + аренда (окон нет)
+bash "$OB" open https://site/path   # перейти
+bash "$OB" read 2000                # видимый текст страницы
+bash "$OB" eval 'fetch("/api/x",{credentials:"include"}).then(r=>r.json()).then(j=>JSON.stringify(j))'
+bash "$OB" screenshot [path]         # PNG, печатает путь
+bash "$OB" cookies https://site      # имена кук (без значений)
+bash "$OB" status                    # аренда + CDP + текущая страница
+bash "$OB" stop                      # ШТАТНО закрыть и отпустить
+bash "$OB" handoff <url>             # человеку: пароль/2FA/капча (см. ниже)
+```
+
+`eval` выполняет JS **в контексте страницы** — значит `fetch()` идёт с её куками и заголовками:
+так дёргают внутренние эндпоинты приложения (то, что недоступно извне и чего не умеет панель).
+
+## Хендофф человеку (пароль, 2FA, капча, согласие)
+
+Останавливаюсь и отдаю экран **сам**, без «скажи готово»:
+
+1. `bash "$OB" handoff <url>` — закрывает headless (профиль нельзя открыть дважды) и поднимает
+   **видимое** окно ТОГО ЖЕ профиля на нужной странице;
+2. человек вводит, что нужно (пароль/2FA/капчу вводит только он);
+3. признак успеха ловлю сам: URL ушёл со страницы логина/auth **или** выросли куки домена;
+4. штатно закрываю окно и возвращаюсь в headless — логин остался в профиле.
+
+Скриншот делаю **до** шага (что от человека хотят) и **после** (что получилось); **во время ввода
+пароля не снимаю**. Если признак успеха не увидел — окно остаётся открытым, а я говорю об этом прямо.
+
+## Границы (не двигаются)
+
+- Пароли, 2FA, капчу — **вводит человек**. Я к ним не подхожу.
+- Деньги, оформление заказов, формы с перс.данными — только с явного согласия оператора.
+- Куки не выгружаю и не расшифровываю; содержимое залогиненных страниц не уходит в логи/вику.
+- Антибот-челленджи не обхожу; если сайт невзлюбил `headless` — это повод для `handoff`, а не для трюков.
+
+## Грабли (стоили времени, проверены живьём)
+
+- **Закрывать только штатно** (`stop` → `Browser.close`). Жёсткий kill может не сбросить профиль →
+  потеря логина. Сессионные куки (без срока) перезапуск не переживают по дизайну — настоящие логины живут.
+- **MSYS-пути**: нативным программам нужен вид `C:/...` (`cygpath -m`), а `powershell -File` —
+  только `C:\...` (`cygpath -w`). Иначе «модуль не найден» / «файл .ps1 не найден».
+- **Экранирование PowerShell внутри bash-строки тихо ломается** (`$_` подменяется) — PS-запросы
+  держим в отдельных `.ps1`.
+- **Профиль нельзя открыть дважды** — перед видимым окном headless обязан остановиться (это делает `handoff`).
+- **Профиль**: `~/.config/browser-harness/profiles/ops`; порт CDP: `OPS_CDP_PORT` (9346).
+
+## Аренда
+
+```bash
+BL="$HOME/.config/browser-harness/bin/browser-lease.sh"
+bash "$BL" --lock ops status        # состояние ops-замка (у Chrome оператора — driver.lock)
+```
+
+Чужой держатель `ops.lock` → `start` честно отказывает (rc=1). Мёртвый держатель отпускается по PID/TTL.
+Идёшь в браузер **сам** (в обход `ops-browser.sh`)? Возьми `ops.lock` так же, как любой другой харнесс.
+
+Контракт: mappa `concepts/ops-browser-contract` (проект `pi-extensions`),
+требования `requirements:42`, план `plan:35`. Исходники: репо `pi-extensions/scripts/browser/`
+(установка `just install-browser`).

skills/project-bootstrap/README.md

@@ -24,16 +24,11 @@ clearly intends to turn into a workspace.
 
 ## Prerequisites
 
-`project-bootstrap` does not lay out `.wiki/` or `.tasks/` by itself — it
-delegates to two companion skills, which must be installed on the machine
-running it:
-
-- [`setup-wiki`](../setup-wiki/) — creates the canonical `.wiki/` layout.
-- [`setup-tasks`](../setup-tasks/) — creates the canonical `.tasks/` layout.
-
-If either is missing, `project-bootstrap` stops with a clear error rather
-than falling back to ad-hoc creation. This keeps layout drift between
-projects bootstrapped at different times debuggable.
+Мета в сервисе (решения 14/15): вики и таски проекта живут в **mappa**
+(`using-wiki` / `using-tasks` v2 — mappa-тулы), файловый `.wiki/` / `.tasks/`
+не создаётся. `setup-wiki` / `setup-tasks` умерли (нечего настраивать);
+для проектов вне mappa файловый layout создаётся ad-hoc по канону
+Karpathy / `.tasks/` (см. using-wiki/using-tasks, legacy-раздел).
 
 ## What it creates
 
@@ -42,9 +37,9 @@ projects bootstrapped at different times debuggable.
 | `.git/` | `git init` | Skipped if repo already initialized. |
 | `.gitignore` | `assets/.gitignore.template` | Skipped if file exists. |
 | `README.md` | minimal stub | Skipped if file exists. |
-| `.wiki/` | delegated to `setup-wiki` | Karpathy LLM Wiki layout — `CLAUDE.md`, `index.md`, `log.md`, `overview.md`, `raw/`, `entities/`, `concepts/`, `packages/`, `sources/`. |
-| `.tasks/` | delegated to `setup-tasks` | Canonical board — `STATUS.md` plus per-task `<task-slug>.md` files. |
-| `AGENTS.md` | `assets/AGENTS.md.template` | **Canon** — skill triggers (`use project wiki`, `use task management system`, etc.). On non-Windows hosts, swap the `we're on Windows` line for `we're on Linux` / `we're on macOS`. On upgrade, the template is treated as a canonical set and merged idempotently — only missing trigger lines are appended after user confirm. Re-runs are no-ops. |
+| вики | mappa (`using-wiki`) | сущности `type=wiki` в сервисе; файловый layout — только вне mappa (легаси). |
+| таски | mappa (`using-tasks`) | сущности `type=task` в сервисе; файловый `.tasks/` — только вне mappa (легаси). |
+| `AGENTS.md` | `assets/AGENTS.md.template` | **Canon** — mappa-agnostic generic triggers (caveman, pull remote before work, tdd, interns, recommend, platform). Mappa-специфичные триггеры (`inbox monitor: raise on start`, `session sync: write to mappa`, `use project wiki`, `use task management system`, `check across all projects`) инжектятся через mappa-bootstrap (Step 5.7.2). On non-Windows hosts, swap the `we're on Windows` line for `we're on Linux` / `we're on macOS`. On upgrade, the template is treated as a canonical set and merged idempotently — only missing generic trigger lines are appended after user confirm. Re-runs are no-ops. |
 | `CLAUDE.md` | generated pointer | `Canon is AGENTS.md. Read AGENTS.md.` — legacy pointer for tooling that looks for the old name. |
 | `.wiki/concepts/bootstrap-manifest.md` | generated | Records which skill versions initialized the project, so cross-project layout drift is debuggable. |
 
@@ -55,11 +50,11 @@ projects bootstrapped at different times debuggable.
    found, what will be created, what will be skipped.
 2. **Confirm.** One question, one confirmation. Nothing is written before the
    user agrees.
-3. **Steps 1–5.** Create or skip each piece in order — git, README, `.wiki/`,
-   `.tasks/`, `AGENTS.md` + `CLAUDE.md` pointer. Steps 3 and 4 delegate to the setup-skills.
+3. **Steps 1–5.** Create or skip each piece in order — git, README, вики/таски
+   (mappa, см. using-wiki/using-tasks), `AGENTS.md` + `CLAUDE.md` pointer.
 4. **Step 5.5.** Write `bootstrap-manifest.md` recording the versions of
-   `project-bootstrap`, `setup-wiki`, `setup-tasks`, `project-discipline`,
-   `setup-interns`, and `using-interns` used.
+   `project-bootstrap`, `setup-interns`, and
+   `using-interns` used.
 5. **Step 5.6.** Skill dependencies check. Walk the canonical trigger list
    in `AGENTS.md`, look each up in an embedded `trigger → fulfiller` map,
    detect what's missing on this host (`~/.claude/skills/<name>/SKILL.md`
@@ -105,12 +100,11 @@ target with `CLAUDE_SKILLS_DIR=/path bash scripts/install.sh …`.
 
 ## See also
 
-- [`setup-wiki`](../setup-wiki/) — companion, owns `.wiki/` layout.
-- [`setup-tasks`](../setup-tasks/) — companion, owns `.tasks/` layout.
-- [`using-wiki`](../using-wiki/) — runtime policy for working with `.wiki/`.
-- [`using-tasks`](../using-tasks/) — runtime policy for working with `.tasks/`.
-- [`project-discipline`](../project-discipline/) — cross-project rules
-  activated by the `follow project discipline` trigger.
+- [`using-wiki`](../using-wiki/) — runtime policy for the mappa wiki (v2).
+- [`using-tasks`](../using-tasks/) — runtime policy for the mappa task board (v2).
+- kzntsv-flavored cross-project discipline (activated per-project by
+  `mappa-bootstrap`, which selects the methodology flavor) — moved to
+  `victor/mappa-vitya-skills` (легаси, поглощено монорепо) — mappa-kzntsv-project-discipline.
 - [`setup-interns`](../setup-interns/), [`using-interns`](../using-interns/) —
   pair behind the `delegate to interns when allowed` trigger; cheap-LLM
   delegation under a per-session permission grant.

skills/project-bootstrap/SKILL.md

@@ -1,12 +1,15 @@
 ---
 name: project-bootstrap
 author: ours
-version: 2.0.0
+version: 3.3.0
 description: >
   Initializes or upgrades a project in the current folder: git, .gitignore, README.md,
   .wiki/ using Karpathy's method, .tasks/ for task tracking, AGENTS.md (canon) with
   skill triggers + CLAUDE.md legacy pointer.
   Creates remote Gitea repo and syncs projects-meta cache for greenfield projects.
+  Includes the mappa-bootstrap-project module (v3, решение 4 mappa-as-product):
+  mappa MCP connect + mappa-конвенции + методика-install (версия в манифест).
+  Creates the `.mappa` marker (wiki:3340) so the folder is a mappa project.
   Use this skill when the user says "initialize project", "bootstrap", "setup project",
   "upgrade project", "add wiki", "add tasks", "start project", "set everything up",
   "create new project", or launches the agent in a new folder and wants a full setup.
@@ -34,6 +37,7 @@ ls -A 2>/dev/null | grep -q . && echo "empty:no" || echo "empty:yes"
 [ -d .tasks ] && echo "tasks:yes" || echo "tasks:no"
 [ -f CLAUDE.md ] && echo "claude:yes" || echo "claude:no"
 [ -f README.md ] && echo "readme:yes" || echo "readme:no"
+[ -d .mappa ] && echo "mappa-marker:yes" || echo "mappa-marker:no"
 ```
 
 Determine mode:
@@ -112,7 +116,7 @@ source ~/.config/projects-mcp/auth.toml 2>/dev/null || true
 Get-Content ~/.config/projects-mcp/auth.toml | Select-String "base_url|token"
 ```
 
-If auth file missing → stop and tell user: run `/setup-projects-meta` first.
+If auth file missing → stop and tell the user (нужны Gitea-креды; скил `setup-projects-meta` удалён 2026-08-25).
 
 ### Validate project name
 
@@ -178,13 +182,14 @@ If it exists — leave it untouched.
 
 ---
 
-## Step 3 — .wiki/
+## Step 3 — вики (mappa, решение 14/15)
 
-**Delegate to the `setup-wiki` skill.** It handles greenfield creation, canon migration, and the no-op case (already canon) uniformly, with its own confirmation gate. Don't recreate the layout inline here — that's how drift happens.
-
-If `setup-wiki` is not installed on this machine, **stop** and tell the user: project-bootstrap requires `setup-wiki` (and `setup-tasks`) installed. Don't fall back to ad-hoc creation.
-
-**Reference (for context only — `setup-wiki` is the source of truth):** the canonical layout per Karpathy (gist: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) and `using-wiki`:
+**Канал — mappa:** вики проекта = сущности `type=wiki` в сервисе (решения 14/15:
+мета в сервисе). Ничего файлового создавать не нужно; операции — `using-wiki`
+v2 (mappa wiki-тулы). Файловый `.wiki/` — только для проектов вне mappa
+(легаси): layout по Karpathy (gist: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f).
+`setup-wiki` умер (нечего настраивать) — при необходимости создания страниц
+используй `wiki.create` под лизом (см. using-wiki).
 
 ```
 .wiki/
@@ -197,7 +202,7 @@ If `setup-wiki` is not installed on this machine, **stop** and tell the user: pr
   entities/          ← entity pages (people, services, modules) — empty .gitkeep
   concepts/          ← concept / design decision pages — empty .gitkeep
   packages/          ← package pages — empty .gitkeep
-  sources/           ← one summary per ingested source — empty .gitkeep
+  summaries/         ← one summary per ingested source (LLM, raw_path) — empty .gitkeep
 ```
 
 Page-level workflow (ingest, query, lint) and file formats are owned by the
@@ -222,7 +227,7 @@ file overrides the skill where they conflict.
 - `entities/` — discrete things the project tracks (people, services, modules).
 - `concepts/` — recurring ideas, design decisions, gotchas.
 - `packages/` — code packages this project produces or consumes.
-- `sources/` — one summary page per ingested external doc; frontmatter carries `ingested:` and `raw_path:`.
+- `summaries/` — one summary page per ingested external doc; frontmatter carries `ingested:` and `raw_path:`.
 - `overview.md` — single project-wide overview.
 
 ## Naming
@@ -297,7 +302,7 @@ Parseable: `grep "^## \[" .wiki/log.md | tail -20`.
 
 **Immutable.** Read, never edit. The only allowed modification is appending a `> Status:` blockquote when the user explicitly asks for a status audit.
 
-Place raw inputs here — articles, transcripts, PDFs, screenshots — exactly as they came in. The agent reads from `raw/`, writes summaries into `../sources/`, and never modifies raw files.
+Place raw inputs here — articles, transcripts, PDFs, screenshots — exactly as they came in. The agent reads from `raw/`, writes summaries into `../summaries/`, and never modifies raw files.
 
 For large or path-sensitive sources that live outside the repo, register them here:
 
@@ -306,18 +311,19 @@ For large or path-sensitive sources that live outside the repo, register them he
 \`\`\`
 ```
 
-The empty subdirectories (`entities/`, `concepts/`, `packages/`, `sources/`)
+The empty subdirectories (`entities/`, `concepts/`, `packages/`, `summaries/`)
 each get a `.gitkeep` so git tracks them.
 
 ---
 
-## Step 4 — .tasks/
+## Step 4 — таски (mappa, решение 14/15)
 
-**Delegate to the `setup-tasks` skill.** It handles greenfield creation, migration from flat STATUS.md, and the no-op case uniformly, with its own confirmation gate. Don't recreate the layout inline.
-
-If `setup-tasks` is not installed, **stop** and tell the user — same rule as Step 3.
-
-**Reference (for context only — `setup-tasks` is the source of truth):** the canonical layout is `.tasks/STATUS.md` (the board, with emoji status 🔴/🟡/⚪/🟢/🔵) plus `.tasks/<task-slug>.md` per active or paused task. The full pattern is documented in this repo at `.wiki/raw/setup-task-status-wiki.md`.
+**Канал — mappa:** борд проекта = сущности `type=task` в сервисе (решения
+14/15: мета в сервисе). Ничего файлового создавать не нужно; операции —
+`using-tasks` v2 (mappa task-тулы). Файловый `.tasks/` — только для проектов
+вне mappa (легаси: `STATUS.md` + per-task файлы). `setup-tasks` умер
+(нечего настраивать) — таски создаются через `task_create` под лизом
+(см. using-tasks/task-format).
 
 ---
 
@@ -383,22 +389,24 @@ Template contents (`assets/AGENTS.md.template` — source of truth):
 # Agent instructions. Each line is a trigger for an installed skill.
 
 talk like a caveman
-use project wiki
-use task management system
-check across all projects
 pull remote before work
-follow project discipline
 follow tdd-criteria
 delegate to interns when allowed
 recommend, don't menu
 we're on Windows
 ```
 
-The `check across all projects` line activates the `using-projects-meta` skill
-so cross-project task aggregation and the shared `projects-wiki` are available
-without an explicit verbal trigger. The skill is a no-op until the
-`projects-meta-mcp` server is registered — install via `setup-projects-meta`
-on a fresh machine if `mcp__projects-meta__*` tools are missing.
+Mappa-специфичные триггеры (`check across all projects`, `inbox monitor:
+raise on start`, `use project wiki`, `use task management system`, `session
+sync: write to mappa`) **не в шаблоне** — инжектятся через mappa-bootstrap
+(Step 5.7.2), project-bootstrap mappa-agnostic. `check across all projects`
+активирует **mappa** tooling (`mcp__mappa__*`) — cross-project boards, shared
+wiki и реестр проектов живут в mappa.
+
+The file-based `projects-meta-mcp` and its skills (`using-projects-meta`,
+`setup-projects-meta`, `meta-host-routing`, `setup-wiki`,
+`setup-tasks`) were removed 2026-08-25; the shared `projects-wiki` files are
+stubs «не читать, не править» — канон mappa shared-scope.
 
 The `pull remote before work` line activates the `pulling-before-work` skill,
 which runs one `git pull --ff-only` at session start (and on explicit re-sync
@@ -408,15 +416,6 @@ upstream — never auto-merges, stashes, or pushes. Install the skill on the hos
 if `pulling-before-work` is not in `~/.claude/skills/`; otherwise the trigger is
 silently dead like any other absent skill.
 
-The `follow project discipline` line activates the `project-discipline` skill,
-which codifies four cross-project rules: (1) project AGENTS.md / CLAUDE.md /
-.wiki/CLAUDE.md / .tasks/ override defaults from any other skill; (2) all work on master/main,
-no feature branches without explicit user approval; (3) version bump on every
-edit of versioned artifacts per semver, recorded in commit; (4) commit freely,
-push only after explicit per-session approval. Install the skill on the host
-if `project-discipline` is not in `~/.claude/skills/`; otherwise the trigger is
-silently dead like any other absent skill.
-
 The `follow tdd-criteria` line activates the `tdd-criteria` skill, which enforces
 test-driven development by default with four bright-line carve-outs (visual CSS,
 spike exploration, oneshot scripts, pure wrappers) and four anti-loophole rules
@@ -430,8 +429,8 @@ which lets Claude offload predictable bulk I/O and summarization tasks
 (reading 3+ files, distilling long transcripts) to cheap intern LLMs via the
 local `interns` MCP server (`mcp__interns__bulk_text_read`,
 `mcp__interns__transcript_distill`, etc.) — saves Anthropic quota at ~125× the
-per-call cost reduction on bulk reads. Per-session permission grant mirrors
-`project-discipline` Rule 4: ask-mode default, conversational grant / revoke,
+per-call cost reduction on bulk reads. Per-session permission grant mirrors the
+`mappa-kzntsv-project-discipline` Rule 4 (skill moved from `victor/mappa-vitya-skills`, легаси, поглощено монорепо): ask-mode default, conversational grant / revoke,
 always-ask paths for `.env` / secrets / keys / SSH credentials even with an
 active grant, session-end reset. The skill is a no-op until the `interns` MCP
 server is registered — install via `setup-interns` on a fresh machine if
@@ -474,11 +473,14 @@ Skills used to initialize this project's `.wiki/` and `.tasks/` layout, with the
 | Skill | Version | Role |
 |---|---|---|
 | `project-bootstrap` | <version> | orchestrator |
-| `setup-wiki` | <version> | wiki canonical layout |
-| `setup-tasks` | <version> | tasks canonical layout |
-| `project-discipline` | <version> | cross-project policy |
 | `setup-interns` | <version> | interns MCP server install (one-time, per machine) |
 | `using-interns` | <version> | interns runtime policy + per-session permission grant |
+| `mappa-*` (методика, модуль 5.7) | <version of reference-package skills> | mappa-циклы: session-orient / task-work / knowledge / messaging / delegation / brainstorm-promote / closing-ritual |
+
+Модуль `mappa-bootstrap-project` (решение 4 mappa-as-product) фиксирует
+версию методики в этой строке — читать `version:` из frontmatter каждого
+mappa-скилла, не хардкодить. Если пакет не установлен — `unknown` (видно
+в депс-чеке 5.6).
 
 This file is overwritten if `project-bootstrap` is re-run on the same project. For history, use `git log .wiki/concepts/bootstrap-manifest.md`.
 ```
@@ -507,13 +509,16 @@ Mismatch between template and map → silent gaps in the recommendation.
 | `talk like a caveman` | `caveman` | skill | `~/.claude/skills/caveman/SKILL.md` | `bash scripts/install.sh caveman` |
 | `use project wiki` | `using-wiki` | skill | `~/.claude/skills/using-wiki/SKILL.md` | `bash scripts/install.sh using-wiki` |
 | `use task management system` | `using-tasks` | skill | `~/.claude/skills/using-tasks/SKILL.md` | `bash scripts/install.sh using-tasks` |
-| `check across all projects` | `using-projects-meta` | skill | `~/.claude/skills/using-projects-meta/SKILL.md` | `bash scripts/install.sh using-projects-meta` |
+| `check across all projects` | mappa (`mcp__mappa__*`) | MCP | `mcpServers.mappa` in `~/.claude.json` | — |
 | `pull remote before work` | `pulling-before-work` | skill | `~/.claude/skills/pulling-before-work/SKILL.md` | `bash scripts/install.sh pulling-before-work` |
 | `session handoff: read on start, write on end` | `session-handoff` | skill | `~/.claude/skills/session-handoff/SKILL.md` | `bash scripts/install.sh session-handoff` |
-| `follow project discipline` | `project-discipline` | skill | `~/.claude/skills/project-discipline/SKILL.md` | `bash scripts/install.sh project-discipline` |
 | `follow tdd-criteria` | `tdd-criteria` | skill | `~/.claude/skills/tdd-criteria/SKILL.md` | `bash scripts/install.sh tdd-criteria` |
 | `delegate to interns when allowed` | `using-interns` | skill | `~/.claude/skills/using-interns/SKILL.md` | `bash scripts/install.sh using-interns` |
 | `recommend, don't menu` | `recommend-dont-menu` | skill | `~/.claude/skills/recommend-dont-menu/SKILL.md` | `bash scripts/install.sh recommend-dont-menu` |
+| `use project wiki` | `mappa-knowledge` | skill | см. mappa-bootstrap (репо mappa) | `cd <mappa-repo> && bash skills/mappa-bootstrap/assets/install.sh` |
+| `use task management system` | `mappa-task-work` | skill | см. mappa-bootstrap (репо mappa) | `cd <mappa-repo> && bash skills/mappa-bootstrap/assets/install.sh` |
+| `inbox monitor: raise on start` | `mappa-session-orient` | skill | см. mappa-bootstrap (репо mappa) | `cd <mappa-repo> && bash skills/mappa-bootstrap/assets/install.sh` |
+| `session sync: write to mappa` | `mappa-session-orient` | skill | см. mappa-bootstrap (репо mappa) | `cd <mappa-repo> && bash skills/mappa-bootstrap/assets/install.sh` |
 | `we're on Windows` / `we're on Linux` / `we're on macOS` | `active-platform` | skill | `~/.claude/skills/active-platform/SKILL.md` | `bash scripts/install.sh active-platform` |
 
 ### Algorithm
@@ -527,7 +532,11 @@ Mismatch between template and map → silent gaps in the recommendation.
    match any row are user-custom — skip silently. The platform line matches
    the `active-platform` row regardless of which platform is pinned.
 3. For each matched canonical line, check the detection path:
-   - `kind: skill` → does `~/.claude/skills/<name>/SKILL.md` exist?
+   - `kind: skill` → does `~/.claude/skills/<name>/SKILL.md` **or**
+     `~/.agents/skills/<name>/SKILL.md` exist? (Skill installs can land in
+     either host path — `scripts/install.sh` writes `~/.claude/skills/`, a
+     manual/alternate install may use `~/.agents/skills/`; a skill present in
+     either path fulfills the trigger. Same two-path rule as Step 5.7.3.)
    - `kind: plugin` → does `~/.claude/plugins/installed_plugins.json` contain
      the plugin key under `plugins`? (Treat malformed JSON as "missing" and
      continue — don't crash the bootstrap over a detection edge case.)
@@ -572,12 +581,160 @@ Mismatch between template and map → silent gaps in the recommendation.
   `setup-X` at first use; bootstrap doesn't duplicate that detection.
 - The `~/.claude/skills/` and `~/.claude/plugins/` paths resolve identically
   on Windows / Linux / macOS — `~` works under git-bash too.
+- **Detection paths (unified with Step 5.7.3):** a `kind: skill` fulfiller is
+  considered present if its `SKILL.md` exists in `~/.claude/skills/<name>/`
+  OR `~/.agents/skills/<name>/`. The dependency tables below list the
+  canonical install path (`~/.claude/skills/`, what `scripts/install.sh`
+  writes); detection itself accepts both.
 - **Hard rule — never auto-install.** Slash commands aren't callable from a
   skill, and silently mutating user-level skill / plugin state without
   consent is overreach. The recommendation is informational. The user can
   install some / all / none of the recommendations, or remove canonical
   lines from `AGENTS.md` to lean the project's trigger set down.
 
+---
+
+## Step 5.7 — mappa-bootstrap-project (модуль, решение 4 mappa-as-product)
+
+> Спека: `.wiki/concepts/mappa-as-product.md` (wiki:2672), решение 4. Модуль
+> вызывается project-bootstrap'ом как шаг в режимах greenfield-full и upgrade.
+> Скоуп: connect (MCP) + mappa-конвенции в AGENTS.md (idempotent merge) +
+> методика-install (пакет из репо, версия в манифест) + manifest/deps-check.
+
+### 5.7.1 — Connect (MCP)
+
+Проверить, что mappa MCP-сервер зарегистрирован на этой машине. Канон —
+`~/.claude.json` → `mcpServers.mappa` (stdio: `node <repo>/dist/src/mcp-entry.js`,
+env `MAPPA_CORE_URL` + `MAPPA_API_TOKEN`). pi-рантайм читает ту же
+регистрацию через MCP-адаптер.
+
+```bash
+# POSIX / Windows (git-bash):
+python -c "import json; d=json.load(open('$HOME/.claude.json')); print('mappa' in d.get('mcpServers', {}))"
+```
+
+- **Зарегистрирован** → пропустить, идти к 5.7.2.
+- **Не зарегистрирован** → печать одного информационного блока (НЕ
+  авто-инсталл, то же правило что 5.6):
+
+  ```
+  ℹ️  mappa MCP не зарегистрирован (~/.claude.json mcpServers.mappa отсутствует).
+      Установка: собери репо mappa (npm run build) и добавь в mcpServers:
+      { "type": "stdio", "command": "node",
+        "args": ["<mappa-repo>/dist/src/mcp-entry.js"],
+        "env": { "MAPPA_CORE_URL": "...", "MAPPA_API_TOKEN": "..." } }
+      Секреты — из pass (см. secret:<path> реф-стиль, wiki:2672 решение 11).
+  ```
+
+  mappa-конвенции в AGENTS.md (5.7.2) можно добавлять и без MCP-регистрации
+  — триггеры будут ждать установки сервера (как любой absent-скилл).
+
+### 5.7.2 — mappa-конвенции в AGENTS.md (инъекция через mappa-bootstrap)
+
+`project-bootstrap` — mappa-agnostic: mappa-триггеры **не хардкодятся** в
+шаблоне (см. `assets/AGENTS.md.template`). Инъекция канонического набора
+mappa-триггеров (`inbox monitor: raise on start`, `session sync: write to
+mappa`, `use project wiki`, `use task management system`, `check across all
+projects`) — через скил `mappa-bootstrap` (репо mappa, единый источник):
+
+```bash
+bash <mappa>/skills-core/mappa-bootstrap/assets/install.sh --triggers <project-dir>
+```
+
+После инъекции — **верифицировать** наличие строк (substring-проверка, та же
+машинерия что Step 5 upgrade-merge). Если пользователь сознательно убрал
+mappa-триггеры из AGENTS.md — не возвращать (уважать выбор). Источник истины
+набора — mappa-bootstrap, НЕ шаблон project-bootstrap.
+
+### 5.7.3 — методика-install (пакет из репо mappa, версия в манифест)
+
+Методика = reference-пакет (wiki:2672 решение 3/6): mappa-скилы живут в
+**репо mappa** (`mappa/skills/`, релокация task:1323, коммит 5301e85) — НЕ
+в репо skills. project-bootstrap НЕ хранит тела и НЕ дублирует пути
+(мёртвый маппинг на `scripts/install.sh mappa-*` убран, task:1339):
+установка/триггеры/deps-check mappa-скилов делегируются скилу
+`mappa-bootstrap` (репо mappa, спека wiki:3265).
+
+1. Определить список mappa-циклов: `mappa-session-orient`,
+   `mappa-task-work`, `mappa-knowledge`, `mappa-messaging`,
+   `mappa-delegation`, `mappa-brainstorm-promote`, `mappa-closing-ritual`
+   (плюс остальные из `mappa/skills/`).
+2. Проверить установку по правилу детекта Step 5.6 (оба пути:
+   `~/.claude/skills/` и `~/.agents/skills/`)? → да: пропустить
+   (upgrade-императив не дублировать).
+3. Нет → печать информационного блока (НЕ авто-инсталл, правило 5.6):
+
+  ```
+  ℹ️  Методика mappa не установлена. Установка (скил mappa-bootstrap,
+      репо mappa, НЕ skills-репо):
+      cd <mappa-repo> && bash skills/mappa-bootstrap/assets/install.sh
+  ```
+
+4. Версия методики фиксируется в bootstrap-manifest (5.7.4): читать
+   `SKILL.md` frontmatter каждого mappa-скилла (`version:`), не хардкодить.
+
+### 5.7.4 — manifest/deps-check
+
+Манифест (Step 5.5) дополняется строкой методики — версия = версия
+reference-пакета (репо mappa, `version` из frontmatter скиллов; пакетная
+версия — `mappa-bootstrap` из `mappa/skills/mappa-bootstrap/SKILL.md`).
+Добавить в таблицу манифеста:
+
+| Skill | Version | Role |
+|---|---|---|
+| `mappa-bootstrap-project` (модуль) | <project-bootstrap version> | connect + конвенции + методика-install |
+| `mappa-bootstrap` (скил, репо mappa) | <mappa-bootstrap version> | установка/триггеры/deps-check mappa-скилов |
+
+Deps-check (Step 5.6): mappa-триггеры (`inbox monitor: raise on start`,
+`use project wiki`, `use task management system`) маппятся на fulfiller'ы
+через скил `mappa-bootstrap` — `bash <mappa>/skills/mappa-bootstrap/assets/install.sh --check`
+(источник истины — `mappa/skills/`, НЕ репо skills; мёртвые пути
+`~/.claude/skills/mappa-*/SKILL.md` из таблицы убраны, task:1339).
+Недостающие mappa-скиллы → в блок рекомендаций 5.6 (тем же форматом,
+install-команда — скил mappa-bootstrap, см. 5.7.3).
+
+---
+
+## Step 5.8 — `.mappa` маркер (контракт wiki:3340)
+
+Машиночитаемый маркер проекта в корне папки (схема v1 — `.mappa/config.yaml`):
+гейт mappa-скилов («без маркера папка не участвует в mappa-операциях»,
+task:1546) + признак корня проекта для харнессов. Создаётся на bootstrap —
+без ручного прогона генератора (task:1583). Детерминированный рендер:
+фиксированный порядок полей, без секретов, без timestamp — повторный запуск
+no-op (`keep`).
+
+1. **Собрать значения** (реестр mappa → локальное знание):
+   - `project` — канон папки (`basename "$PWD"`); если проект уже в реестре
+     (`projects_resolve`) — сверить, не расходится ли;
+   - `tenant` — `MAPPA_TENANT` (по умолчанию `vitya`);
+   - `url` — `MAPPA_CORE_URL` (без trailing slash);
+   - `git_provider` — из реестра `projects.git_provider` (например `gitea`),
+     иначе из шага 1.5 (создано через Gitea API → gitea); опционально;
+   - `git` — `projects.qualified` (owner/repo) из реестра, иначе из remote
+     шага 1.5; опционально (опустить, если неизвестно).
+2. **Записать маркер** (скрипт — ассет этого скила, реализует контракт
+   wiki:3340; в репо: `skills/project-bootstrap/assets/dot_mappa_marker.py`):
+
+   ```bash
+   python assets/dot_mappa_marker.py write \
+     --project "$(basename "$PWD")" --tenant vitya --url "$MAPPA_CORE_URL" \
+     --git-provider gitea --git "$OWNER/$REPO"
+   ```
+
+   Без `--git-provider`/`--git`, если поля неизвестны. Повторный прогон —
+   no-op (`keep`); отличающийся существующий маркер без `--force` НЕ
+   перезаписывается — покажи diff и спроси (правило «never overwrite»).
+3. **Верифицировать**: `python assets/dot_mappa_marker.py check` → exit 0.
+4. **Контракт-тест** (TDD, task:1583): `python assets/test_dot_mappa_marker.py`
+   — «после bootstrap есть `.mappa/config.yaml`», детерминизм, без секретов,
+   порядок полей, идемпотентность.
+
+Маркер публичен (без секретов) и попадает в коммит шага 6. Валидный
+существующий маркер не трогаем.
+
+---
+
 ## Step 6 — Commit
 
 ```bash
@@ -602,11 +759,13 @@ Print a final report:
 ✅ Done! Created:
   .wiki/          — project wiki (Karpathy method)
   .tasks/         — task tracking system
+  .mappa/         — mappa project marker (wiki:3340, schema v1)
   AGENTS.md     — skill triggers (canon)
   CLAUDE.md     — legacy pointer
   .gitignore      — standard template
   README.md       — starter file
   remote          — Gitea repo created and pushed
+  mappa           — mappa-bootstrap-project: connect + конвенции + методика (модуль 5.7)
 
 Skipped (already existed):
   git             — left untouched
@@ -622,10 +781,10 @@ Remote: <Gitea URL>
 
 ---
 
-## Step 8 — projects-meta sync (greenfield-full mode)
+## Step 8 — mappa registry (greenfield-full mode)
 
-Only in **greenfield-full** mode. Re-sync the projects-meta cache so the new
-project becomes visible to `mcp__projects-meta__*` tools.
+Only in **greenfield-full** mode. Register the new project in mappa
+(`mcp__mappa__projects_register`) so it becomes visible in the registry.
 
 ```bash
 # POSIX:
@@ -650,6 +809,30 @@ If the sync script doesn't exist → skip with informational message:
     Run /setup-projects-meta to install it. The new repo is already created in Gitea.
 ```
 
+## Step 9 — Address book registration
+
+Register the new project in the inter-session address book so other agents can
+write letters to it (`inter-session-messaging` skill).
+
+The address book lives in the shared wiki clone:
+`~/projects/.wiki/concepts/projects-address-book.md` — a markdown table with
+columns `адрес (папка) | qualified | роль`. The **address is the folder name as
+is**; the qualified name comes from the remote just created.
+
+1. Read the current table from `~/projects/.wiki/concepts/projects-address-book.md`.
+2. Append a row:
+   ```
+   | <folder-name> | <owner>/<repo> | <role> |
+   ```
+   `<folder-name>` is the local folder name as-is (e.g. `.common`, `books`);
+   `<owner>/<repo>` is the qualified Gitea name from the remote; `<role>` —
+   short description (boss-zone, ops, infra, app, …).
+3. Do **not** overwrite existing rows — append only, keep the table sorted.
+4. Commit + push the shared wiki repo (`~/projects/.wiki`).
+
+If the file doesn't exist yet (book not bootstrapped) → create it with the
+canonical header and this project as the first row, then push.
+
 ---
 
 ## Rules