chore(deps): bump dompurify from 3.4.12 to 3.4.13 in /web/frontend

[dependabot]

Bumps dompurify from 3.4.12 to 3.4.13.

Release notes

Sourced from dompurify's releases.

DOMPurify 3.4.13

• Fixed an issue with hook removal during IN_PLACE sanitization, thanks @​koyokr
• Fixed an issue with hooks potentially bypassing the clone guard, thanks @​AkshayjainG
• Fixed an issue with DOM clobbering via ownerDocument during IN_PLACE, thanks @​AkshayjainG
• Bumped several dependencies where possible

Commits

• 3067f77 release: 3.4.13 (#1562)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[padak]

Verified as part of a batch review of all six open Dependabot PRs (#554, #555, #558, #559, #563, #564), all of which close open Dependabot security alerts.

All six were merged into a single throwaway branch off main and validated together, because a clean line-based merge of a lockfile does not by itself guarantee the lockfile stays internally consistent:

• all six merge into main with no conflict;
• web/frontend: npm ci succeeds and npm run build (tsc -b && vite build) passes — tsc type-checks the mermaid.render() / mermaid.initialize() call sites against mermaid 11.16.1's own type definitions, which is the only safety net here since the SPA has no tests;
• npm ls dompurify confirms the overrides block still pins dompurify 3.4.13 tree-wide, including under mermaid (which itself declares ^3.3.3);
• web/backend: npm ci succeeds;
• Python: full suite green on the combined state with cryptography 50.0.0 — 5489 passed, 161 skipped;
• cryptography 50.0.0's breaking changes (FFDH deprecation, stricter DER/X.509/OCSP parsing, PKCS#7 decryption) do not touch kbagent's usage, which is limited to RSA keypair generation plus PKCS8/SPKI PEM serialization in services/workspace_service.py. Smoke-tested that exact API surface against 50.0.0.

Note for follow-up, unrelated to these PRs: npm audit reports a high-severity advisory for nanoid@3.3.16 (GHSA-2v37-7h3g-55p8) in both web/frontend and web/backend, pulled in transitively via postcss. It is build-time only and never reaches the shipped bundle, and Dependabot has not raised an alert for it.