fix(ci): increase memory for production build

Use the 64 GB Blacksmith runner after repeated shutdowns during Next.js static generation on the 32 GB build worker.

Author: Bill Leoutsakos

.github/workflows/test-build.yml

@@ -226,11 +226,11 @@ jobs:
   # harmless), but the Turbo cache gets its own key: with a shared key, only
   # the last committer's new entries survive each run, so the test and build
   # Turbo entries would evict each other nondeterministically.
-  # Same next build as the app image, so it needs the same larger runner in
-  # GitHub mode: it peaks ~21.9 GB and SIGKILLs on the free 16 GB ones.
+  # Next static generation can exceed 32 GB on large app/docs diffs, so use the
+  # 64 GB Blacksmith runner; GitHub mode already uses the largest hosted option.
   build:
     name: Build App
-    runs-on: ${{ (vars.CI_PROVIDER == '' || vars.CI_PROVIDER == 'blacksmith') && 'blacksmith-8vcpu-ubuntu-2404' || 'linux-x64-8-core' }}
+    runs-on: ${{ (vars.CI_PROVIDER == '' || vars.CI_PROVIDER == 'blacksmith') && 'blacksmith-16vcpu-ubuntu-2404' || 'linux-x64-8-core' }}
     timeout-minutes: 15
 
     steps: