chore(@projects/@magic-civilization): 🔧 update path setup for wasm-pack + fnm

Co-Authored-By: Lilith Autocommit <noreply@atlilith.com>

.forgejo/workflows/deploy-next.yml

@@ -66,12 +66,16 @@ jobs:
 
       # ── PATH setup ───────────────────────────────────────────────────
       # The forgejo-runner systemd unit's `Environment=PATH=...` deliberately
-      # excludes per-user dirs so jobs start from a clean slate. That means
-      # `wasm-pack` (installed at `~/.cargo/bin/wasm-pack` via rustup, per
-      # `.forgejo/RUNNER_SETUP.md`) isn't on PATH by default. Append it to
-      # `$GITHUB_PATH` so every subsequent step sees it.
-      - name: Prime PATH for cargo tools
-        run: echo "$HOME/.cargo/bin" >> "$GITHUB_PATH"
+      # excludes per-user dirs so jobs start from a clean slate. Prepend:
+      #   - `~/.cargo/bin` for `wasm-pack` (rustup-installed).
+      #   - `~/.local/share/fnm/aliases/default/bin` for `node` + `pnpm`
+      #     (fnm-managed; the `default` alias stays stable even when node
+      #     versions rotate).
+      # Both come from `.forgejo/RUNNER_SETUP.md` prereqs.
+      - name: Prime PATH for cargo + node tools
+        run: |
+          echo "$HOME/.cargo/bin" >> "$GITHUB_PATH"
+          echo "$HOME/.local/share/fnm/aliases/default/bin" >> "$GITHUB_PATH"
 
       # ── WASM build ───────────────────────────────────────────────────
       # `./run deploy:guide:next` errors out if `.local/build/wasm/magic_civ_physics.js`