gto-agent-communication

# GT Office Agent CLI Communication Use `gto` as the default communication interface for GT Office agent collaboration. If `gto` is not on `PATH`, run `node tools/gto/bin/gto.mjs` from the GT Office repository instead. ## Quick Rules - Prefer `gto send <from> <to> <text>` for normal one-shot task dispatch. - Use `gto send ... --wait` when the sender explicitly needs the next reply in the same task thread. - Use `gto wait <taskId> --from <agent>` when you already have a task id and only need to wait for the next reply. - Use `gto inbox <agent>` to inspect open task threads for one agent. - Use `gto thread <taskId>` to inspect the full conversation history for one task. - Use `gto agent send-task`, `gto agent reply-status`, or `gto agent handover` only when you need the lower-level explicit form. - Always carry forward the returned `taskId` from the original task dispatch. - Do not send follow-up updates without `taskId`. ## Environment Defaults When GT Office launched the terminal, prefer the injected defaults: - `GTO_WORKSPACE_ID` - `GTO_AGENT_ID` If those variables are present, you can omit `--workspace-id` and `--agent-id`. ## Core Commands Send a task: ```bash gto send manager build "Review the migration plan and reply with blockers." --json ``` Send and wait for the next reply: ```bash gto send manager build "Review the migration plan and reply with blockers." --wait --timeout-sec 120 --json ``` Reply with a status update: ```bash gto agent reply-status --ta...