chore(deps): update dependency @docusaurus/theme-mermaid to ^3.10.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
@docusaurus/theme-mermaid (source)	dependencies	minor	^3.9.2 → ^3.10.0

---

Release Notes

facebook/docusaurus (@​docusaurus/theme-mermaid)

v3.10.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}

[claude]

Code Review: Dependency Update — @docusaurus/theme-mermaid ^3.9.2 → ^3.10.0

This is a routine Renovate Bot minor version bump confined entirely to the docs/ folder. The review covers both the intent and any structural concerns.

What Changed

• docs/package.json: Single line change bumping @docusaurus/theme-mermaid from ^3.9.2 to ^3.10.0
• docs/yarn.lock: 274 lines of transitive lock file updates pulling in the full @docusaurus/*@3.10.0 ecosystem as deps of the new theme-mermaid

Observations

Partial ecosystem upgrade (worth noting, not a blocker)
Only @docusaurus/theme-mermaid is pinned to ^3.10.0 in package.json, while the rest of the Docusaurus stack (@docusaurus/core, @docusaurus/preset-classic, etc.) stays at 3.9.2. The lock file ends up carrying both 3.9.2 and 3.10.0 variants of the @docusaurus/* packages. This is technically fine — Yarn resolves them correctly as separate entries — but it does mean the docs bundle will carry duplicate copies of Docusaurus internals.

If there's ever a desire to keep the Docusaurus ecosystem in sync, bumping all @docusaurus/* packages together (rather than one at a time) would avoid the dual-version bloat in the lock file. That said, for a docs-only dependency this is a cosmetic concern, not a functional one.

Registry source difference (not a concern)
New 3.10.0 entries resolve from registry.yarnpkg.com vs the existing 3.9.2 entries from registry.npmjs.org. Both are the same registry under different mirrors — no issue here.

No source code impact
All changes are scoped to docs/. No TUnit engine, test framework, source generator, or CI pipeline code is affected.

Verdict

The change looks correct. Auto-merge is appropriate for this routine docs dependency update.