Correct comments left stale by the main-shell mouse default flip

These four spots described mouse reporting as off by default,
matching the main shell's old behavior. The satellite pickers still
keep reporting off on purpose, but the main shell now defaults it
on, so the comments read backwards. Reword them to state each
surface's actual behavior instead of claiming they match, and
update the readiness doc to describe the decision as settled with
current line references.

Author: TheGreatAxios

docs/tui-cutover-readiness.md

@@ -99,12 +99,14 @@ performed.
    the shell's key handler), but the reported real-terminal failure is not
    reproduced or explained. Until someone pastes into a real TTY, treat text paste
    as unverified.
-2. **Mouse selection policy (CL-5540).** DEC mouse reporting is moving to
-   off-by-default (`mouseCapture` in `src/tui-opentui/product-host.ts:101`) so the
-   terminal owns drag-select and copy. The cost is that click-to-expand and
-   drag-scroll are off unless the user presses `Alt+M`
-   (`src/tui-opentui/shell.ts:3392`). This is a deliberate trade, but it is a
-   visible regression for mouse users and the default is not settled.
+2. **Mouse selection policy (CL-5540).** DEC mouse reporting defaults on in
+   the main shell (`useMouse` in `src/tui-opentui/product-host.ts:218`), so
+   wheel scroll and click-to-expand work out of the box. The cost is native
+   text selection, which the terminal cannot perform while reporting is on;
+   `Alt+M` (`toggleMouseCapture` in `src/tui-opentui/shell.ts:4006`) hands the
+   mouse back for that. The satellite pickers (`list-modal.ts`,
+   `provider-setup.ts`) keep reporting off and are unaffected. This is the
+   settled decision, not a pending tradeoff.
 3. **Shift+Enter does not insert a newline on terminals that do not report the
    modifier.** `Ctrl+Enter` and `Ctrl+J` are the working newline chords and the
    help catalog says so (`src/tui-opentui/keybindings.ts`). The kitty keyboard

src/tui-opentui/list-modal.ts

@@ -44,9 +44,8 @@ export async function runListModal(
     : await createCliRenderer({
         exitOnCtrlC: false,
         targetFps: 30,
-        // Same trade as the product host (CL-5540): reporting off by default
-        // so the terminal owns drag-select and its own copy in these satellite
-        // pickers too.
+        // Reporting stays off in this satellite picker, unlike the main
+        // shell, so the terminal owns drag-select and its own copy here.
         useMouse: false,
         enableMouseMovement: false,
       })

src/tui-opentui/mouse-reporting-disabled.test.ts

@@ -1,10 +1,11 @@
 /**
  * CL-5540: the onboarding provider picker and the satellite list modals
  * (session resume, session mode) mount their own renderer and must disable
- * DEC mouse reporting the same way the product host does, or the terminal
- * never gets button-1 drags to run its own text selection. These tests mock
- * `@opentui/core` so the real (non-test-injected) `createCliRenderer` branch
- * runs, and assert on the options it was actually called with.
+ * DEC mouse reporting, unlike the main shell, or the terminal never gets
+ * button-1 drags to run its own text selection in these pickers. These
+ * tests mock `@opentui/core` so the real (non-test-injected)
+ * `createCliRenderer` branch runs, and assert on the options it was
+ * actually called with.
  */
 import { afterAll, describe, expect, mock, test } from "bun:test"
 import type { Harness } from "./harness.js"

src/tui-opentui/provider-setup.ts

@@ -586,8 +586,8 @@ export async function runProviderSetup(
     : await createCliRenderer({
         exitOnCtrlC: false,
         targetFps: 30,
-        // Same trade as the product host (CL-5540): reporting off by default
-        // so the terminal owns drag-select and its own copy during onboarding.
+        // Reporting stays off during onboarding, unlike the main shell, so
+        // the terminal owns drag-select and its own copy here.
         useMouse: false,
         enableMouseMovement: false,
       })