Placement: show where a task lands, and let Start

Goal: an operator whose project spans MicroVM and static nodes knows where the next task will land, and is never stuck on an old MicroVM hold. 1. For a project assigned to both MicroVM and static nodes, show the landing per provider/auth pair (Claude subscription, Claude API key, Gemini API key, …), or let the operator prefer static nodes for the project. 2. After Stop or Reset, Start offers "Start fresh elsewhere" instead of only resuming on the old MicroVM hold (today only Reset + Start moves it). Out of scope: the placement policy itself; billing rules; the wait-reason sentences (Task 7780). Done means: - On dev, a project on one MicroVM and one static node shows the landing per pair (or prefer-static moves the next task to the static node). - A stopped task held on a MicroVM node starts fresh on another node from Start; a test covers release + re-place. Required checks: ./dc check full Carries draft 7802 unchanged in scope.

Prefer-static-nodes per project + "Start fresh elsewhere" (release + re-place, tested) merged via PR #6216 (f94d1bca8). Full gate passed except develop's own Vale "Superadmin" lint (draft 7907). Its deploy is superseded by newer queued deploys.