Distinguish top-level review wakes from subtask completion

Top-level tasks submitted to in_review fired the same
subtask_completed wake as the subtree leaves, so the reviewer's
prompt framed the work as "a subtask you delegated". Add a dedicated
task_review_requested wake reason with a reviewer-specific title and
step list, and route the parent-less branch of the task PATCH handler
through it.

src/main/orchestration/initial-user-turn.ts

@@ -87,6 +87,8 @@ function buildGenericWakeTurn(trigger: string | null): string {
       return "An approval you requested has been decided. Act on the outcome surfaced in your briefing.";
     case "subtask_completed":
       return "A subtask you delegated is ready for review. Evaluate the work against its acceptance criteria and either accept it or request changes.";
+    case "task_review_requested":
+      return "A direct report submitted a top-level task for your review. Validate against the original acceptance criteria before deciding.";
     case "goal_activated":
       return "A goal you own has been activated. Decompose it into projects and tasks, then delegate the first batch of work.";
     case "report_blocked":