model-routerlisted

# model-router Scores a task, then hands it off to the matching subagent. Three tiers, one each — effort is fixed per tier, the model is whatever the project's profile resolves to. | Tier | Subagent | Effort (fixed) | Model — `frontier` (default) | `opus-centric` | `lean` | | -------- | ------------------------------ | -------------- | ---------------------------- | -------------- | ------ | | Quick | `bigin-skills:quick-executor` | low | sonnet | sonnet | haiku | | Standard | `bigin-skills:standard-worker` | high | opus | opus | sonnet | | Deep | `bigin-skills:deep-architect` | xhigh | fable | opus | opus | Two axes, scored separately, because they answer different questions: - **Capability** picks the tier, and therefore the model. Raise it when the model had the context, clearly tried, and still got it wrong. - **Verification** sets the gate discipline in the spawn payload, and never touches the model. Raise it when the failure was a skipped file, unrun tests, or a refactor abandoned partway. Breadth, coverage, and blast radius are *verification* signals. Spending them on a bigger model over-provisions routine work (a 30-file rename is not hard, just wide) and under-provisions small-but-hard work (a one-file bug in an unfamiliar subsystem is the case that actually wants a stronger model). Routes down as we