Extend the model picker to schedules

schedules.model_id (migration 0013) pins every fired run of a recurring spawn
to a registered model backend, exactly like a hand-spawned agent: the worker
copies it into each firing's spawn payload, the launched agent records the pin,
and resumes stay on the same backend. The Schedules form gets the same Model
dropdown as the spawn form (Claude subscription by default), with a badge in
the schedules table. Create/update routes fail fast on a missing or disabled
backend so a stale selection bounces immediately instead of every firing
failing asynchronously in Activity; a backend deleted later still fails each
firing visibly rather than silently falling back to the subscription.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DzDofD7gP63WpeLG8vEdZu

docs/local-models.md

@@ -14,7 +14,8 @@ thing a **model backend** changes is the environment of that one agent's process
 | `CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC` | `1` (skip sidecar calls a local endpoint won't serve; override via the row's env map) |
 
 Register backends on the dashboard's **Claude → Models** tab (or `POST /claude/models`),
-then pick one from the **Model** dropdown when spawning an agent. No selection = the
+then pick one from the **Model** dropdown when spawning an agent — or on a **Schedule**,
+so every fired run spawns on that backend. No selection = the
 worker's logged-in Claude subscription, exactly as before. The agent is *pinned* to its
 backend: resumes come back up on the same one, and deleting a backend makes resumes of
 its agents fail loudly rather than silently falling back to the subscription.