convergence-monitoring

> **Platform Note:** State files use the platform's native directory: `.claude/` (Claude Code), > `.codex/` (Codex CLI), or `.cursor/` (Cursor IDE). Shared metrics live in > `.orchestrator/metrics/`. See `skills/_shared/platform-tools.md`. # Convergence-Monitoring Skill ## Platform-native (CC 2.1.105+) This skill's watcher is registered as a plugin monitor via `.claude-plugin/plugin.json`'s `experimental.monitors` reference to `monitors/monitors.json`. Each session that loads this plugin auto-starts the watcher in the background (see `scripts/lib/convergence-monitor.mjs`). Each NDJSON stdout line from the watcher becomes a `<task_notification>` event Claude sees mid-session. For harness < 2.1.105 (no monitor support), the skill's manual probes documented below serve as the fallback path. ## When to Invoke **Explicit invocation (`/convergence-monitoring`):** Standalone assessment — reads wave history from `.orchestrator/metrics/events.jsonl`, computes all three signals, reports verdict + recovery options. **Embedded (loop context):** `/autoresearch` and `wave-executor` invoke this skill after each Impl-Core or Impl-Polish wave when `convergence-monitoring: true` is set in Session Config. The skill returns a structured verdict that the caller uses to gate the next wave. **NOT a substitute for quality gates.** Quality-gates verify correctness (typecheck, test, lint). Convergence-monitoring verifies *progress direction* — whether the work is moving toward done or oscillat...