peer-synclisted

# peer-sync ## Purpose When the lead starts a new session and `yakos peer status` shows other peer sessions active, this skill produces a concise summary of what the peers have been doing — recent decisions, active claims, in-flight mode proposals — so the lead doesn't dispatch into a peer's in-progress work. ## Scope - Reads `/var/lib/yakos/<project>/coord/activity.ndjson` (tail) - Reads `/var/lib/yakos/<project>/coord/active-claims.json` (projection) - Reads each peer session's `coord/sessions/<user>@<host>-<pid>.ndjson` (last ~5 events per session) - Output is a single context-block summary, < 500 tokens Does NOT: - Modify any coord state - Send peer messages - Make dispatch decisions (that's the lead's job after reading this) ## Automated pass Lead invokes via `bash`: ```bash yakos peer status yakos peer log --since "$(date -u -j -v '-10M' +%Y-%m-%dT%H:%M:%SZ 2>/dev/null \ || date -u -d '-10 minutes' +%Y-%m-%dT%H:%M:%SZ)" yakos peer claims ``` The three outputs together form the peer-context picture. This skill exists to *synthesize* them into a lead-friendly summary, not to gather them — the gathering is already CLI-supported. Synthesis format (skill output): ``` Peer context (last 10 min): - N peer session(s) active: <user1>@<host>, <user2>@<host> - Recent decisions: - alice (frontend-pro): refactored src/auth/login.ts to use OAuth fallback - bob (backend-pro): added /v1/users endpoint - Active claims (M peers holding K files): - alice holds src/a