Take the Engine and the Harness from runvil-harness

.github/workflows/ci.yml

@@ -96,17 +96,6 @@ jobs:
       - name: Docs
         run: cargo doc --workspace --no-deps --all-features --exclude workshop --exclude workshop-server --exclude workshop-server-api
 
-      # Each facade as consumers read it and as the docs site publishes it: the
-      # topic docs build alone, with default features.
-      - name: Facade docs
-        run: cargo doc -p runvil-engine --no-deps
-
-      - name: Harness facade docs
-        run: cargo doc -p runvil --no-deps
-
-      - name: Engine docs (private items)
-        run: cargo doc --locked --no-deps --all-features -p runvil-runtime --document-private-items
-
   check-workshop:
     runs-on: windows-latest
     steps:
@@ -278,46 +267,6 @@ jobs:
             exit 1
           fi
 
-  # `cargo xtask api` reads rustdoc JSON, which only a nightly emits, so this
-  # job runs on the nightly pinned in crates/build-xtask/src/api/toolchain.rs.
-  # The date is read from that constant, never repeated here, so the two
-  # cannot drift; exporting it as RUSTUP_TOOLCHAIN puts every cargo below on it.
-  api-surface:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Read the pinned nightly
-        id: pin
-        shell: bash
-        run: |
-          set -euo pipefail
-          nightly="$(sed -n 's/^ *nightly: "\(nightly-[0-9-]*\)",.*$/\1/p' crates/build-xtask/src/api/toolchain.rs)"
-          case "$nightly" in
-            nightly-[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]) ;;
-            *)
-              echo "expected one pinned nightly in crates/build-xtask/src/api/toolchain.rs, found: '$nightly'"
-              exit 1
-              ;;
-          esac
-          echo "nightly=$nightly" >> "$GITHUB_OUTPUT"
-          echo "RUSTUP_TOOLCHAIN=$nightly" >> "$GITHUB_ENV"
-
-      - name: Install the pinned nightly
-        run: rustup toolchain install "${{ steps.pin.outputs.nightly }}" --profile minimal
-
-      - name: Install cargo-nextest
-        uses: taiki-e/install-action@4dc1969decfa71b34f25aa7f3dd4656654d9ad1e # nextest
-
-      - name: Cache cargo
-        uses: Swatinem/rust-cache@6323deb102c322ba6fcbdcafc7e3dddab59af2b6 # v2
-
-      - name: Surface closure and listing
-        run: cargo xtask api --check
-
-      - name: Nightly-only fixtures
-        run: cargo nextest run --locked -p build-xtask --run-ignored only
-
   # The custom lints, the dylint library in cppalliance/dylints at the
   # rev the root Cargo.toml's [workspace.metadata.dylint] pins. `cargo
   # dylint` fetches it and builds it on the nightly in its
@@ -377,43 +326,13 @@ jobs:
             exit 1
           fi
 
-  # The Engine crates inherit `rust-version` from the root Cargo.toml's
-  # [workspace.package]; this job builds them at that toolchain. The version
-  # is read from the manifest, never repeated here, so the two cannot drift.
-  msrv:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Read the declared floor
-        id: floor
-        shell: bash
-        run: |
-          set -euo pipefail
-          floor="$(sed -n 's/^rust-version = "\([0-9.]*\)"$/\1/p' Cargo.toml)"
-          if [[ ! "$floor" =~ ^[0-9]+\.[0-9]+(\.[0-9]+)?$ ]]; then
-            echo "expected one rust-version in the root Cargo.toml, found: '$floor'"
-            exit 1
-          fi
-          echo "floor=$floor" >> "$GITHUB_OUTPUT"
-          echo "RUSTUP_TOOLCHAIN=$floor" >> "$GITHUB_ENV"
-
-      - name: Install the floor toolchain
-        run: rustup toolchain install "${{ steps.floor.outputs.floor }}" --profile minimal
-
-      - name: Cache cargo
-        uses: Swatinem/rust-cache@6323deb102c322ba6fcbdcafc7e3dddab59af2b6 # v2
-
-      - name: Build the Engine crates at the floor
-        run: cargo build --locked -p runvil-engine -p runvil-runtime -p runvil-lua -p runvil-prompt -p runvil-types -p runvil-vfs -p runvil-model-client
-
   # Single required status check for branch protection: it fails when any
   # job fails or is cancelled, so a cancelled job cannot read as green.
   # needs: is a static list, so every newly added job must be added to it
   # or that job bypasses this gate.
   ci-green:
     runs-on: ubuntu-latest
