commontoolsinc
diff --git a/‎.github/workflows/deno.yml‎
Lines changed: 7 additions & 0 deletions b/‎.github/workflows/deno.yml‎
Lines changed: 7 additions & 0 deletions
diff --git a/‎deno.json‎
Lines changed: 1 addition & 0 deletions b/‎deno.json‎
Lines changed: 1 addition & 0 deletions
diff --git a/‎docs/specs/recipe-construction/overview.md‎
Lines changed: 5 additions & 0 deletions b/‎docs/specs/recipe-construction/overview.md‎
Lines changed: 5 additions & 0 deletions
diff --git a/‎docs/specs/recipe-construction/recipe-integration-tests.md‎ renamed to ‎docs/specs/recipe-construction/pattern-integration-tests.md‎
Lines changed: 18 additions & 13 deletions b/‎docs/specs/recipe-construction/recipe-integration-tests.md‎ renamed to ‎docs/specs/recipe-construction/pattern-integration-tests.md‎
Lines changed: 18 additions & 13 deletions
diff --git a/‎packages/pattern-tests/deno.json‎
Lines changed: 15 additions & 0 deletions b/‎packages/pattern-tests/deno.json‎
Lines changed: 15 additions & 0 deletions
@@ -118,6 +118,13 @@ jobs:
           API_URL=http://localhost:8000/ \
           deno task integration
 
+      - name: 🧪 Run pattern-tests integration tests
+        working-directory: packages/pattern-tests
+        run: |
+          HEADLESS=1 \
+          API_URL=http://localhost:8000/ \
+          deno task integration
+
   cli-integration-test:
     name: "CLI Integration Tests"
     runs-on: ubuntu-latest
 
@@ -18,6 +18,7 @@
     "./packages/llm",
     "./packages/memory",
     "./packages/patterns",
+    "./packages/pattern-tests",
     "./packages/runner",
     "./packages/seeder",
     "./packages/shell",
 
@@ -1,5 +1,10 @@
 # Recipe Graph Unification Spec
 
+> **Terminology update:** Authored graphs are now referred to as “patterns.”
+> The builder module still exposes helpers like `recipe(...)`, so this spec
+> uses “pattern” when discussing authored artifacts and keeps the API names
+> unchanged.
+
 ## Summary
 
 Unify builder-time `OpaqueRef` proxies and runtime `Cell` objects into a single
 
@@ -1,4 +1,8 @@
-# Recipe Integration Test Harness
+# Pattern Integration Test Harness
+
+> **Terminology update:** What we previously called “recipes” are now referred
+> to as “patterns.” The builder API still exports a `recipe(...)` helper, but
+> throughout this document we describe the authored artifacts as patterns.
 
 ## Objectives
 
@@ -10,11 +14,12 @@
 
 ## Test Artifact Structure
 
-Each recipe test case consists of:
+Each pattern test case consists of:
 
-- **Recipe module**: A `.tsx` or `.ts` file exporting a recipe, lift, or handler.
-- **Fixture file** (proposed `.recipe.test.json` or `.recipe.test.ts`):
-  - `arguments`: Optional initial argument payload (JSON) passed to the recipe.
+- **Pattern module**: A `.tsx` or `.ts` file exporting a pattern, lift, or
+  handler.
+- **Fixture file** (proposed `.pattern.test.json` or `.pattern.test.ts`):
+  - `arguments`: Optional initial argument payload (JSON) passed to the pattern.
   - `initialState`: Optional set of documents/cells to seed before running.
   - `assertions`: Array of checkpoints. Each checkpoint contains:
     - `expect`: A list of `{ path: string, value: JSONValue }` assertions on the
@@ -43,12 +48,12 @@ Example fixture snippet:
 
 ## Harness Execution Flow
 
-1. Compile the recipe module (shared pipeline for V1 and V2).
-2. Run the recipe twice per fixture:
+1. Compile the pattern module (shared pipeline for V1 and V2).
+2. Run the pattern twice per fixture:
    - **V1 mode**: Use current `recipe`/`lift`/`handler` exports.
    - **V2 mode**: Swap in `recipeV2`/`liftV2`/`handlerV2` and new runtime paths.
 3. For each mode:
-   - Instantiate the runtime, seed initial state, run the recipe, and evaluate
+   - Instantiate the runtime, seed initial state, run the pattern, and evaluate
      assertions.
    - For checkpoints with events, emit them sequentially via handler streams and
      re-run assertions after the scheduler settles.
@@ -62,14 +67,14 @@ Example fixture snippet:
 - Provide utilities for referencing cells/streams via friendly syntax (e.g.,
   resolve `result.increment` to the correct link automatically using the stored
   snapshot or capability wrappers).
-- Allow fixtures to specify tolerance for unordered arrays or partial structures
-  when recipes return collections.
+- Allow fixtures to specify tolerance for unordered arrays or partial
+  structures when patterns return collections.
 
 ## Rollout
 
-- Add the harness and fixtures under `packages/runner/integration/` so UI-facing
-  patterns remain focused on front-end rendering scenarios.
-- Seed the suite with high-impact recipes (mirroring those in
+- Add the harness and fixtures under `packages/runner/integration/` so
+  UI-facing patterns remain focused on front-end rendering scenarios.
+- Seed the suite with high-impact patterns (mirroring those in
   `packages/patterns/`) to validate end-to-end behavior.
 - Expand coverage to other workspaces once the harness stabilizes.
 - Keep fixtures mode-agnostic so future migrations (beyond V2) can reuse the
 
@@ -0,0 +1,15 @@
+{
+  "name": "@commontools/pattern-tests",
+  "tasks": {
+    "integration": "LOG_LEVEL=warn deno test --trace-leaks -A ./integration/*.test.ts",
+    "test": "echo 'No tests defined.'"
+  },
+  "lint": {
+    "rules": {
+      "exclude": ["ban-types"]
+    }
+  },
+  "exports": {
+    ".": "./mod.ts"
+  }
+}