Merge pull request #525 from bcorfman/devlogin

Add dev cloud persistence back in

Author: bcorfman

.github/workflows/deploy-frontend-pages.yml

@@ -67,7 +67,7 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v7
         with:
-          node-version: 26
+          node-version: 24
 
       - name: Install
         run: npm ci
@@ -77,6 +77,7 @@ jobs:
 
       - name: Build dev channel
         env:
+          VITE_PHASERFORGE_ENABLE_DEV_CLOUD_PERSISTENCE: '1'
           VITE_API_BASE_URL: ${{ vars.VITE_API_BASE_URL_DEV }}
           VITE_PHASERFORGE_DEPLOY_CHANNEL: dev
           VITE_E2E_TEST_BRIDGE: '1'

.plans/railway-stable-dev-deployment-plan-2026-07-18.md

@@ -68,7 +68,7 @@ Goal: create a working dev backend without changing stable behavior.
 - [x] Attach a separate development Postgres database.
 - [x] Configure development-only values for `PUBLIC_BASE_URL`, `FRONTEND_BASE_URL`, `CORS_ALLOW_ORIGINS`, `COOKIE_SAMESITE`, `COOKIE_SECURE`, `TRUST_PROXY`, session settings, and OAuth callback URLs.
 - [x] Use separate GitHub OAuth credentials/app callback configuration if GitHub login is enabled in development.
-- [ ] Run migrations against the empty development database.
+- [x] Run migrations against the empty development database.
 - [ ] Verify `/api/v1/health`, auth, session persistence, CSRF, CORS, and basic cloud-game CRUD against the dev service.
 - [ ] Confirm no development request can resolve to the stable database or stable OAuth callback.
 - [x] Configure the development Railway service's source/ref and environment-specific variables in the dashboard; keep shared build/start/health behavior in `railway.toml`.