-    needs: [fmt, clippy, test, docs, check-workshop, check-workshop-linux, ui, supply-chain, api-surface, dylint, msrv]
+    needs: [fmt, clippy, test, docs, check-workshop, check-workshop-linux, ui, supply-chain, dylint]
     if: always()
     steps:
       - name: Verify every job succeeded

.gitignore

@@ -1,6 +1,5 @@
 /.model-cache/
 /target
-/target-msrv/
 /vibe-review.md
 /conformance-audit.md
 /local/

AGENTS.md

@@ -1,6 +1,6 @@
 # Runvil
 
-Multi-crate Rust workspace for the Engine, the Harness that runs it, and Workshop, a Host. The Gateway is a separate product in its own repository, `cppalliance/runvil-gateway`.
+Multi-crate Rust workspace for Workshop, a Host, and the tooling that builds its installers. The Engine and the Harness are in their own repository, `cppalliance/runvil-harness`, which the root `Cargo.toml` pins by commit. The Gateway is a separate product in its own repository, `cppalliance/runvil-gateway`.
 
 ## Definitions
 
@@ -18,7 +18,6 @@ Seven terms have exactly one meaning each, everywhere in this repository: code c
 
 - "Host", in any capitalization, means only the Host. Other senses use another word: "machine", "real files", "Engine globals", "Engine call", the part's own name ("the desktop app"), or a verb such as run, serve, embed, or hold.
 - "Engine", "Harness", and "Plugin" mean only the defined terms. Anything else gets a qualified lowercase name, such as the Gateway's speech engine or a Tauri plugin. This repository's own checks are "structural checks", "test support", or "fixtures".
