A routine can be configured before it is run (fix #1507)

FEATURES-SPEC.md

@@ -24,6 +24,7 @@ happens while nobody is at the keyboard.
 - Start an agent from a ticket row
 - Start an agent from a queue entry's play button
 - "Run now" on a routine
+- "Configure first, then run" on a routine — the launcher opens with its prompt, so the model and location can be set first
 - The whole CLI is one command: `the-framework` serves the dashboard — four options, no verbs
 - `--host` / `--port`, the two things a browser cannot be asked; `--help` / `--version`
 - Reach the dashboard from another machine — non-loopback bind behind a generated shared token

packages/the-framework/dashboard/components/DashboardPage.tsx

@@ -69,7 +69,7 @@ export function DashboardPage({
 
         {/* Routine work sits below the AI Queue (#1139/#1159): the scheduled jobs and the button
             that fires one now. */}
-        <RoutineWork onAgentStarted={onAgentStarted} />
+        <RoutineWork onAgentStarted={onAgentStarted} onSelectProject={onSelectProject} />
 
         <HotTickets onSelectProject={onSelectProject} onSelectAgent={onSelectAgent} />
       </div>

packages/the-framework/dashboard/components/RoutineWork.SPEC.md

@@ -6,6 +6,7 @@ The Overview's Routine work card: the jobs fired by the scheduled sweep — the
 - The queue-draining routine's Run now fires a drain-only sweep — the only path that can fan out several agents, up to the concurrency setting; card-fired routines run unattended, like the sweep's own.
 - Two checkbox tiers: the master switch turns the schedule on or off, a row's box takes that one routine in or out of it — recorded as opt-outs, so a routine added by a later version runs by default.
 - "Trigger routine now" sweeps once even with auto-run off (the click is the consent), and the sweep answers on the card per project, so "ran and found nothing" never looks like "never ran".
+- Beside each Run now sits "Configure first, then run": it opens the picked project's launcher with that routine's prompt already in the box, so the model and where it runs can be set before an agent is spent. For the queue-draining routine it says what it costs — the launcher sends one agent, not the fan-out.
 
 ## Before modifying/creating SPEC.md files
 

packages/the-framework/dashboard/components/RoutineWork.test.SPEC.md

@@ -1,4 +1,4 @@
-Covers the Routine work card: routines listed by label with Run now starting the prompt verbatim (unattended, then jumping to the agent), the drain firing a fan-out-capable sweep instead, per-routine opt-out boxes versus the master auto-agent switch, the on-demand trigger working with auto-run off, the sweep's per-project answers landing on the card, the concurrency setting's clamping, and the picker, empty, failure, and busy states.
+Covers the Routine work card: routines listed by label with Run now starting the prompt verbatim (unattended, then jumping to the agent), the drain firing a fan-out-capable sweep instead, per-routine opt-out boxes versus the master auto-agent switch, the on-demand trigger working with auto-run off, the sweep's per-project answers landing on the card, the concurrency setting's clamping, "Configure first, then run" carrying the prompt to the picked project's launcher instead of starting anything (and saying so on the drain), and the picker, empty, failure, and busy states.
 
 ## Before modifying/creating SPEC.md files