From 8b68613b0879fdd479b60969b85242eb29d44a80 Mon Sep 17 00:00:00 2001
From: vitya <vitya.kuznetsov@gmail.com>
Date: Thu, 21 May 2026 09:19:56 +0300
Subject: [PATCH] =?UTF-8?q?meta(tasks):=20re-close=20using-vds-ops-review?=
 =?UTF-8?q?=20=E2=9C=85=20via=20fresh-eyes=20subagent=20+=202=20=E2=9A=AA?=
 =?UTF-8?q?=20informational=20follow-ups?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Prior close-note 2026-05-21 was done by the implementation agent → violated
spec rule «Кто делает: не имплементер». Re-opened, dispatched general-purpose
subagent (clean context, no impl-priming), verdict ✅ PASS on all 5 acceptance
dimensions (activation / false-positive / ambiguity / hermes mapping / drift).

2 informational notes выявлены вне 5 dimensions и filed как ⚪ ready siblings:
- using-vds-ops-description-length-investigate — description 1473 chars vs
  MEMORY-recorded ≤900 hard limit; empirically works → drift investigation
- using-synology-ops-disambiguation-uplift — NAS skill lacks explicit
  `traefik` disambiguation clause that VDS skill has → sibling parity

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 .tasks/STATUS.md | 61 ++++++++++++++++++++++++++++++++++++++++++------
 1 file changed, 54 insertions(+), 7 deletions(-)

diff --git a/.tasks/STATUS.md b/.tasks/STATUS.md
index 366ac5a..57c17f2 100644
--- a/.tasks/STATUS.md
+++ b/.tasks/STATUS.md
@@ -1,5 +1,5 @@
 # Task Board
-_Updated: 2026-05-20 (using-yt-tools — 2 findings closed 🟢: skill-body-venv-invocation v0.2.2→0.2.3, windows-powershell-path-doc-fix v0.1.5→0.1.6. Both concurrent-session gaps resolved.)_
+_Updated: 2026-05-21 (using-vds-ops-review re-closed 🟢 via fresh-eyes subagent — 0 findings on 5 dimensions, 2 informational notes filed as ⚪ siblings: description-length-investigate + synology-ops-disambiguation-uplift.)_
 
 <!--
   Canonical layout. One block per task. Per-task deep context lives in
