routelisted

# Route `/route` classifies every ticket of a run on four dimensions — workflow, executor, model, effort — plus the review lane the reviewed workflows carry, writes each conclusion into its ticket as a `## Routing` section, and ends by staging the run directory whose exact `/crew` command it prints. That section is **advisory input**: `/crew`'s driver builds and validates its wave table from it, and from that validation onward the wave table is the sole routing authority. Three entrances, one exit — whichever was typed, the run ends at the staging script: | Typed | The run's ticket set | | --- | --- | | `/route #<parent>` | the parent ticket's open sub-issues | | `/route #<a> #<b> …` | exactly those tickets, whether or not they share a parent | | `/route <spec-or-feature-dir>` | cut from that spec first — **to-tickets+route** | Routing is a **suggestion**: steps 1–3 read and propose, step 4 is the first write, and the user decides at the one checkpoint between them. ## 1. Settle the mode A repo with no `agentcrew.toml` at its root is a first run: go to the setup wizard in [`references/setup.md`](references/setup.md), and resume here once it is done. The same wizard reconfigures a repo whenever the user asks, and fills a config an upgrade left a key short. Settle the tracker: [`references/trackers.md`](../../references/trackers.md) turns this repo's `docs/agents/issue-tracker.md` into the **read**, **edit**, and **mark** operations the steps below call. Then settle the