docs: fix filename typo and add Cloudflare Pages deploy details across docs

docs/operations/gitea-cloudflare-pages.md

@@ -6,7 +6,12 @@ Deploy the Linear Void frontend (Vite + TypeScript SPA) from Gitea to Cloudflare
 
 ## Prerequisites
 
-1. **Cloudflare Pages project** created (Dashboard → Workers & Pages → Create → Pages), see [Cloudflare Pages Setup](./cloudflare-pages-setup.md).
+> **Important:** The Pages project must exist before the API deploy call works. You'll get error 8000007 ("Project not found") if you skip this step.
+
+1. **Cloudflare Pages project** created first:
+   - Dashboard → Workers & Pages → Create → Pages → Direct Upload
+   - Name it `linearvoid` (or a different name if `linearvoid` is already taken by a Worker — see note below)
+   - See [Cloudflare Pages Setup](./cloudflare-pages-setup.md) for full details.
 2. **Project name**: note the exact name (e.g., `linearvoid`).
 3. **API token** with Pages permissions:
    - Create at <https://dash.cloudflare.com/profile/api-tokens>
@@ -14,6 +19,8 @@ Deploy the Linear Void frontend (Vite + TypeScript SPA) from Gitea to Cloudflare
    - Store in Gitea → Settings → Secrets as `CLOUDFLARE_API_TOKEN`
 4. **Account ID** from Cloudflare dashboard overview → store as `CLOUDFLARE_ACCOUNT_ID`
 
+> **Naming conflict:** If a Worker already exists with the name `linearvoid`, the Pages project must use a different name (e.g., `linearvoid-site`). Update the `projectName` in the workflow accordingly. Workers and Pages share a namespace under "Workers & Pages".
+
 ## Project-specific values
 
 | Setting            | Value                                                      |
@@ -46,7 +53,7 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v4
         with:
-          node-version: 20
+          node-version: 22
 
       - name: Install dependencies
         run: cd frontend && npm ci
@@ -64,24 +71,50 @@ jobs:
           gitHubToken: ${{ secrets.GITEA_TOKEN }}
 ```
 
-If the `cloudflare/pages-action@v1` action is unavailable from Gitea, use the direct API approach:
+If the `cloudflare/pages-action@v1` action is unavailable from Gitea, use the direct Cloudflare Pages API (multipart/form-data with manifest):
+
+Snippet to generate a manifest in format `-F manifest='{"index.html": "abc123", "style.css": "def456"}'`
+
+```bash
+# Build manifest form argument from all files in frontend/dist
+form_args="-F manifest={"
+for file in $(find frontend/dist -type f | sed 's|^frontend/dist/||'); do
+  hash=$(sha256sum "frontend/dist/$file" | awk '{print $1}')
+  form_args="$form_args\"$file\":\"$hash\","
+done
+form_args="${form_args%,}}" # remove trailing comma and close JSON
+```
 
 ```yaml
-- name: Create deployment artifact
-  run: tar -czf site.tgz -C frontend/dist .
+- name: Generate deployment manifest
+  run: |
+    cd frontend/dist
+    form_args="-F manifest={"
+    for file in $(find . -type f ! -name manifest.json | sed 's|^\./||'); do
+      hash=$(sha256sum "$file" | awk '{print $1}')
+      form_args="$form_args\"$file\":\"$hash\","
+    done
+    form_args="${form_args%,}}" # remove trailing comma and close JSON
+    echo "Form arguments: $form_args"
+    echo "FORM_ARGS=$form_args" >> $GITHUB_ENV
 
 - name: Deploy to Cloudflare Pages
   env:
     CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
     CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
   run: |
+    cd frontend/dist
+    form_args="$FORM_ARGS" # use form arguments generated in previous step
+    COMMIT_HASH=$(git rev-parse --short HEAD 2>/dev/null || echo "unknown")
     curl -sS -X POST \
       "https://api.cloudflare.com/client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/pages/projects/linearvoid/deployments" \
       -H "Authorization: Bearer ${CLOUDFLARE_API_TOKEN}" \
-      -H "Content-Type: application/octet-stream" \
-      --data-binary @site.tgz
+      -F "commit_hash=${COMMIT_HASH}" \
+      $form_args
 ```
 
+This matches the Cloudflare Pages Direct Upload API: `Content-Type: multipart/form-data`, each file as a separate form field, and a `manifest` JSON mapping filenames to SHA-256 hashes.
+
 ## Secrets to add in Gitea
 
 | Secret                  | Value                                |
@@ -102,8 +135,10 @@ If the `cloudflare/pages-action@v1` action is unavailable from Gitea, use the di
 - Multi-page SPA (`vite.config.ts`) produces three entry points — Cloudflare Pages serves them correctly.
 - For SPA fallback routing, add a `frontend/public/_redirects` file with `/* /index.html 200` before building.
 - If deployments fail with 403, verify the API token has `Account → Cloudflare Pages → Edit` permission.
+- If you get error **8000007** ("Project not found"), the Pages project hasn't been created yet. Create it via the Cloudflare dashboard (Workers & Pages → Create → Pages → Direct Upload) first, then re-run.
+- If `linearvoid` is already taken by a Worker, use a different project name like `linearvoid-site` and update the `projectName` and `PROJECT_NAME` values in the workflow.
 
 ## Related resources
 
-- Cloudflare Workers dashboard: `https://dash.cloudflare.com/{accountId}/workers/services/view/linearvoid/production/settings` — for managing the `infrastructure/cloudflare/worker.js` deployment
-- Cloudflare Pages project: `https://dash.cloudflare.com/{accountId}/pages/view/linearvoid` — deployment history and custom domain settings
+- Cloudflare Workers dashboard: `https://dash.cloudflare.com/deb11491c54ec53a24772e98ac6d8128/workers/services/view/linearvoid/production/settings` — for managing the `infrastructure/cloudflare/worker.js` deployment
+- Cloudflare Pages project: `https://dash.cloudflare.com/deb11491c54ec53a24772e98ac6d8128/pages/view/linearvoid` — deployment history and custom domain settings