[adrienlacombe]

Turns the Vercel project behind get-starknet.starknet-react.com into a permanent redirect to https://starknet-io.github.io/get-starknet, so existing links keep working after the move to GitHub Pages (#348).

The Pages site is live

Checked just before opening this PR:

• Pages: the API reports build_type: workflow, status: built, HTTPS enforced. The Docs push run for 371838d succeeded.
• Live URLs: /get-starknet/, /get-starknet/llms.txt and /get-starknet/getting-started.md (text/markdown) return 200. /get-starknet/getting-started 301s to its trailing-slash URL.

Change

Only vercel.json:

• Redirect: every path goes to the same path under the new URL with a 308 ("source": "/:path(.*)", "permanent": true).
• No build: framework: null (Vercel's "Other" preset), and installCommand: "" skips the install, as Vercel's docs describe.
• Placeholder output: the build only writes a one-line dist/index.html. Vercel rejects an empty output directory (STATIC_BUILD_EMPTY_OUT_DIR), and the catch-all redirect runs before any file is served, so the placeholder never shows.

Verification

• vercel build (Vercel CLI 65.7.0) on a copy of this branch, with a placeholder project link and no login. It succeeds without installing dependencies. The generated routing is one 308 rule (^(?:/(.*))$ → https://starknet-io.github.io/get-starknet/$1) that runs before any file lookup.
• That rule on sample paths:
  • / → /get-starknet/
  • /getting-started and /getting-started/ → the same path under /get-starknet/
  • /core/createStore, /demo/ui, /llms.txt, /getting-started.md → the same path under /get-starknet/
  • Encoded paths (/a%20b) are kept as-is.
• Before switching to /:path(.*): the first version used /:path*, which didn't match / or trailing-slash paths. vercel build also rejected an empty output directory. Both are fixed here.

⚠️ Check that Vercel still deploys from master

get-starknet.starknet-react.com still serves the vocs 1 build (last-modified: 18:43 UTC), although #347 and #348 merged at 19:15 and 19:17 UTC. Vercel posts no status on this repo's commits, so from GitHub I can't tell whether its builds of those merges failed or its Git integration no longer deploys master.

Someone with access to the starknet-react.com Vercel account needs to:

1. Check the project's latest deployments.
2. After this merges, confirm that https://get-starknet.starknet-react.com/getting-started returns a 308 to the new URL, redeploying if needed.

Outside this PR

• The redirect works only while the Vercel project and the domain stay attached, so keep the project; it now only serves redirects.
• To retire it completely later, delete the project and the DNS record, then remove vercel.json and the .vercel line in .gitignore. Old links stop working at that point.

🤖 Generated with Claude Code