added starlight deployment

Author: adrum

.github/workflows/deploy-starlight.yml

@@ -0,0 +1,89 @@
+name: Deploy Starlight docs to Cloudflare
+
+on:
+  push:
+    branches: [3.x]
+    # Only run when something the build actually consumes changes —
+    # avoids re-deploying when the legacy docusaurus tree or unrelated
+    # repo files are touched.
+    paths:
+      - "starlight/**"
+      - "v1/**"
+      - "v2/**"
+      - "v3/**"
+      - "snippets/**"
+      - "images/**"
+      - "assets/**"
+      - "mp4/**"
+      - "fonts/**"
+      - "favicon.svg"
+      - ".github/workflows/deploy-starlight.yml"
+  # Manual trigger from the Actions tab.
+  workflow_dispatch:
+
+# Cancel any in-flight deploy when a newer commit lands on main.
+concurrency:
+  group: deploy-starlight
+  cancel-in-progress: true
+
+jobs:
+  deploy:
+    name: Build & deploy
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      deployments: write
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - name: Set up Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: pnpm
+          cache-dependency-path: starlight/pnpm-lock.yaml
+
+      - name: Install dependencies
+        working-directory: starlight
+        run: pnpm install --frozen-lockfile
+
+      - name: Build site
+        working-directory: starlight
+        run: pnpm build
+
+      - name: Inject Cloudflare route into wrangler.toml
+        # wrangler.toml ships without a [[routes]] block because wrangler
+        # doesn't interpolate env vars there. Append one from repo vars
+        # so the same file works for local *.workers.dev deploys and for
+        # zone-bound CI deploys without a code change.
+        if: vars.CF_ROUTE_PATTERN != '' && vars.CF_ZONE_NAME != ''
+        working-directory: starlight
+        env:
+          CF_ROUTE_PATTERN: ${{ vars.CF_ROUTE_PATTERN }}
+          CF_ZONE_NAME: ${{ vars.CF_ZONE_NAME }}
+        run: |
+          {
+            echo ""
+            echo "[[routes]]"
+            echo "pattern = \"${CF_ROUTE_PATTERN}\""
+            echo "zone_name = \"${CF_ZONE_NAME}\""
+          } >> wrangler.toml
+          echo "--- wrangler.toml route block ---"
+          tail -4 wrangler.toml
+
+      - name: Deploy to Cloudflare Workers
+        uses: cloudflare/wrangler-action@v3
+        with:
+          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
+          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
+          workingDirectory: starlight
+          # wrangler reads ./wrangler.toml from workingDirectory and uses
+          # the [assets] block to upload ./dist.
+          command: deploy

starlight/wrangler.toml

@@ -0,0 +1,48 @@
+#:schema node_modules/wrangler/config-schema.json
+
+# Cloudflare Worker config for the Starlight docs build.
+#
+# Deployment model: Workers Static Assets (no Worker script needed).
+# Wrangler uploads `./dist` and serves it directly. Because every page
+# the build produces lives under `/docs/...` (the splash at /docs/, all
+# versioned content at /docs/v1/, /docs/v2/, /docs/v3/), this Worker
+# slots cleanly into a `/docs/*` route on a parent zone.
+#
+# Build first:    pnpm --filter starlight build
+# Deploy:         npx wrangler deploy
+# Local preview:  npx wrangler dev
+#
+# To mount on the /docs/* subpath of an existing zone, uncomment the
+# [[routes]] block below and replace the pattern + zone_name with your
+# domain. Without routes, the Worker is reachable at its
+# *.workers.dev URL.
+
+name = "inertiacore-docs"
+compatibility_date = "2026-04-13"
+
+# Workers Static Assets — points at the Astro build output.
+# `not_found_handling = "404-page"` makes Cloudflare serve dist/404.html
+# for unmatched paths, which Starlight already generates.
+[assets]
+directory = "./dist"
+not_found_handling = "404-page"
+
+# Route binding lives in CI, not here.
+#
+# Wrangler does not interpolate environment variables inside
+# `[[routes]]` blocks, so this file ships without one. The deploy
+# workflow appends a `[[routes]]` block from the `CF_ROUTE_PATTERN` and
+# `CF_ZONE_NAME` GitHub Actions repository variables before running
+# `wrangler deploy` — see .github/workflows/deploy-starlight.yml.
+#
+# Without a route, `wrangler deploy` puts this Worker on its
+# *.workers.dev URL, which is fine for local smoke-testing via
+# `npx wrangler deploy` or `npx wrangler dev`.
+
+# Optional: separate dev/staging environment with its own subdomain.
+#
+# [env.staging]
+# name = "inertiacore-docs-staging"
+# [env.staging.assets]
+# directory = "./dist"
+# not_found_handling = "404-page"