feat(mission-control): give the list handler its own review task

"Let Claude handle it" now creates one ClaudeDo task per run to host the
ConPTY session (Idle/IsManual, never queued) instead of an untracked
ad-hoc tile, so the run has a real title, diff, and review outcome.
Since the handler merges its own changes straight into the list's
working dir, the task never gets a WorktreeEntity; its review range
lives as new HandlerBaseCommit/HandlerHeadCommit columns on TaskEntity
instead, reusing the existing commit-range diff machinery and keeping
it out of the worktrees overview entirely.

docs/open.md

@@ -65,6 +65,19 @@ Offene Entscheidungen dazu:
   LIST column. Plus a real-Claude smoke run of the five phases (dedupe questions, enhancements
   landing in task descriptions, queued execution, merges).
 
+## Offene Verifikation (2026-08-05)
+
+- **List handler owns a task (2026-08-05)** — build + unit tests all green, but **not visually
+  verified**: start "Let Claude handle it" on a list, confirm exactly one new task appears in that
+  list (`Idle`, MANUAL badge, title "List handler: <list>"), the Mission Control tile is
+  task-based (Submit for review button present), Submit for review flips it to
+  `WaitingForReview`, and the detail pane's diff/merge card shows the full range of everything the
+  run merged to main (via the new `HandlerBaseCommit`/`HandlerHeadCommit` fallback — no
+  `WorktreeEntity` is created for this task, so the diff comes from `list.WorkingDir` directly).
+  Approve should go straight to `Done` with no merge attempt. Design choice: the review range
+  lives as two new nullable columns directly on `TaskEntity` (not a phantom `WorktreeEntity` row),
+  specifically so `list_worktrees`/the Worktrees overview never see it.
+
 ---
 
 ## Bewusst verworfen (nicht erneut vorschlagen)