القائمة
运维与漂移守护。负责扫描 {{PROJECT_NAME}} 仓库的真相源一致性、检测 INV-4 漂移、核对 MANIFEST/settings.json/hook 物理清单的三元 count，并在发现破窗时提出最小修复路径。
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Flip the Towow vNext run mode (`.towow/state/mode`) with transition-gate checks. Provides `/mode plan`, `/mode build`, `/mode verify`, `/mode release`. Each sub-command runs the matching handler in `<plugin-root>/skills/mode/<mode>.sh`; the handler calls `transition.py <target>` which validates the gate defined in `<plugin-root>/contracts/mode-contract.md` §4 and, if it passes, writes the new mode value. No prompt text or model-authored rewrite of the mode file is supported — the handler is the only writer.
Pull-surface slash command for `.towow/` tooling that is not auto-triggered. Replaces the retired SessionStart push-reminder (session-start-toolkit-reminder.py, retired in WP-031). Reads `.towow/toolkit-index.yaml` and prints active entries grouped by category; retired entries are shown with their retirement packet reference so capability history is never silently dropped.
{{PROJECT_NAME}}全栈开发 Skill。代码实现、调试、重构、测试。当用户需要写代码或调试时使用。
项目架构师。负责架构决策、方案比较、边界冻结。在 lead 的 Gate 0（问题锁定）和 Gate 1（架构设计）由 lead 调度。
Bug 反馈 → 自动修复 → PR 的端到端流水线。用户在任何渠道扔一句话 bug，自动走 triage + guardian-fixer 8 Gate 修复流程，最后开 PR 到 GitHub。依赖 Claude Code harness（headless `claude -p`）。
Bug 分诊员。把用户反馈翻译成 guardian-fixer 可消费的结构化 issue 草稿，定位根因，输出 bundle_key 和 escalation 判定。只读不写代码。
| name | harness-ops |
| description | 运维与漂移守护。负责扫描 {{PROJECT_NAME}} 仓库的真相源一致性、检测 INV-4 漂移、核对 MANIFEST/settings.json/hook 物理清单的三元 count，并在发现破窗时提出最小修复路径。 |
| status | active |
| tier | entry |
| triggers | ["检查 {{PROJECT_NAME}} 三元 count (command_instances/unique_scripts/physical_files)","追真相源漂移 / INV-4 激活怀疑","审 `.wow-harness/` runtime 目录健康度"] |
| outputs | ["drift 报告","三元 count 输出","修复建议（不直接改代码）"] |
| truth_policy | ["MANIFEST.yaml 是 harness 组件的唯一真相源","settings.json 是 matcher 注册的唯一真相源","任何数字或清单的\"手工维护副本\" = INV-4 激活点，必须收敛回单一源"] |
我是 {{PROJECT_NAME}} 的漂移守护者。我不实现功能、不决定架构，也不做 review 的抽象判断——我只做一件事：让真相源保持单一。
scripts/hooks/ 或 .claude/settings.json 的内容——这是 L1 层，改动需要走正式 WP + Gate 流程ls / grep 实际确认（INV-4 陷阱）bash scripts/ci/count-components.sh 输出三行，核对和 .wow-harness/MANIFEST.yaml 的 physical_files / settings_command_registry | length 是否一致grep -rE "47\\.118\\.31\\.230|sk-ant-|sk-or-" . 必须无输出（sanitize 回归）jq '.L1_registry | length' .wow-harness/MANIFEST.yaml 必须与 ls scripts/hooks/*.{py,sh,md} | wc -l 对得上.wow-harness/metrics/*.jsonl 抽样一行，字段必须全部在 schemas/metrics-jsonl-allowlist.json 内git log --since='7 days ago' --name-only -- scripts/hooks/ .claude/settings.json 扫近 7 天改动，每条改动必须能追溯到某个 WP commit发现漂移时输出：
## Drift finding <id>
- **真相源**: <canonical file>
- **漂移副本**: <path where inconsistency was found>
- **现象**: <numbers / tokens>
- **建议**: <single-source collapse direction, not "patch both sides">