Queue view: tighter phone rows and consistent

Seen on Tasks › Queue at 1440px and 390px while verifying Task 7569. Itemized: 1. On a phone, each row takes three or four lines (title, badge, meta, then the controls on their own line). Put the priority pill and Start/Stop on the meta line when they fit. 2. Running rows' Stop is an `inherit` outlined button, but queued rows' Start is a primary outlined button. Pick one style for both lists so the verbs line up. 3. Running rows show "#1", "#2", but running work has no queue position. Drop the number there, or show the run's age. 4. An epic child's meta line repeats its epic ("in Retire the legacy export path") right under a title that already names it ("[plan] Retire the legacy export path"). Skip the "in …" part when the title already contains the epic's title. Out of scope: the hold rules (`routes/tasks.py::_dispatchable_statement`, `routes/task_queue.py::_hold_reasons`) and the board view. Done means: - Each item is implemented, or rejected with a one-line reason in the PR. - Screenshots at 1440px and 390px in the report. - `./dc check quick` green; QueueView vitest suite passes.

Queue view: phone controls share the meta line, Stop matches Start, no number on running rows, epic note skipped when the title names the epic. Rebased over 7569; quick gate green, QueueView 15/15, screenshots checked. PR #6094 queued.