Sans-IO engine and harness product

.cursor/rules/workshop-spa.mdc

@@ -1,21 +1,22 @@
 ---
 description: Workshop SPA conventions - feature directories, barrel exports, lazy loading, CSS colocation, token-only values
-globs: crates/workshop-server/ui/**
+globs: crates/workshop/ui/**
 alwaysApply: false
 ---
 
 # Workshop SPA Conventions
 
 ## Feature directories and lazy loading
 
-- Feature-based directories under `ui/` (`ui/agent/`, `ui/editor/`, `ui/layout/`, `ui/menu/`, `ui/take/`, `ui/stt/`, `ui/chrome/`, `ui/status/`, `ui/workspace/`, `ui/gateway/`). Shared code lives in `services/` or `base/`; shared UI assets (boot-loaded icons) live in `ui/shared/`; design tokens live in `tokens/`.
+- The package at `crates/workshop/ui/` is a sibling of the `crates/workshop/server/` crate that builds and serves it. `src/` has three layers: `base/` (lifecycle, events, paths, the `WorkshopPart` base class), `services/` (DOM-free registries and services), and `parts/` (feature directories; every panel extends `base/workshop-part.ts`).
+- Feature-based directories under `parts/` (`parts/agent/`, `parts/editor/`, `parts/layout/`, `parts/menu/`, `parts/take/`, `parts/stt/`, `parts/chrome/`, `parts/status/`, `parts/workspace/`, `parts/gateway/`). Shared code lives in `services/` or `base/`; shared UI assets (boot-loaded icons) live in `parts/shared/`; design tokens live in `tokens/`.
 - Barrel exports: every directory has an `index.ts`. Lazy directories export `register()` installing commands, menu items, panel factories, and socket subscriptions.
 - The boot shell (`main.ts`, `services/`, `base/`) loads immediately. Feature directories load via dynamic `import()` on first activation. Lazy-loaded panels never import the boot shell.
 - Registration, not central wiring: panel types, menu items, services, socket handlers, keyboard shortcuts, and lifecycle disposal self-register through the panel, menu/command, and service registries.
 
 ## CSS colocation and tokens
 
-- CSS lives beside its TypeScript, imported as a side-effect. Never a separate `styles/` tree. Every feature directory is self-contained: `.ts`, `.css`, and `index.ts` together. A designer finds the styles for the agent chat at `ui/agent/agent-session.css`, not by grepping a flat directory.
+- CSS lives beside its TypeScript, imported as a side-effect. Never a separate `styles/` tree. Every feature directory is self-contained: `.ts`, `.css`, and `index.ts` together. A designer finds the styles for the agent chat at `parts/agent/agent-session.css`, not by grepping a flat directory.
 - No raw color, size, or spacing values in component CSS. Use `--ws-*` tokens from `tokens/`. Primitives go in `tokens/base.css`, intent aliases in `tokens/semantic.css`, per-component overrides in `tokens/component.css`. A designer themes the app by editing `semantic.css`.
 - CSS classes use the `.ws-` project prefix (`.ws-agent-toolbar`). Design tokens use the `--ws-` prefix (`--ws-color-bg-surface`).
 - Directories and files are kebab-case (`agent-session-view.ts`, `agent-session.css`).

.gitattributes

@@ -9,10 +9,10 @@
 # The UI sources are bundled by esbuild; CRLF conversion on Windows
 # checkouts would change bundle bytes between platforms.
 crates/gateway/config-ui/ui/** text eol=lf
-crates/workshop/server/ui/** text eol=lf
+crates/workshop/ui/** text eol=lf
 # Images are not text; the blanket rules above must not convert them.
 crates/gateway/config-ui/ui/**/*.png binary
-crates/workshop/server/ui/**/*.png binary
+crates/workshop/ui/**/*.png binary
 # The event-log schema canary pins the version-1 file exactly as the log
 # writer emits it (LF); autocrlf must not rewrite it on Windows checkouts.
 crates/workshop/server/tests/it/observer/*.jsonl text eol=lf

.github/workflows/ci.yml

@@ -41,11 +41,10 @@ jobs:
           cache-dependency-path: |
             crates/*/ui/package-lock.json
             crates/gateway/*/ui/package-lock.json
-            crates/workshop/*/ui/package-lock.json
 
       - name: Install UI dependencies
         run: |
-          npm ci --prefix crates/workshop/server/ui
+          npm ci --prefix crates/workshop/ui
           npm ci --prefix crates/gateway/config-ui/ui
 
       - name: Build Gateway without Workshop UI tooling
