chore: bump all outdated deps to latest

[isamu]

Summary

Bump every outdated dependency to its latest available version (minor + patch + major), then verify the dev server still boots cleanly.

Verification

• yarn install ✅
• yarn build ✅
• yarn lint ✅
• Playwright dev-server smoke ✅ — yarn dev started, page navigated, no console.error / pageerror / failed network requests within 2s of load

Bumps by category

Universal (all 34 plugins)

• vite ^8.0.x → ^8.1.0
• @tailwindcss/vite ^4.2.4 → ^4.3.1

Plugin-specific majors that survived the smoke

• @vitejs/plugin-react ^4.7.0 → ^6.0.3 (Avatar, MindMap, MoodBoard, Template, Quiz)
• three ^0.174.0 → ^0.184.0 + @types/three (Avatar)
• @types/node ^25.x → ^26.0.1 (Mulmocast, Markdown, Present3D)
• openai ^4.x → ^6.45.0 (MindMap)
• eslint-plugin-react-hooks ^5.2.0 → ^7.1.1 (MindMap, MoodBoard)
• marked → ^18.0.5 (TextResponse, SummarizePdf, Markdown)

Other minor / patch

• tsx, vitest, vite-plugin-dts, typescript-eslint, @types/react, react, react-dom, @types/google.maps, @pixiv/three-vrm, exa-js, @mulmochat-plugin/ui-image, plugin-local deps

Items to Confirm / Review

• The smoke test is shallow (just "does it load without errors"). It does NOT exercise any plugin's interactive flow. Reviewers may want to manually open the dev server for plugins where this PR ships a Major bump
• xlsx (Spreadsheet, exotic tarball pinned) intentionally skipped
• Lockfile churn is large because vite 8.1 pulls fresh rolldown/@oxc-project/* versions

User Prompt

ほか、これらの dir で update 可能なパッケージがあればすべて上げていきたい。lint や build が壊れないように気をつけてね。

(続) playweight とかで全部起動してテストして。そのあと PR。

🤖 Generated with Claude Code

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	vite@​8.0.11 ⏵ 8.1.0		+18	+1	+2
	@​tailwindcss/​vite@​4.2.4 ⏵ 4.3.1	+1		+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @emnapi/runtime is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@tailwindcss/vite@4.3.1 → npm/vite@8.1.0 → npm/@emnapi/runtime@1.11.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/runtime@1.11.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report