fix(report): set explicit assetPrefix to avoid runtime publicPath error (#2345)

* fix(report): set explicit assetPrefix to avoid runtime publicPath error

Without an explicit output.assetPrefix, rsbuild defaults to 'auto',
which relies on document.currentScript.src at runtime. Combined with
inlineScripts: true the src is empty, and some browsers throw
'Automatic publicPath is not supported in this browser' when the bundle
tries to resolve asset paths. This surfaced in 1.7.x when reports moved
to the html-and-external-assets layout (with externalized screenshots).

Setting assetPrefix: './' makes rspack emit relative paths and skip the
runtime auto-detection path entirely.

* feat(core): warn when ReportMergingTool meets a version-mismatched source report

Users who install @midscene/android and @midscene/core at different
versions (commonly 'latest' on core while pinning android to a prepatch)
end up with ReportMergingTool loaded from the older @midscene/core at
the package root while the agent generates reports from the newer core
nested under @midscene/android. Before #2153's per-execution append
model, mergeReports read only the last <script type="midscene_web_dump">
tag per source file, which silently drops every intermediate action and
leaves the merged report with nothing but the test's final step.

Peek at the source report's sdkVersion on append and log a clear warning
when it differs from the merger's own getVersion(), so the mismatch
surfaces before the user spends time debugging an empty-looking report.

Author: quanru

apps/report/rsbuild.config.ts

@@ -154,6 +154,7 @@ export default defineConfig({
     },
   },
   output: {
+    assetPrefix: './',
     inlineScripts: true,
     injectStyles: true,
   },

packages/core/src/report.ts

@@ -29,7 +29,7 @@ import {
   ReportActionDump,
 } from './types';
 import type { ReportFileWithAttributes } from './types';
-import { getReportTpl, reportHTMLContent } from './utils';
+import { getReportTpl, getVersion, reportHTMLContent } from './utils';
 
 /**
  * Check if a report is in directory mode (html-and-external-assets).
@@ -58,6 +58,24 @@ export function dedupeExecutionsKeepLatest<T extends Pick<ExecutionDump, 'id'>>(
   }
   return Array.from(deduped.values());
 }
+/**
+ * Peek at the first `sdkVersion` field embedded in a midscene_web_dump
+ * script tag inside the given report file. Returns undefined if no
+ * recognizable tag or sdkVersion is present.
+ */
+function peekReportSdkVersion(reportFilePath: string): string | undefined {
+  try {
+    const dump = extractLastDumpScriptSync(reportFilePath);
+    if (!dump) return undefined;
+    const match = dump.match(/"sdkVersion"\s*:\s*"([^"]+)"/);
+    return match?.[1];
+  } catch {
+    return undefined;
+  }
+}
+
+const warnedMismatchedVersions = new Set<string>();
+
 export class ReportMergingTool {
   private reportInfos: ReportFileWithAttributes[] = [];
 
@@ -72,6 +90,21 @@ export class ReportMergingTool {
   }
 
   public append(reportInfo: ReportFileWithAttributes) {
+    if (reportInfo.reportFilePath) {
+      const sourceVersion = peekReportSdkVersion(reportInfo.reportFilePath);
+      const currentVersion = getVersion();
+      if (
+        sourceVersion &&
+        currentVersion &&
+        sourceVersion !== currentVersion &&
+        !warnedMismatchedVersions.has(sourceVersion)
+      ) {
+        warnedMismatchedVersions.add(sourceVersion);
+        logMsg(
+          `[@midscene/core] ReportMergingTool version mismatch: source report was written by @midscene/core@${sourceVersion} but the merger is @midscene/core@${currentVersion}. This commonly means @midscene/core and the device package (e.g. @midscene/android) resolve to different versions in node_modules. Merged output may silently drop intermediate steps. Align the versions and reinstall (rm -rf node_modules package-lock.json && npm install).`,
+        );
+      }
+    }
     this.reportInfos.push(reportInfo);
   }
   public clear() {