fix(ci): use npm run build directly in CI workflows to always produce full site build

The deploy and preview CI workflows were calling `make clean`, a developer
convenience Makefile target whose recipe has changed several times:
- Previously ran `gatsby clean && make site` which launched `gatsby develop:lite`
  (a lite/dev build that EXCLUDES blog, news, events, and resources collections)
  or failed with "gatsby: not found" because gatsby is not globally installed in CI.
- Was later patched to `npm run clean && make build`, but this dependency on
  a mutable Makefile target is fragile and has already caused multiple production
  outages where blog posts (and other collections) were missing from the site.

Fix: call `npm run build` directly in both workflow files.
`npm run build` is defined in package.json as:
  cross-env BUILD_FULL_SITE=true gatsby build
This is the canonical, stable production build command and always includes
all collections. It cannot be accidentally changed to a lite build.

Also clarifies the Makefile `clean` target comment to note it is for local
developer use only; CI should not rely on it.

Author: leecalcote

.github/workflows/build-and-deploy-site.yml

@@ -28,10 +28,18 @@ jobs:
       #     restore-keys: |
       #       ${{ runner.os }}-gatsby-
 
-      - name: Install and Build 🔧
-        run: |
-          make setup
-          make clean
+      - name: Install 🔧
+        run: make setup
+
+      - name: Build 🏗️
+        # Always run the full production build explicitly.
+        # Do NOT use `make clean` here — that target is a developer convenience
+        # command whose recipe has changed multiple times, causing blog posts and
+        # other collections to be silently excluded from the deployed site when
+        # it ran a lite/dev build instead of the full production build.
+        # `npm run build` is the canonical, stable production build command:
+        #   cross-env BUILD_FULL_SITE=true gatsby build
+        run: npm run build
 
       - name: Deploy 🚀
         uses: JamesIves/github-pages-deploy-action@v4

.github/workflows/build-and-preview-site.yml

@@ -14,10 +14,18 @@ jobs:
           persist-credentials: false
           fetch-depth: 1
 
-      - name: Install and Build 🔧
-        run: |
-          make setup
-          make clean
+      - name: Install 🔧
+        run: make setup
+
+      - name: Build 🏗️
+        # Always run the full production build explicitly.
+        # Do NOT use `make clean` here — that target is a developer convenience
+        # command whose recipe has changed multiple times, causing blog posts and
+        # other collections to be silently excluded from the deployed site when
+        # it ran a lite/dev build instead of the full production build.
+        # `npm run build` is the canonical, stable production build command:
+        #   cross-env BUILD_FULL_SITE=true gatsby build
+        run: npm run build
 
       - name: Broken Link Check 🔗
         uses: technote-space/broken-link-checker-action@v2

Makefile

@@ -39,8 +39,8 @@ site-fast:
 build:
 	npm run build
 
-## Empty build cache and run layer5.io on your local machine.
-clean: 
+## Empty build cache and rebuild layer5.io on your local machine (developer use only; CI uses `npm run build` directly).
+clean:
 	npm run clean && make build
 
 ## Run Eslint on your local machine.