diff --git a/packages/vitest-native/scripts/fidelity-report.mjs b/packages/vitest-native/scripts/fidelity-report.mjs
index e424ff5..4fc0232 100644
--- a/packages/vitest-native/scripts/fidelity-report.mjs
+++ b/packages/vitest-native/scripts/fidelity-report.mjs
@@ -98,12 +98,25 @@ const knownDiffs = fs.existsSync(knownDiffsPath)
   ? JSON.parse(fs.readFileSync(knownDiffsPath, "utf8"))
   : [];
 
+// The page is built by VitePress, which parses Markdown as Vue: a bare `<Tag>`
+// in free text is read as an (unclosed) HTML element and breaks the build, `|`
+// breaks table columns, and `{{ }}` is Vue interpolation. Probe names/reasons
+// and known-difference text come from the corpus, so escape those hazards in
+// any cell rendered as free text (not inside a code span).
+const cell = (s) =>
+  String(s ?? "")
+    .replace(/\|/g, "\\|")
+    .replace(/</g, "&lt;")
+    .replace(/>/g, "&gt;")
+    .replace(/\{\{/g, "&#123;&#123;")
+    .replace(/\}\}/g, "&#125;&#125;");
+
 const probeRows = probes
-  .map((p) => `| \`${p.name}\` | ${p.match ? "✅ match" : `❌ ${p.reason ?? "diverged"}`} |`)
+  .map((p) => `| \`${p.name}\` | ${p.match ? "✅ match" : `❌ ${cell(p.reason ?? "diverged")}`} |`)
   .join("\n");
 
 const knownDiffRows = knownDiffs.length
-  ? knownDiffs.map((d) => `| ${d.area} | ${d.difference} | ${d.why} |`).join("\n")
+  ? knownDiffs.map((d) => `| ${cell(d.area)} | ${cell(d.difference)} | ${cell(d.why)} |`).join("\n")
   : "| _none recorded_ | | |";
 
 const page = `<!--
diff --git a/website/guide/fidelity.md b/website/guide/fidelity.md
index 762f29f..1b4c60e 100644
--- a/website/guide/fidelity.md
+++ b/website/guide/fidelity.md
@@ -113,5 +113,5 @@ They are documented here rather than hidden.
 | Area | Behavior | Why it isn't gated |
 | --- | --- | --- |
 | Default device metrics (Dimensions / PixelRatio) | The default window/screen size, pixel ratio and font scale are a fixed test-host default. Both engines report the same default — the cross-check gates that — but it is not any specific physical device. | Device metrics aren't behavior, and the default won't match a real device. Tests that depend on exact metrics should set them explicitly (e.g. Dimensions.set) rather than rely on the default. |
-| Text onPress accessibilityRole | A <Text> with an onPress handler is auto-assigned accessibilityRole "link" by some React Native versions and not others. | Version-variant across the supported RN range — a single mock value can't match every minor, so it isn't pinned by a probe. |
+| Text onPress accessibilityRole | A &lt;Text&gt; with an onPress handler is auto-assigned accessibilityRole "link" by some React Native versions and not others. | Version-variant across the supported RN range — a single mock value can't match every minor, so it isn't pinned by a probe. |
 | Appearance color scheme | Appearance.getColorScheme() reflects the host environment rather than a fixed value. | Environment-dependent (CI vs local, OS settings), so it isn't a stable cross-engine invariant to gate. |