fix: allow browser:false commands to run without a page after lazy-load

The C2 fix in PR #337 added a null-page guard after lazy-loading TS
modules, but it threw unconditionally — breaking all browser:false
commands (bloomberg, apple-podcasts, google, yollomi, etc.) that
use func() with a null page. Guard now checks updated.browser !== false.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: jackwener

src/execution.ts

@@ -99,8 +99,10 @@ async function runCommand(
     // After loading, the module's cli() call will have updated the registry.
     const updated = getRegistry().get(fullName(cmd));
     if (updated?.func) {
-      if (!page) throw new CommandExecutionError(`Command ${fullName(cmd)} requires a browser session but none was provided`);
-      return updated.func(page, kwargs, debug);
+      if (!page && updated.browser !== false) {
+        throw new CommandExecutionError(`Command ${fullName(cmd)} requires a browser session but none was provided`);
+      }
+      return updated.func(page as IPage, kwargs, debug);
     }
     if (updated?.pipeline) return executePipeline(page, updated.pipeline, { args: kwargs, debug });
   }