@@ -90,11 +89,10 @@ jobs:
           cache-dependency-path: |
             crates/*/ui/package-lock.json
             crates/gateway/*/ui/package-lock.json
-            crates/workshop/*/ui/package-lock.json
 
       - name: Install UI dependencies
         run: |
-          npm ci --prefix crates/workshop/server/ui
+          npm ci --prefix crates/workshop/ui
           npm ci --prefix crates/gateway/config-ui/ui
 
       - name: Test (concurrent via nextest)
@@ -136,11 +134,10 @@ jobs:
           cache-dependency-path: |
             crates/*/ui/package-lock.json
             crates/gateway/*/ui/package-lock.json
-            crates/workshop/*/ui/package-lock.json
 
       - name: Install UI dependencies
         run: |
-          npm ci --prefix crates/workshop/server/ui
+          npm ci --prefix crates/workshop/ui
           npm ci --prefix crates/gateway/config-ui/ui
 
       - name: Docs
@@ -168,11 +165,10 @@ jobs:
           cache-dependency-path: |
             crates/*/ui/package-lock.json
             crates/gateway/*/ui/package-lock.json
-            crates/workshop/*/ui/package-lock.json
 
       - name: Install UI dependencies
         run: |
-          npm ci --prefix crates/workshop/server/ui
+          npm ci --prefix crates/workshop/ui
           npm ci --prefix crates/gateway/config-ui/ui
 
       - name: Build featureless Gateway
@@ -250,11 +246,10 @@ jobs:
           cache-dependency-path: |
             crates/*/ui/package-lock.json
             crates/gateway/*/ui/package-lock.json
-            crates/workshop/*/ui/package-lock.json
 
       - name: Install UI dependencies
         run: |
-          npm ci --prefix crates/workshop/server/ui
+          npm ci --prefix crates/workshop/ui
           npm ci --prefix crates/gateway/config-ui/ui
 
       - name: Build featureless Gateway
@@ -303,22 +298,21 @@ jobs:
           cache-dependency-path: |
             crates/*/ui/package-lock.json
             crates/gateway/*/ui/package-lock.json
-            crates/workshop/*/ui/package-lock.json
 
       - name: Install UI dependencies
-        working-directory: crates/workshop/server/ui
+        working-directory: crates/workshop/ui
         run: npm ci
 
       - name: Typecheck
-        working-directory: crates/workshop/server/ui
+        working-directory: crates/workshop/ui
         run: npm run typecheck
 
       - name: Build
-        working-directory: crates/workshop/server/ui
+        working-directory: crates/workshop/ui
         run: npm run build
 
       - name: Test
-        working-directory: crates/workshop/server/ui
+        working-directory: crates/workshop/ui
         run: npm test
 
       - name: Install config UI dependencies

.github/workflows/dist-ci/build-setup.yml

@@ -12,8 +12,7 @@
     cache-dependency-path: |
       crates/*/ui/package-lock.json
       crates/gateway/*/ui/package-lock.json
-            crates/workshop/*/ui/package-lock.json
 - name: Install UI dependencies
-  run: npm ci --prefix crates/workshop/server/ui
+  run: npm ci --prefix crates/workshop/ui
 - name: Install config UI dependencies
   run: npm ci --prefix crates/gateway/config-ui/ui

.github/workflows/llama-cuda-blackwell.yml

@@ -103,7 +103,7 @@ jobs:
           node-version: 22
 
       - name: Install UI dependencies
-        working-directory: crates/workshop/server/ui
+        working-directory: crates/workshop/ui
         run: npm ci
 
       - name: Install config UI dependencies

.github/workflows/nightly.yml

@@ -64,10 +64,9 @@ jobs:
           cache-dependency-path: |
             crates/*/ui/package-lock.json
             crates/gateway/*/ui/package-lock.json
-            crates/workshop/*/ui/package-lock.json
       - name: Install UI dependencies
         run: |
-          npm ci --prefix crates/workshop/server/ui
+          npm ci --prefix crates/workshop/ui
           npm ci --prefix crates/gateway/config-ui/ui
       - name: Build
         run: cargo build --release --locked -p gateway
@@ -98,10 +97,9 @@ jobs:
           cache-dependency-path: |
             crates/*/ui/package-lock.json
             crates/gateway/*/ui/package-lock.json
-            crates/workshop/*/ui/package-lock.json
       - name: Install UI dependencies
         run: |
-          npm ci --prefix crates/workshop/server/ui
+          npm ci --prefix crates/workshop/ui
           npm ci --prefix crates/gateway/config-ui/ui
       - name: Build
         run: cargo build --release --locked -p gateway
