Fix Pages deploy: use explicit npm install workflow

withastro/action requires a committed lockfile and exits 1 at its
"Check lockfiles" step when none exists. Replace it with setup-node +
`npm install` + upload-pages-artifact so the site builds without a
package-lock.json (which can't be generated until local npm is fixed).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: kunalsuri

.github/workflows/deploy.yml

@@ -24,15 +24,25 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v4
-      - name: Install, build, and upload the site
-        # Official Astro action: detects the package manager, runs the build,
-        # and uploads the Pages artifact. Runs its own Node (default 24) — so
-        # this succeeds regardless of the local machine's toolchain.
-        uses: withastro/action@v3
-        # with:
-        #   path: .              # root of the Astro project
-        #   node-version: 24     # override if needed
-        #   package-manager: npm
+
+      - name: Set up Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: 24
+
+      # Plain `npm install` (not `npm ci`) so this works WITHOUT a committed
+      # package-lock.json. Once local npm is fixed, commit the generated
+      # lockfile and this becomes fully reproducible.
+      - name: Install dependencies
+        run: npm install
+
+      - name: Build site
+        run: npm run build
+
+      - name: Upload Pages artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: ./dist
 
   deploy:
     needs: build