feat(cli): run-ID telemetry correlation and check breakdown event

HYPERFRAMES_RUN_ID (trimmed, 128-char cap) attaches as run_id to the
generic cli_command / cli_command_result events, absent when unset, so
an orchestrator setting it per design element can group a verify loop's
invocations in analytics. check additionally emits one check_report
event per invocation (including lint-short-circuited and failing runs):
gate booleans, per-class error/warning counts, launch/seek/contrast
phase timings, sample counts, ok and exit code. Timings stay internal;
no command output changes.

packages/cli/src/utils/checkBrowser.ts

@@ -93,6 +93,7 @@ export async function runBrowserCheck(
   let chromeBrowser: import("puppeteer-core").Browser | undefined;
 
   try {
+    const launchSettleStart = Date.now();
     const session = await openSettledCompositionPage(html, server.url, {
       renderReadyTimeoutMs: options.timeout,
       renderReadyWarningSuffix: "checking the current page state",
@@ -104,12 +105,14 @@ export async function runBrowserCheck(
     await waitForPreferredSeekTarget(page, 500);
 
     const rootAnchor = await resolveRootAnchor(page);
+    const launchSettleMs = Date.now() - launchSettleStart;
     const driver = createPageDriver(page, (time) => {
       currentTime = time;
     });
     const result = await runGrid(driver, options, motion);
     return {
       ...result,
+      timings: { ...result.timings, launchSettleMs },
       runtimeFindings: drafts.map((draft) => runtimeFinding(draft, rootAnchor)),
     };
   } finally {