@@ -161,10 +159,9 @@ jobs:
           cache-dependency-path: |
             crates/*/ui/package-lock.json
             crates/gateway/*/ui/package-lock.json
-            crates/workshop/*/ui/package-lock.json
 
       - name: Install UI dependencies
-        working-directory: crates/workshop/server/ui
+        working-directory: crates/workshop/ui
         run: npm ci
 
       - name: Install config UI dependencies

.github/workflows/promptforge-gateway-v-release.yml

@@ -143,7 +143,7 @@ jobs:
         with:
           "node-version": 22
       - name: "Install UI dependencies"
-        run: "npm ci --prefix crates/workshop/server/ui"
+        run: "npm ci --prefix crates/workshop/ui"
       - name: "Install config UI dependencies"
         run: "npm ci --prefix crates/gateway/config-ui/ui"
       - name: Install dist

.github/workflows/release-workshop.yml

@@ -115,10 +115,9 @@ jobs:
           cache-dependency-path: |
             crates/*/ui/package-lock.json
             crates/gateway/*/ui/package-lock.json
-            crates/workshop/*/ui/package-lock.json
 
       - name: Install UI dependencies
-        working-directory: crates/workshop/server/ui
+        working-directory: crates/workshop/ui
         run: npm ci
 
       # The gateway sidecar build needs the config UI's esbuild pipeline

.github/workflows/workshop-installer-smoke.yml

@@ -28,7 +28,7 @@ jobs:
           node-version: 22
 
       - name: Install UI dependencies
-        working-directory: crates/workshop/server/ui
+        working-directory: crates/workshop/ui
         run: npm ci
 
       - name: Build featureless Gateway

.gitignore

@@ -14,9 +14,9 @@
 # UI build pipeline: npm install target and the esbuild output. The build
 # scripts write the bundle to OUT_DIR; `npm run build`/`--watch` still write
 # dist/ in place for the jsdom tests, and none of it is tracked.
-/crates/workshop/server/ui/node_modules/
+/crates/workshop/ui/node_modules/
 /crates/gateway/config-ui/ui/node_modules/
-/crates/workshop/server/ui/dist/
+/crates/workshop/ui/dist/
 /crates/gateway/config-ui/ui/dist/
 # tauri-build's generated ACL schemas, regenerated on every workshop build.
 /crates/workshop/shell/gen/

AGENTS.md

@@ -1,6 +1,6 @@
 # PromptForge
 
-Multi-crate Rust workspace for the PromptForge pipeline runtime, inference gateway, and Workshop desktop product.
+Multi-crate Rust workspace for the PromptForge pipeline engine, the harness that hosts it, the inference gateway, and the Workshop desktop product.
 
 ## Principles
 
@@ -17,15 +17,17 @@ Multi-crate Rust workspace for the PromptForge pipeline runtime, inference gatew
 - Workshop is a user-facing agentic development environment: a Tauri desktop application with an HTML/CSS/TypeScript UI
 - PromptForge is the runtime execution engine for the PromptForge Prompting Language: structured Markdown files with live Lua code fences
 - Gateway is an independent service that proxies local and remote inference through one OpenAI-compatible HTTP and WebSocket endpoint
+- Harness is the engine's only production host: it owns the tokio runtime, the performers that carry out the engine's effects, agent sessions, and the run log; Workshop and other clients drive runs through it
 
 ## Structure
 
-- The three main products are PromptForge, Gateway, and Workshop
-- Workshop crates are named workshop-* and must not depend on gateway crates
+- The four main products are PromptForge, Gateway, Workshop, and Harness
+- Workshop crates are named workshop-* and must not depend on gateway crates; workshop crates may name the gateway public pair, the promptforge door, and `harness-api`
 - Gateway's public surface is two root crates, `gateway-api` and `gateway-api-discovery`; everything else lives under crates/gateway/, a manifestless container private to the family - no outside crate may depend into it, and workshop crates may name only the public pair. Gateway crates must not depend on promptforge or workshop crates
 - Workshop crates live under crates/workshop/, a manifestless container private to the family - no outside crate may depend into it; the shell is crates/workshop/shell (package `workshop`), and the server and its subsystems sit beside it with short directory names
