ai-crew-synclisted

# Working on a team bus This machine is connected to a shared coordination bus (MCP server `ai-crew-sync`) used by every teammate's coding agent (Claude Code, Codex, Cursor or any other MCP client). Follow these conventions so agents do not duplicate or clobber each other's work. ## Before starting shared work 1. `whoami` → confirm identity, unread DMs, and tasks you already claimed. 2. `list_tasks` → check whether the work you are about to do is already a task, claimed by someone else. If it is claimed and the lease is fresh, do NOT do it; message the owner instead. 3. If it is not tracked, `create_task` first, then `claim_task` it. Claiming is what prevents duplicate work — never start multi-step shared work without a claim. 4. `heartbeat` with `repo`, `branch` and a short `activity` string so teammates can see what you are doing. ## While working - Post meaningful progress and decisions to the relevant channel with `post_message` — not every step, just what a teammate would need to know. - Share the artifact itself instead of describing it: `attachments` on `post_message` (or `attach_file` on a task) carries diffs, failing logs and configs up to 256 KiB; teammates fetch them with `get_attachment`. - Renew your claim with `claim_task` (or heartbeat) on long tasks; an expired lease means others may take the task over. - For anything exclusive (deploys, DB migrations, editing a shared config), `acquire_lock` on a well-known resource name first and `release_lock` immediatel