coordinationlisted

# Agent Coordination Use `cortex-agent task` and `cortex-agent event`; do not edit journal, snapshot, lease, cursor, or delivery files directly. Discover the exact machine contract with `cortex-agent help task --json`. Read operations are side-effect free: ```bash cortex-agent task status --project . --task T-001 cortex-agent task list --project . cortex-agent event list --project . --task T-001 cortex-agent query coordination-tasks --project . --state READY_FOR_REVIEW ``` Write commands delegate the complete event envelope to the Coordination Application Service using `--event-json`. The service is the only owner of schema, actor, sequence, transition, journal, and snapshot rules. ACK confirms delivery only. It never approves a Decision, releases a Waitpoint, commits, pushes, merges, publishes, dispatches, or changes task state. Operate production notifications through the public CLI: ```bash cortex-agent notification pump --project . --consumer coordinator \ --target coordinator:root --adapter codex --once cortex-agent notification pump --project . --consumer coordinator \ --target coordinator:root --adapter codex --watch cortex-agent notification pump --project . --consumer coordinator \ --target coordinator:root --adapter codex --status cortex-agent notification pump --project . --consumer coordinator \ --target coordinator:root --adapter codex --stop ``` `watch` is a foreground single-consumer process using filesystem events and bounded backoff; `status`