chore(website): target Node.js 24, add vercel.json +semver: none

[bravo-kernel]

Bumps the website toolchain to Node.js 24 and pins it where Vercel actually reads it.

Node.js 24

File	Change
website/.nvmrc	20 → 24 (local dev parity)
website/package.json	added "engines": { "node": "24.x" }

engines.node is the part that matters for the deployment: Vercel reads the Node version from Project Settings, overridden by engines.node in package.json. It does not read .nvmrc. Per the current docs, 24.x is now Vercel's default (20.x and 22.x are the other options), so this aligns with the platform default rather than fighting it.

vercel.json

New website/vercel.json, documenting the build in-repo:

{
  "$schema": "https://openapi.vercel.sh/vercel.json",
  "buildCommand": "yarn build",
  "outputDirectory": "build"
}

Both values match what Vercel already does by auto-detection, so this is a no-op that just makes the settings reviewable. framework is deliberately omitted — the exact Docusaurus slug isn't in the docs and auto-detection already handles it. Note there is no Node version property in vercel.json; that is why the pin lives in package.json.

One thing to confirm on the preview deploy: this only takes effect if the Vercel project's Root Directory is website (near-certain, since there is no root package.json).

Dependency bumps: none needed

@docusaurus/* is already at 3.10.2, which is the latest release. yarn outdated only flagged react/react-dom 19.2.0 → 19.2.8, already inside the existing ^19.2.0 range — left to dependabot.

The second commit refreshes caniuse-lite via npx update-browserslist-db@latest, collapsing four stale lockfile entries into 1.0.30001809. It reported No target browser changes, and package.json is untouched.

Verification

• yarn build succeeds on Node v24.15.0
• after the lockfile refresh the build emits zero warnings (the caniuse-lite is 21 months old and baseline-browser-mapping notices are gone)
• yarn install --frozen-lockfile — what Vercel runs — reports Already up-to-date, so the lockfile and manifest are consistent

CI does not build the website, so the Vercel preview deploy on this PR is the real check.

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docusaurus-powershell	Ready	Preview	Aug 16, 2026 9:55am