Move BikeGPX processing off-device and add FIT support

.github/workflows/deploy-pages.yml → .github/workflows/deploy-worker.yml

@@ -1,4 +1,4 @@
-name: Deploy GitHub Pages
+name: Deploy Worker
 
 on:
   workflow_run:
@@ -12,20 +12,20 @@ on:
 
 permissions:
   contents: read
-  pages: write
   pull-requests: read
-  id-token: write
 
 concurrency:
-  group: pages
+  group: production-worker
   cancel-in-progress: false
 
 jobs:
-
-  build:
-    name: Build site
+  deploy:
+    name: Deploy Worker
     if: github.event_name == 'workflow_dispatch' || github.event.workflow_run.conclusion == 'success'
     runs-on: ubuntu-latest
+    environment:
+      name: production
+      url: https://ridecontrol.xyz
     steps:
       - name: Check out verified revision
         uses: actions/checkout@v7
@@ -35,8 +35,6 @@ jobs:
         uses: oven-sh/setup-bun@v2
         with:
           bun-version: latest
-      - name: Set up GitHub Pages
-        uses: actions/configure-pages@v6
       - name: Install dependencies
         run: bun install --frozen-lockfile
       - name: Resolve build metadata
@@ -50,21 +48,11 @@ jobs:
             build_pr_url="https://github.com/${GITHUB_REPOSITORY}/pulls?q=is%3Apr+is%3Aclosed"
           fi
           echo "VITE_BUILD_PR_URL=${build_pr_url}" >> "$GITHUB_ENV"
-      - name: Build site
+      - name: Build Worker
         run: bun run build
-      - name: Upload site artifact
-        uses: actions/upload-pages-artifact@v5
+      - name: Deploy Worker
+        uses: cloudflare/wrangler-action@v3
         with:
-          path: dist
-
-  deploy:
-    name: Deploy site
-    needs: build
-    runs-on: ubuntu-latest
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
-    steps:
-      - name: Deploy to GitHub Pages
-        id: deployment
-        uses: actions/deploy-pages@v5
+          accountId: c1e6e1378d9461aa07039950b1bf8b89
+          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
+          command: deploy

.gitignore

@@ -1,3 +1,7 @@
 node_modules/
 dist/
+.wrangler/
+.dev.vars
+.dev.vars.*
+!.dev.vars.example
 .DS_Store

AGENTS.md

@@ -1,6 +1,7 @@
 # Project instructions
 
 - After making any changes, always run `bun run ci` before handing work back.
+- Run `bun run ci` again immediately before every push, and do not push unless it passes for the exact commit being pushed. While GitHub Actions is unavailable, local CI is the required merge gate; do not wait for a GitHub Actions status check to merge.
 - `bun run ci` must run the Ultracite-configured Biome checks and Tailwind CSS language-server diagnostics automatically, followed by the unit tests, TypeScript check, and production build.
 - Fix all reported issues rather than bypassing or disabling checks unless the project requirements explicitly demand an exception.
 - Keep the codebase as DRY as practical: before adding constants, calculations, formatting, parsing, labels, or state-derivation logic, search for an existing domain utility and reuse or extend it. Consolidate meaningful duplication into clearly named domain modules, but do not introduce generic abstractions that hide simple behavior or couple unrelated concepts solely because their implementations look similar.
@@ -14,6 +15,6 @@
 - When the user says "add, commit", group all existing changes into logical sets, stage and commit each group, and repeat until every change is committed and the working tree is clean.
 - At the start of every new work request, check the current Git branch before changing files. If the current branch is `main`, create and switch to a descriptively named task branch first.
 - Never push work directly to `main`. If `main` already contains uncommitted changes or commits that have not been pushed, create the task branch from its current state so all of that work moves forward on the new branch, then continue the normal workflow there.
-- When the user says "add, commit, push, pr, merge" or otherwise confirms that the work is ready, complete the delivery workflow in order: group and commit all changes until the tree is clean, push the task branch, open a pull request targeting `main`, wait for required checks to pass, and merge the pull request. If checks fail or the pull request cannot merge, fix the problem on the same task branch and repeat the relevant steps.
+- When the user says "add, commit, push, pr, merge" or otherwise confirms that the work is ready, complete the delivery workflow in order: group and commit all changes until the tree is clean, run `bun run ci` for the exact commit being delivered, push the task branch, open a pull request targeting `main`, and merge the pull request without depending on GitHub Actions while it is unavailable. If local CI fails or the pull request cannot merge, fix the problem on the same task branch and repeat the relevant steps.
 - Keep React component modules compatible with Vite Fast Refresh: export only React components from component files, and move non-component runtime exports such as constants, helpers, and metadata into separate modules to avoid incompatible-export invalidations.
 - Record every new user-facing feature in the README as part of implementing it.