@@ -1198,14 +1198,61 @@ Findings — отдельные follow-up tasks (`using-vds-ops-<gap>-fix` ил
 **NB:** body-секции пустые by design. Ревью НЕ требует их заполнения. Body fill-in — отдельная таска / отдельный последующий проход «доведём using-vds-ops» (см. workshop-promote-brainstorm spec §6 «Проход второй»).
 
 **Status:** done
-**Where I stopped:** Закрыто 2026-05-21. Все blockers 🟢: install ✅, hermes-mapping ✅, test-trigger ✅ (7/7 behavioral tests PASSED, no findings). Ревью пройдено:
-- Activation: все VDS-фразы активируют скилл ✅
-- False-positive: negative тесты корректны ✅
-- Ambiguity: traefik disambiguation работает ✅
-- Hermes-mapping: mode=pending прописан ✅
-- Description sanity: нет drift'а ✅
+**Where I stopped:** Re-closed 2026-05-21 fresh-eyes pass via general-purpose subagent (clean context, no impl-priming). Verdict: ✅ PASS — no findings on 5 acceptance dimensions:
+- (1) Activation coverage ✅ — RU+EN triggers cover 3 positive smoke phrases
+- (2) False-positive ✅ — explicit "Skip for ..." carve-out (NAS modulair-* / write-ops / no-incident)
+- (3) Ambiguity ✅ — explicit `traefik` disambiguation clause (stronger than NAS sibling)
+- (4) Hermes mapping ✅ — `mode: pending`, intended mirrors `using-synology-ops`
+- (5) Description ↔ mapping drift ✅ — no drift
+
+2 informational notes вне 5 dimensions (filed as ⚪ siblings, не блокеры):
+- description length 1473 chars vs ≤900 char limit recorded in MEMORY — empirically works, requires investigation → `using-vds-ops-description-length-investigate`
+- sibling `using-synology-ops` lacks explicit disambiguation clause (VDS skill stronger here) → `using-synology-ops-disambiguation-uplift`
+
 **Next action:** (none — kept until merged)
 **Branch:** master
 <!-- closed-by: vitya@DESKTOP-NSEF0UK / 2026-05-21 / all blockers ✅, 7/7 tests PASSED, no findings, review complete -->
+<!-- reopened-by: vitya@DESKTOP-NSEF0UK / 2026-05-21 / reason: closing agent == impl agent, violates non-implementer rule; need fresh-eyes subagent pass -->
+<!-- closed-by: vitya@DESKTOP-NSEF0UK / 2026-05-21 / fresh-eyes subagent (general-purpose) PASS on all 5 dimensions, 0 blockers, 0 minor findings, 2 informational notes filed as ⚪ siblings -->
+
+---
+
+## ⚪ [using-vds-ops-description-length-investigate] — Investigate description length vs MEMORY ≤900 char limit. Drift between memory feedback и реальным harness behavior?
+
+**Observed (2026-05-21, fresh-eyes review of using-vds-ops):** description field в `skills/using-vds-ops/SKILL.md` = **1473 chars**. MEMORY entry `feedback_skill_description_length_limit.md` декларирует «hard limit ~1024 chars; превышение → harness тихо отбрасывает description и подставляет H1; держать ≤900 chars». При этом 7/7 behavioral smoke-test PASSED, и hermes/mapping.yaml корректно обрабатывает скил с этим description — empirically работает.
+
+**Гипотезы:**
+- (a) Harness limit увеличился / снят — memory note устарел. Проверить current behavior в `available-skills` listing: full description vs H1-fallback.
+- (b) Limit зависит от downstream consumer (Claude vs Gemini vs Copilot). VDS skill пока тестировался только на CC — может Gemini его дропнет.
+- (c) MEMORY note был paranoid — реальный limit выше, но best-practice держать ≤900 всё равно (compression discipline).
+
+**Acceptance:**
+- Замер реального текущего harness limit (написать тестовый skill с известной длиной description, инкрементировать, смотреть когда listing fallback'нет).
+- Обновить или удалить MEMORY entry `feedback_skill_description_length_limit.md` в зависимости от результата.
+- Если limit реально низкий — открыть `using-vds-ops-description-compress` follow-up (compress 1473 → ≤900 без потери triggers).
+
+**Status:** ready
+**Where I stopped:** (not started)
+**Next action:** написать пустой skill `skills/.test-description-length/SKILL.md` с description progressively dlinning, прогонять `/reload-plugins`, смотреть харнес listing. Document findings → update memory.
+**Branch:** (not started)
+<!-- created-by: vitya@DESKTOP-NSEF0UK / 2026-05-21 / origin: [using-vds-ops-review] fresh-eyes subagent informational note #1 -->
+
+---
+
+## ⚪ [using-synology-ops-disambiguation-uplift] — Add explicit disambiguation clause to `using-synology-ops` description (sibling parity with `using-vds-ops`).
+
+**Observed (2026-05-21, fresh-eyes review of using-vds-ops):** VDS skill description содержит explicit clause `Disambiguation: traefik exists on both VDS and NAS — ask «на VDS или на NAS?» before tool call when ambiguous.` NAS skill (`using-synology-ops`) такого clause не имеет, хотя проблема симметричная — `traefik` есть на обоих хостах.
+
+**Acceptance:**
+- `skills/using-synology-ops/SKILL.md` description обновлён: добавить mirror-clause «Disambiguation: `traefik` exists on both NAS and VDS — ask "на NAS или на VDS?" before tool call when ambiguous.»
+- bump version (PATCH — wording / clarity без поведенческого изменения).
+- `scripts/install.ps1 -Names using-synology-ops` пройден.
+- Behavioral smoke-test на двух новых сессиях: «traefik unhealthy» в чистой сессии должна вызвать disambiguation, не silent activation одного скила.
+
+**Status:** ready
+**Where I stopped:** (not started)
+**Next action:** edit SKILL.md description + version bump + reinstall + smoke. Заодно посмотреть нет ли других shared names (`portainer`? `postgres` — где он живёт?).
+**Branch:** (not started)
+<!-- created-by: vitya@DESKTOP-NSEF0UK / 2026-05-21 / origin: [using-vds-ops-review] fresh-eyes subagent informational note #2 -->
 
 ---