[KennyMcSimpson]

Problem

The production dependency dompurify was pinned to 3.4.15, which is affected by one critical and one high severity security advisory.

Changes

• Update dompurify to 3.4.17.
• Regenerate pnpm-lock.yaml so the direct dependency and resolved package metadata stay in sync.

Verification

• pnpm install --frozen-lockfile passed.
• Production dependency audit is clear of high and critical findings; only the existing low severity KaTeX advisory remains.
• Typecheck, tests, and production build passed.