sync

Sync

SYNC writes this conversation's own view of one ring to disk. First call on a ring with no file promotes it (inline → resumed); every later call checkpoints it. Format reference (cite by path, don't reopen it here): ${CLAUDE_PLUGIN_ROOT}/references/ring-file.md.

Common rules (all ring skills)

Disk commands go through absolute paths and /usr/bin/find, /usr/bin/grep, or python3 ${CLAUDE_PLUGIN_ROOT}/scripts/ring.py (every ring.py below means this) — bare find/grep are shimmed and fail silently. No git verb of any kind. No .bak files. A question to the human is posed in plain text, once, with A/B/C choices — never an interactive question tool.

Arguments

Steps

1. Resolve slug and dir per the tables above.
2. Locate the file: glob ring-<slug>-llm.md at the root of <dir>; if absent there, glob <dir>/done/. Found in done/ → refuse (table below) — a parked/done ring is not sync's business, /open --resume reactivates it first. Promotion is only the case where the slug is absent from both locations.
3. Refuse before writing — table below.
4. This conversation's write token: reuse whatever token this conversation already holds — from an earlier /open --resume, an earlier /ring:sync call, or a promotion triggered by /open — and mint one only if it holds none yet. Format and precedence: ${CLAUDE_PLUGIN_ROOT}/references/ring-file.md §2, carrier row — cited, not restated here.
5. Compose and write — table below.
6. python3 ${CLAUDE_PLUGIN_ROOT}/scripts/ring.py scan <dir>. An anomaly on this ring is reported in the output, never repaired silently.
7. Output — one sentence.