fix(controlBrowser): never report moveMouse/search success without a real move

moveMouse returned ok:true even when humanHover did nothing (no on-screen box)
or the selector never matched — recreating the "claims it moved but didn't"
bug. Now: humanHover returns a boolean (and brings the element into view first);
moveMouse returns ok:false when the target isn't found or has no on-screen box,
and when site=naver/... whose box isn't on the current page it navigates to the
site home first before hovering. search now reports input=human|api-fallback|api
so a silent fallback to cursor-less DOM input is visible, and the tool surfaces
that note in the reply instead of implying a human-like search happened.

bot/scripts/stream-test/human.mjs

@@ -136,14 +136,18 @@ export async function navigateOmnibox(text) {
 }
 
 // Move the real cursor over an element (hover, no click) - e.g. to reveal a
-// video player's controls or to focus it for a keyboard shortcut.
+// video player's controls or to focus it for a keyboard shortcut. Returns true
+// only if the element had an on-screen box and the cursor was actually moved;
+// returns false when there is nothing to move to (so callers must not report
+// success). Brings the element into view with a real wheel scroll first.
 export async function humanHover(page, locator) {
-  const box = await locator.boundingBox().catch(() => null);
-  if (!box) return;
+  const box = await bringIntoView(page, locator);
+  if (!box) return false;
   const g = await page.evaluate(() => ({ sx: window.screenX, sy: window.screenY, ow: window.outerWidth, oh: window.outerHeight, iw: window.innerWidth, ih: window.innerHeight }));
   const bx = Math.max(0, Math.round((g.ow - g.iw) / 2));
   const oy = g.sy + Math.max(0, g.oh - g.ih - bx);
   await humanMove(Math.round(g.sx + bx + box.x + box.width * 0.5), Math.round(oy + box.y + box.height * 0.4));
+  return true;
 }
 
 export { sleep, rand };