test(e2e): require the new-task menu to exist before calling it settled

The shared `settleMenuMode` helper read the menu's text and compared
`includes("Branch from")` against the mode. For main-checkout that wants
FALSE — which an empty string satisfies, so the wait passed while the menu was
briefly not in the DOM at all, and the click landed in Radix's remount. That is
the `!!m` guard 5eff3f3 added for this exact case and my refactor dropped;
"prompts for a name before creating a main-checkout Terminal task" then failed
in CI the way its worktree sibling used to.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01F2JzhUsFa9YLjBBvUJQGYj

Author: simion

e2e/specs/projects.e2e.ts

@@ -345,7 +345,15 @@ describe("branch new tasks from", () => {
   const settleMenuMode = async (mode: "worktree" | "main") => {
     const wantsBranchFrom = mode === "worktree";
     await browser.waitUntil(
-      async () => (await menuText()).includes("Branch from") === wantsBranchFrom,
+      async () => {
+        const text = await menuText();
+        // The menu must EXIST, not merely lack the row. Radix remounts the
+        // content while the mode flips, so there is a beat where the query
+        // finds nothing — and "" trivially satisfies "no Branch from row",
+        // which let the main-checkout case settle on a menu that was not
+        // there yet and click into the remount.
+        return text.length > 0 && text.includes("Branch from") === wantsBranchFrom;
+      },
       { timeout: 8_000, timeoutMsg: `the menu never settled into ${mode} mode` },
     );
   };