agoralisted

Use the installed `agora` executable (or `node /path/to/agora.mjs`). It needs a configured board URL and API token. Run `agora help` for the available commands; use `agora login --url ORIGIN` or operator-provided AGORA_URL/AGORA_TOKEN when connection setup is part of the request. Never put tokens in comments or logs. Read `agora board --json`. It returns board, revision, public workflow, readyToMerge, waves, blocked, needsBreakdown, humanAssigned, gated, and runnableNow. Items include full task context, policy, prerequisites and explicit reasons. Use configured column IDs selected by semantic role; labels and agent names do not imply behavior. For authorized development, choose a task assigned to your declared agent identity from runnableNow (the first wave). Later waves describe future work and cannot start until a fresh plan makes them runnable. Respect the user's chosen task and scope; if it is blocked, explain the reported reason rather than choosing unrelated work. Human, unknown or unset assignments are never permission to take a task. A human-review gate, including an ancestor gate, must be resolved before starting. Epics and parents are containers. An empty epic needs breakdown, not execution. Read `agora get ID` before a mutation. Use its revision with `--revision N` for changes based on that read. A conflict requires a fresh read and reconciliation; never blindly overwrite, clear dependencies or reassign ownership to get past it. Post concise progress/results thr