-- Engine crates call the code that steps a run "the caller" and never mention the Host. They name the Harness only to say that a responsibility belongs to it, never how the Harness performs it.
 - Names defined elsewhere keep their own meaning (the HTTP `Host` header, Cargo's `harness = false`), crate names are written as they are, and quotations of people stay verbatim.
 - `crates/workshop/ui/test/docs-claims.mjs` enforces these rules in every `AGENTS.md`, every `## Invariants` crate doc, and every `.cursor/rules` file.
 
@@ -36,7 +35,6 @@ Seven terms have exactly one meaning each, everywhere in this repository: code c
 - A Cargo feature gates a real constraint such as a toolchain requirement or heavy native build, not product shape. Feature-disabled builds must not leak optional types into core paths.
 - Runtime and serve paths never compile native dependencies or invoke build tools.
 - Unsafe code stays in its explicitly owned boundary.
-- Engine and Harness crates report every failure as the universal `Error` in `runvil-types`, which `runvil-engine` and `runvil` re-export. A new failure is a new `ErrorCode` variant in its hundreds family with a never-used number, plus an `ErrorFact` variant only when no key names the value. No other error enum or struct, `thiserror` derive, or `impl std::error::Error`; a foreign cause joins through `Error::with_cause`. Allowed: `VfsError` in `runvil-vfs`, throwaway test error types, crate-private `Err` markers that the caller turns into `Error`, and pairs such as `InjectFailure`.
 - Comments explain a non-obvious constraint, ordering requirement, or workaround. A platform or external-bug workaround cites its upstream issue URL.
 - JSON that reaches a recorder or a replay comparison round-trips exactly: object keys sorted, numbers finite, parsed with `float_roundtrip`. A value derived and then logged is rounded to its meaningful precision at the source.
 
@@ -45,8 +43,7 @@ Seven terms have exactly one meaning each, everywhere in this repository: code c
 - Tests: `cargo nextest run --locked --workspace --exclude workshop --exclude workshop-server --exclude workshop-server-api --all-features`, and `cargo nextest run --locked -p workshop -p workshop-server -p workshop-server-api`.
 - Lint: `cargo clippy --workspace --exclude workshop --exclude workshop-server --exclude workshop-server-api --all-targets --all-features`, and `cargo clippy -p workshop -p workshop-server -p workshop-server-api --all-targets`, both with `CARGO_BUILD_WARNINGS=deny`. Clippy covers `cargo check`, so never run a standalone `cargo check --workspace`.
 - Format: `cargo fmt --all --check`.
-- Docs: `cargo doc --workspace --no-deps --all-features --exclude workshop --exclude workshop-server --exclude workshop-server-api` and `cargo doc -p runvil-engine --no-deps` (default features), both with `RUSTDOCFLAGS="-D warnings"`. Clippy does not run rustdoc lints, so never skip these.
-- Facade surface: `cargo +<nightly> xtask api --check`, with the nightly named in `crates/build-xtask/src/api/toolchain.rs` and `CARGO_BUILD_WARNINGS` unset (`Remove-Item Env:CARGO_BUILD_WARNINGS` in PowerShell). It checks both facades, and fails when a surface names an item its facade does not re-export or differs from its listing, `crates/runvil-engine/public-api.txt` or `crates/runvil/public-api.txt`.
+- Docs: `cargo doc --workspace --no-deps --all-features --exclude workshop --exclude workshop-server --exclude workshop-server-api`, with `RUSTDOCFLAGS="-D warnings"`. Clippy does not run rustdoc lints, so never skip this.
 - Custom lints: `cargo dylint --all -- --locked --workspace --all-targets --all-features`, with `cargo-dylint` and `dylint-link` installed. The lints and their UI tests live in `cppalliance/dylints`, at the `rev` the root `Cargo.toml`'s `[workspace.metadata.dylint]` pins; a new lint lands there first.
 - Structural checks: `cargo test -p build-xtask`.
 - Wording: `node --test crates/workshop/ui/test/docs-claims.mjs`, from any directory, no `npm ci` needed.
@@ -57,8 +54,8 @@ Seven terms have exactly one meaning each, everywhere in this repository: code c
 - Pseudo-random test input comes only from a fixed seed that the failure prints. Temporary directory names come from the test's name, the process id, and a counter.
 - A file holds one concept and has no length limit. Split a file only when it holds a second unrelated concept. Size limits sit on functions and types, and clippy and `cargo test -p build-xtask` enforce them. Split an oversized type by responsibility; a new entry in the allowlist in `crates/build-xtask/src/type_size.rs` is a plan decision with a reason, never a way to make a change pass.
 - Production code uses the standard module layout: `foo.rs`, with `foo/bar.rs` for its children. No `#[path]`, and no inline `mod` blocks. A module never has exactly one child file (tests aside): merge it, or make it a peer module `foo_bar.rs` declared beside `foo.rs`.
-- Test code goes at the bottom of the file under test in a `#[cfg(test)] mod tests { }` block when practical (if in doubt, beside), and otherwise in `foo-tests.rs` beside it, wired with `#[path = "foo-tests.rs"] mod tests;`. A big test file may split by topic into siblings named after it, `<stem>-<topic>.rs` (so `foo-tests-topic.rs`). These are the only files wired with `#[path]`, apart from the cfg-selected platform files in `crates/runvil-internal/vfs/src/real.rs`, so a hyphen in a file name means test code. Top-level `tests/` and `benches/` trees follow Cargo's conventions.
-- Crates outside the Engine and Harness keep their older layout until their own pass.
+- Test code goes at the bottom of the file under test in a `#[cfg(test)] mod tests { }` block when practical (if in doubt, beside), and otherwise in `foo-tests.rs` beside it, wired with `#[path = "foo-tests.rs"] mod tests;`. A big test file may split by topic into siblings named after it, `<stem>-<topic>.rs` (so `foo-tests-topic.rs`). These are the only files wired with `#[path]`, so a hyphen in a file name means test code. Top-level `tests/` and `benches/` trees follow Cargo's conventions.
+- The crates in this repository keep their older layout until their own pass.
 
 ## SPA and CSS Rules