chore(deps): update dependencies

[trpfrog]

Summary

• Update 99 of the 102 dependency-candidate package keys from the update document.
• Node.js support configuration remains unchanged; the existing engine range and CI already allow Node.js 24.
• Do not apply any proposed new features.
• Keep breaking-change adaptations and regression tests grouped by dependency for reviewability.
• Remove the webpack-only Next.js configuration. The normal production build path remains Turbopack; no webpack build was run.

Updated major dependencies

• ai 7.0.77 and @ai-sdk/openai 4.0.46.
• cssnano 8.0.8.
• nanoid 6.0.1.
• p-retry 8.0.0, with an explicit retry-attempt regression test.

Intentionally held back

• wrangler remains at 3.114.17. PR Bump up modules, fix tests and improve CI #113 documented that its bundled workerd Linux binary required glibc 2.35 while Vercel's Amazon Linux 2023 build image provided glibc 2.34, causing postinstall/deployment failure. This is independent of the Node.js 24 support decision.
• @vitest/coverage-v8 and @vitest/ui remain at 4.1.10 because Vite Plus 0.2.9 bundles Vitest 4.1.10 and rejects mismatched coverage providers.

Compatibility changes

• Prisma 7: add the PlanetScale adapter and move the generated client/configuration to the Prisma 7 layout.
• Hono, js-yaml, Next MDX metadata, type-fest, Workers execution context mocks, and Font Awesome snapshots: preserve existing behavior after API or output changes.
• Devicon: use the BOM-free base stylesheet so Turbopack can parse it.
• The webpack-only Next.js hook is removed. Webpack remains only where required transitively by the existing MDX toolchain; it is not used as the project's build mode.

Validation

• pnpm -w test: 5 projects, 232 tests passed.
• CI-equivalent pnpm exec vp test run --coverage.enabled --coverage.provider=v8 --coverage.reporter=json-summary --coverage.reporter=json --coverage.reportOnFailure=true: 37 files, 235 tests passed.
• TypeScript checks passed for all 8 workspace tsconfig files.
• GitHub Actions Node 24.x test and coverage job passed.
• cssnano 8 passed a direct PostCSS compression smoke check.
• pnpm --filter trpfrog.net build remains incomplete locally: after moving the stale .next directory aside and starting from a clean build directory, Turbopack still remained at Creating an optimized production build ... for 60 seconds and was stopped. This was reproduced with AI SDK 6 and 7, cssnano 7 and 8, and with cssnano disabled, so it is not attributed to one of these dependency updates. No webpack fallback was used.
• A one-off Vercel Preview deployment of the current HEAD with TURBO_FORCE=1 and Vercel's force/no-cache deployment option performed a fresh build successfully: the logs report Cached: 0 cached, 8 total, Build Completed in /vercel/output, and Deployment completed. Thus the fresh Turbopack compile succeeds in the Vercel build environment even though the local macOS build remains stuck.

The dependency update document and regression specification memo remain untracked and are intentionally excluded from this PR. The working-tree-only partialPrefetching change is also excluded.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
admin.trpfrog.net	Ready	Preview	Aug 22, 2026 5:36pm
trpfrog-net	Ready	Preview	Aug 22, 2026 5:36pm

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	65.6%	538 / 820
🔵	Statements	65.52%	555 / 847
🔵	Functions	63.77%	169 / 265
🔵	Branches	63.46%	238 / 375

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
apps/image-generation/src/controller/resource.ts	5.88%	0%	0%	5.88%	10-32
packages/utils/src/deps-resolver.ts	100%	100%	100%	100%

Generated in workflow #311 for commit 806a9f2 by the Vitest Coverage Report Action

[trpfrog]

レビューコメントに対応しました。

• resource controller: ! を使わず、欠落時は 400 を返す明示的なガードに変更しました。vite.config.ts に typescript/no-non-null-assertion: error を追加し、今後の non-null assertion を lint で検出します。
• UUID v7 テスト: version nibble (7) と RFC 9562 variant bits (10xx) を確認する意図があるため、UUID_V7_PATTERN 定数へ切り出しました。新しい依存は追加していません。
• js-yaml: v5.3.0 の ESM export map が公開している named export load を使う必要があるためです。対象の import 箇所は同じ方針に統一しています。
• legal MDX metadata: MDX の named export 全般が非対応という意味ではありません。今回の Next.js 16.3.2 + @next/mdx + mdxRs 構成では、MDX page 内の route metadata が安定して認識されなかったため、Next.js の route-segment convention である layout.tsx に移してタイトルを維持しています。

追加コミット: 11c14cdd, 4a5efecd。Node.js 24 の CI と Vercel preview は pass 済みです。

[trpfrog]

署名付きrebaseを完了しました。origin/main以降の54コミットをSSH署名付きで再作成し、force-with-leaseでPRブランチを更新しています。先ほどのレビュー回答に記載した 11c14cdd / 4a5efecd はrebase前のIDで、現在の対応コミットは da4d97fa / 806a9f21 です。GitHub Test、Vercel admin、Vercel trpfrog-net は全てpassしています。