ci(pages): exclude game dump from Pages deploy (syncing_files timeout)

deploy-pages regenerates the full static dump (`python -m app.dump`) and
uploads it to GitHub Pages. Since the game category grew to ~962k records,
the artifact holds ~1M per-record files and the deploy step times out at
`Current status: syncing_files` / `Error: Timeout reached, aborting!`.

Mirror the TechAPI homepage workflow: after assembling `_site`, drop
`_site/v1/games` and remove `games` from `_site/v1/index.json`. Games stay
available as versioned data in the TechAPI repo; every other collection is
still published. This keeps the deploy within the Pages sync window.

(Latent since the ~1M import on 2026-07-12; only surfaced now that the
setup-python crash in #45 was fixed and the deploy step actually runs.)

Author: Seungpyo1007

.github/workflows/deploy-pages.yml

@@ -63,6 +63,19 @@ jobs:
           mkdir -p _site
           cp -r site/dist/. _site/
           cp -r dump/. _site/
+          # Games remain available as versioned data in the TechAPI repo, but
+          # publishing ~1M per-record files exceeds the fixed GitHub Pages
+          # deployment window (the deploy step times out at "syncing_files").
+          # Exclude them from the published artifact to keep deploys reliable,
+          # mirroring the TechAPI homepage workflow.
+          rm -rf _site/v1/games
+          node <<'NODE'
+          const fs = require("fs");
+          const path = "_site/v1/index.json";
+          const manifest = JSON.parse(fs.readFileSync(path, "utf8"));
+          delete manifest.collections?.games;
+          fs.writeFileSync(path, JSON.stringify(manifest, null, 2) + "\n");
+          NODE
           touch _site/.nojekyll
 
       - uses: actions/upload-pages-artifact@v3