peer-handofflisted

# peer-handoff ## Purpose In multi-dev co-pilot mode, two developers share a project across parallel sessions. yakOS already has `peer status`, `peer log`, `peer claims`, `peer propose-mode` for coordination — but no documented "I'm done, you continue from here" handoff protocol. This skill defines the handoff. Sender signals completion + context; receiver runs `peer-sync` to catch up + acknowledges. ## Scope - Applies only when `yakos peer status` shows at least one other active peer session - Uses the existing coord activity stream (`/var/lib/yakos/<project>/coord/activity.ndjson`) - Does NOT replace mode negotiation — propose-mode/respond-mode is for "should we work in parallel"; handoff is for "I'm done, your turn" ## Automated pass ### Sender (the dev finishing their slice) Lead invokes via `bash`: ```bash yakos peer handoff \ --to alice@dev01 \ --completed-scope 'src/auth/login.ts, src/auth/oauth.ts' \ --notes 'OAuth flow works; loginWithPassword still has the email-case bug from the original ticket' \ --next-action 'finish the email-case fix; tests are in tests/auth_test.go' ``` This emits a `peer_handoff` event to the coord activity stream with the structured fields above. The lead also: 1. Updates `work/current/decisions.md` with a 2-3 line summary citing the handoff (operator-visible record; coord stream is shared but decisions.md is the local audit) 2. Releases any held claims on the completed scope: `yakos peer release s