Rename production build workflow wording

Author: Jake Fitzgerald

.claude-plugin/marketplace.json

@@ -7,13 +7,13 @@
     "description": "CAD, robotics, fabrication, and local review plugins."
   },
   "description": "CAD, robotics, fabrication, and local review plugins.",
-  "version": "0.1.13",
+  "version": "0.1.14",
   "plugins": [
     {
       "name": "cad",
       "source": "./plugins/cad",
       "description": "CAD, robotics, fabrication, and local review skills.",
-      "version": "0.1.13",
+      "version": "0.1.14",
       "author": {
         "name": "earthtojake"
       },

…hub/workflows/materialize-build-test.yml .github/workflows/build-test-branch.yml.github/workflows/materialize-build-test.yml renamed to .github/workflows/build-test-branch.yml .github/workflows/materialize-build-test.yml renamed to .github/workflows/build-test-branch.yml

@@ -1,4 +1,4 @@
-name: Materialize Build Test
+name: Build Test Branch
 
 on:
   push:
@@ -11,12 +11,12 @@ permissions:
   contents: write
 
 concurrency:
-  group: materialize-build-test
+  group: build-test-branch
   cancel-in-progress: false
 
 jobs:
-  materialize:
-    name: Materialize build-test
+  build-test:
+    name: Build build-test
     runs-on: ubuntu-latest
 
     steps:
@@ -81,23 +81,23 @@ jobs:
       - name: Create local build-test branch
         run: git checkout -B build-test "$GITHUB_SHA"
 
-      - name: Materialize generated outputs
+      - name: Build production outputs
         run: scripts/build.sh --clean
 
-      - name: Validate materialized layout
-        run: scripts/check/check-materialized.sh
+      - name: Validate production build layout
+        run: scripts/check/check-builds.sh
 
       - name: Run code tests
         run: scripts/test.sh
 
-      - name: Commit materialized outputs
+      - name: Commit build artifacts
         id: commit
         run: |
           git config user.name "github-actions[bot]"
           git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
           git add -A
           if git diff --cached --quiet; then
-            echo "No materialized output changes to commit."
+            echo "No build artifact changes to commit."
             echo "committed=false" >> "$GITHUB_OUTPUT"
             exit 0
           fi

.github/workflows/check-builds.yml

@@ -35,5 +35,5 @@ jobs:
           npm ci --prefix packages/cadjs
           npm ci --prefix viewer
 
-      - name: Check materialized build outputs
-        run: scripts/check/check-materialized.sh
+      - name: Check production build outputs
+        run: scripts/check/check-builds.sh

AGENTS.md

@@ -45,7 +45,7 @@ product and `models/` as the shared fixture/artifact area.
   one-off, or local-only helper scripts there; use `tmp/` or `/tmp` instead.
 - `viewer/`, `packages` are the source of truth for CAD Viewer and shared CAD runtime behavior. Duplicate files under skills such as `skills/cad-viewer/scripts/viewer`, `skills/cad-viewer/scripts/packages/`, `skills/cad/scripts/packages/`, and snapshot runtimes are generated copies that should not be edited.
 - When changing skill behavior that uses `packages/cadjs`, `packages/cadpy`, or `skills/cad-viewer/scripts/viewer`, edit the root source in `packages/*` or `viewer/*`, then rebuild the generated skill copies. Never patch the copies as the lasting fix.
-- `plugins/cad/skills/` is a generated, materialized plugin package copy of
+- `plugins/cad/skills/` is a generated production plugin package copy of
   the root `skills/` sources. Edit `skills/*` first, then run
   `scripts/build/build-plugin.sh` to refresh the plugin copy; do not hand-edit
   plugin skill copies.
@@ -59,7 +59,7 @@ product and `models/` as the shared fixture/artifact area.
 - Keep release versioning in lockstep: the git tag, plugin manifests and
   `plugins/*/VERSION`, package manifests/locks, Python `pyproject.toml` files,
   and any other repo-owned release version numbers should all match. The
-  current release version is `0.1.13`. Use `scripts/release/bump-version.sh`
+  current release version is `0.1.14`. Use `scripts/release/bump-version.sh`
   for version bumps as described in `COMMIT.md`.
 
 ## Environments

COMMIT.md

@@ -146,5 +146,5 @@ scripts/check-version.sh --incremented-from origin/main
 Use `--amend` when the version bump belongs in the current commit. Use
 `--no-commit` when you need to combine the bump with other staged work or when
 resolving a rebase conflict manually. Create and push release tags only from a
-materialized release branch when the user or release workflow explicitly asks
+production release branch when the user or release workflow explicitly asks
 for tags to be published.

CONTRIBUTING.md

@@ -7,7 +7,7 @@ fixture/artifact area.
 ## Local Checkout
 
 For production use, clone `main`; it is the installable branch with
-materialized skill and plugin outputs. For development, branch from `dev` and
+generated skill and plugin outputs. For development, branch from `dev` and
 open PRs back to `dev`:
 
 ```bash
@@ -174,27 +174,27 @@ scripts/check-version.sh --incremented-from origin/dev
 ```
 
 `build-test` and release branches must be installable from a plain checkout, so
-they contain materialized generated outputs instead of symlinks:
+they contain generated production outputs instead of symlinks:
 
 ```bash
 scripts/build.sh --clean
 scripts/build.sh --check
 ```
 
-The build-test automation materializes `dev`, validates the built layout, and
+The build-test automation builds `dev`, validates the production layout, and
 pushes the generated result to `build-test`.
 
 PRs opened against `dev` must keep release metadata consistent and incremented
-from their `dev` base. The `dev` to `build-test` materializer also checks that
+from their `dev` base. The `dev` to `build-test` release builder also checks that
 the `dev` release version is greater than `main` before it builds and pushes
-the materialized branch.
+the production-build branch.
 
 If the repository has a `BUILD_TEST_PUSH_TOKEN` Actions secret, the
-materializer uses it for the `build-test` push so that push-triggered checks run
+release builder uses it for the `build-test` push so that push-triggered checks run
 on `build-test`. Without that secret, the workflow falls back to
 `GITHUB_TOKEN` and explicitly dispatches the `build-test` checks after pushing.
-In both cases, the materializer validates the generated layout before it pushes.
-Once this flow is trusted, the materializer target will change from `build-test`
+In both cases, the release builder validates the generated layout before it pushes.
+Once this flow is trusted, the release builder target will change from `build-test`
 to `main`, and production users should continue cloning `main`.
 
 ## Iteration Loop

README.md

@@ -59,7 +59,7 @@ robot description files, simulation, and local review.
 ## 💻 Installation
 
 For production use, install or clone from `main`; that branch contains the
-materialized skill/plugin outputs needed by provider installers.
+generated skill/plugin outputs needed by provider installers.
 
 ### Skills
 

docs/package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "cad-skills-docs",
-  "version": "0.1.13",
+  "version": "0.1.14",
   "license": "MIT",
   "private": true,
   "scripts": {