notifying-main-agentlisted

## Overview Discuss work details and authorization directly with the user; the main agent accepts those decisions. Ask it only for integrated context or a coordinator-owned action result. Address every operation by your instruction path. Live bodies carry one delta in at most two sentences. Put detailed context or evidence in repeatable `--ref`; transport adds identity, intent, and correlation. ## Ask the main agent ```bash uv run --script "${CLAUDE_PLUGIN_ROOT}/scripts/send-dispatch-message.py" \ --instruction-path <your exact instruction path> \ --to main --intent question \ --message "<one integration question; include expected reply shape>" \ --ref "<source or artifact when needed>" ``` Continue independent work. If the coordinator's answer becomes blocking, report `awaiting-main-agent`; a user-owned question remains `awaiting-user-input`. `awaiting-main-agent` means a coordinator action or fact is required. Waiting on your own subagent, review, or CI is progress, recorded as a wait under [Report status](#report-status). ## Report status At every checkpoint and terminal outcome, make exactly one call: ```bash uv run --script "${CLAUDE_PLUGIN_ROOT}/scripts/report-task-status.py" \ --instruction-path <your exact instruction path> \ --status <done|failed|awaiting-authorization|awaiting-user-input|awaiting-main-agent> \ --note "<outcome or exact unblock>" --ref "<proof when needed>" ``` The command persists status before notifying the recorded main-agen