-- The composed topology rule: a crate in a family container (crates/promptforge/, crates/gateway/, crates/workshop/) may depend only on crates at the crates/ root and its own siblings; the root is the public layer. Crates named build-* are meta tooling, exempt from container privacy
-- PromptForge crates are named promptforge-* and must not depend on gateway or workshop crates
+- Harness crates are named harness-*. Their public surface is one root crate, `harness-api`; everything else lives under crates/harness/, a fourth manifestless container private to the family, and `harness-api` is its one door - the only outside crate permitted to depend into it. harness-* crates may depend on `promptforge-api-runtime`, `promptforge-api-types`, `gateway-api`, `gateway-api-discovery`, and shared-* crates, never on workshop crates or on a private gateway crate; workshop crates may depend on harness-* only through `harness-api`; promptforge-* and gateway-* crates must not depend on harness crates
+- The composed topology rule: a crate in a family container (crates/promptforge/, crates/gateway/, crates/workshop/, crates/harness/) may depend only on crates at the crates/ root and its own siblings; the root is the public layer. Crates named build-* are meta tooling, exempt from container privacy
+- PromptForge crates are named promptforge-* and must not depend on gateway, workshop, or harness crates
 - PromptForge is one door: crates outside the promptforge-* family may depend only on promptforge-api-runtime and promptforge-api-types, never on the internal promptforge-* substrate crates; the crates under crates/promptforge/ are private to the family, and promptforge-api-runtime is the only outside crate permitted to depend into them
 - The Workshop shell (the `workshop` crate) depends on `workshop-server-api` and never on `workshop-server`; the facade is the shell's entire view of the server
 - Shared crates are named shared-*, contain the public API surface across products and downstream crates, and must not depend on any product crates. PromptForge's own public surface is promptforge-api-runtime and promptforge-api-types, named promptforge-* now that the types crate has left shared-*; Gateway's is gateway-api and gateway-api-discovery, named gateway-* now that both have left shared-*
@@ -54,8 +56,8 @@ Multi-crate Rust workspace for the PromptForge pipeline runtime, inference gatew
 ## Structural Rules
 
 - Dependencies flow one way: shell -> features -> services -> vocabulary. Never add a dependency from a lower tier to a higher one. If Cargo rejects a cycle, the design is wrong, not the graph. On the SPA side, lazy-loaded panels never import the boot shell; shared code lives in services/ or base/.
-- Every workshop-* crate's lib.rs opens with a //! doc carrying a `## Invariants` marker that lists what the crate may depend on and what it may not. Read it before adding an import. Every SPA concern directory (ui/editor/, ui/agent/, etc.) has the same in its index.ts.
-- No file exceeds 500 lines. If an edit would push a file past 500, split first, then edit. `cargo test -p build-xtask` enforces the tier graph, the lint inheritance, the ceiling over the Rust files in the workshop crates carrying the marker, and the product-boundary matrix above (including the one-door rule and the container privacy rules for crates/promptforge/, crates/gateway/, crates/workshop/, and the nested crates/gateway/stt/ subsystem, whose only family-visible crate is gateway-stt) across every workspace manifest; `cargo test -p gateway-stt --test it architecture` checks the same product matrix from cargo metadata; the Tauri shell (the `workshop` crate) is exempt until the headless agent mode plan.
+- Every workshop-* and harness-* crate's lib.rs opens with a //! doc carrying a `## Invariants` marker that lists what the crate may depend on and what it may not. Read it before adding an import. Every SPA concern directory (ui/editor/, ui/agent/, etc.) has the same in its index.ts.
+- No file exceeds 500 lines. If an edit would push a file past 500, split first, then edit. `cargo test -p build-xtask` enforces the tier graph, the lint inheritance, the ceiling over the Rust files in the workshop-* and harness-* crates carrying the marker, and the product-boundary matrix above (including the one-door rules for promptforge and harness and the container privacy rules for crates/promptforge/, crates/gateway/, crates/workshop/, crates/harness/, and the nested crates/gateway/stt/ subsystem, whose only family-visible crate is gateway-stt) across every workspace manifest; `cargo test -p gateway-stt --test it architecture` checks the same product matrix from cargo metadata; the Tauri shell (the `workshop` crate) is exempt until the headless agent mode plan.
 - Source directories are flat by default. A subdirectory of source files must contain at least three files; one or two files belong beside the parent module as `foo-bar.rs` (parent stem, dash, kebab label), wired with an explicit path attribute so the module name stays clean: `#[path = "foo-bar.rs"] mod bar;`. The two forms are convertible in both directions: when a `foo-*.rs` sibling group grows to three files, rehydrate it into a `foo/` subdirectory in standard module layout (`foo/bar.rs` beside `foo.rs`) and drop the path attributes; when a subdirectory shrinks below three files, flatten it back to kebab siblings. Apply whichever conversion applies when you touch files in a group on the wrong side of the line. Top-level `tests/` and `benches/` trees are exempt; they follow Cargo target conventions.
 
 ## SPA and CSS Rules