fix(deps): take the fixes for proxy-addr, source-map-js and katex that turn main's OSV scan red

pnpm-workspace.yaml

@@ -536,3 +536,36 @@ overrides:
   #     written. Transitive-only and dev-only: nothing publishable declares
   #     undici, and both paths reach the tree through devDependencies.
   'ip-address@<11.0.0': '^10.5.1'
+  # OSV 2026-10-06 (#21945, scheduled scan run 37407261685) — one advisory that
+  # names a fixed version, so this is the "take the fix" path osv-scanner.toml's
+  # header prescribes and NOT an exemption.
+  #   katex GHSA-238p-pmpm-9mq7 (2.1 low) — an inherited `Object.prototype.trust`
+  #     is read as an explicit `trust: true`, so a prototype pollution that
+  #     already exists elsewhere lets attacker math emit links or load external
+  #     resources. Range introduced:0.11.0 -> fixed:0.18.2, read from the OSV
+  #     offline npm database the scanner downloads. Flagged at the single
+  #     resolved copy 0.16.47.
+  #   ⚠️ Unlike the dedupes above, this is a FORCED upgrade past the dependent's
+  #     declared range. The one consumer is mermaid@11.16.1 (apps/docs declares
+  #     mermaid ^11.16.0), which declares katex ^0.16.45, and no published
+  #     mermaid admits the fix: 11.17.0 through 12.1.0 all declare ^0.16.47
+  #     (npm view, 2026-10-06). mermaid touches katex in one place, a lazy
+  #     `import("katex")` that calls the default export's renderToString() with
+  #     { throwOnError, displayMode, output } for a `$$...$$` label. The 0.17 and
+  #     0.18 breaking changes (the internal __defineFunction API, prefixed
+  #     internal CSS classes) touch neither that call nor the outer `.katex`
+  #     class mermaid styles. Measured: a mermaid 11.16.1 flowchart with a
+  #     `$$...$$` label renders MathML through katex 0.18.10 in Chromium, under
+  #     the same initialize() options apps/docs/components/mermaid.tsx passes.
+  #     The target resolves to 0.18.10, not 0.18.11: 0.18.11 is deprecated on
+  #     npm ("Accidentally published with breaking changes"), and pnpm skips it.
+  #   Transitive-only and docs-only: nothing publishable declares katex, so
+  #     check-override-consistency.mjs's manifest rule has no declared range to
+  #     hold in lockstep and says nothing about this entry (measured; neither
+  #     census lists it: mermaid consumes it, and the bound clears the target
+  #     floor). The floor is the advisory's 0.11.0; the bound is 0.19.0, the
+  #     caret boundary of the 0.18 target line, per this block's header rule —
+  #     never `<0.18.2`.
+  #     Re-check when a mermaid release declares a katex range that admits
+  #     0.18.2: the entry then turns into a dedupe and stays as the floor.
+  'katex@>=0.11.0 <0.19.0': '^0.18.2'