refactor(switchyard): remove built-in service integration

.github/workflows/ci.yaml

@@ -413,7 +413,6 @@ jobs:
             nemo-relay
             nemo-relay-adaptive
             nemo-relay-pii-redaction
-            nemo-relay-switchyard
             nemo-relay-ffi
             nemo-relay-cli
           )

Cargo.toml

@@ -10,7 +10,6 @@ members = [
     "crates/worker",
     "crates/adaptive",
     "crates/pii-redaction",
-    "crates/switchyard",
     "crates/cli",
     # Language Bindings
     "crates/python",
@@ -34,8 +33,6 @@ nemo-relay-worker-proto = { version = "0.7.0", path = "crates/worker-proto" }
 nemo-relay-worker = { version = "0.7.0", path = "crates/worker" }
 nemo-relay-adaptive = { version = "0.7.0", path = "crates/adaptive" }
 nemo-relay-pii-redaction = { version = "0.7.0", path = "crates/pii-redaction" }
-nemo-relay-switchyard = { version = "0.7.0", path = "crates/switchyard" }
-switchyard-translation = "0.1.0"
 nemo-relay-ffi = { version = "0.7.0", path = "crates/ffi" }
 nemo-relay-cli = { version = "0.7.0", path = "crates/cli" }
 opentelemetry = { version = "0.32", default-features = false }

RELEASING.md

@@ -30,7 +30,7 @@ The release pipeline publishes these package surfaces from a tag push:
 
 | Ecosystem | Published Surface |
 |---|---|
-| crates.io | `nemo-relay-types`, `nemo-relay-plugin`, `nemo-relay-worker-proto`, `nemo-relay-worker`, `nemo-relay`, `nemo-relay-adaptive`, `nemo-relay-pii-redaction`, `nemo-relay-switchyard`, `nemo-relay-ffi`, `nemo-relay-cli` |
+| crates.io | `nemo-relay-types`, `nemo-relay-plugin`, `nemo-relay-worker-proto`, `nemo-relay-worker`, `nemo-relay`, `nemo-relay-adaptive`, `nemo-relay-pii-redaction`, `nemo-relay-ffi`, `nemo-relay-cli` |
 | PyPI | `nemo-relay`, `nemo-relay-plugin`, `nemo-relay-cli-bin` |
 | npm | `nemo-relay-node` and its seven platform packages, `nemo-relay-openclaw`, `nemo-relay-cli-bin`, and its seven platform packages |
 | GitHub Releases | CLI binaries, `nemo-relay` and `nemo-relay-cli-bin` wheels, CLI and Node npm tarballs, and checksums |
@@ -53,8 +53,7 @@ NeMo Relay versions are anchored on the workspace SemVer in the repository root
 - The root `Cargo.toml` `workspace.dependencies` entries for
   `nemo-relay-types`, `nemo-relay-plugin`, `nemo-relay-worker-proto`,
   `nemo-relay-worker`, `nemo-relay`, `nemo-relay-adaptive`,
-  `nemo-relay-pii-redaction`, `nemo-relay-switchyard`, `nemo-relay-ffi`, and
-  `nemo-relay-cli` must
+  `nemo-relay-pii-redaction`, `nemo-relay-ffi`, and `nemo-relay-cli` must
   stay aligned with that same version.
 - `crates/node/package.json` carries the base npm version for the Node.js
   package. The repository-root `package-lock.json` carries the npm workspace
@@ -139,7 +138,7 @@ Before you create a release tag, confirm the following:
    - crates.io trusted publishers for `nemo-relay-types`,
      `nemo-relay-plugin`, `nemo-relay-worker-proto`, `nemo-relay-worker`,
      `nemo-relay`, `nemo-relay-adaptive`, `nemo-relay-pii-redaction`,
-     `nemo-relay-switchyard`, `nemo-relay-ffi`, and `nemo-relay-cli` are
+     `nemo-relay-ffi`, and `nemo-relay-cli` are
      configured for the top-level
      [`.github/workflows/ci.yaml`](.github/workflows/ci.yaml) workflow
    - GitHub Actions `id-token: write` access is available for the top-level npm publish job
@@ -174,8 +173,7 @@ The helper updates:
 2. The root [`Cargo.toml`](Cargo.toml) `workspace.dependencies` versions for
    `nemo-relay-types`, `nemo-relay-plugin`, `nemo-relay-worker-proto`,
    `nemo-relay-worker`, `nemo-relay`, `nemo-relay-adaptive`,
-   `nemo-relay-pii-redaction`, `nemo-relay-switchyard`, `nemo-relay-ffi`, and
-   `nemo-relay-cli`.
+   `nemo-relay-pii-redaction`, `nemo-relay-ffi`, and `nemo-relay-cli`.
 3. [`crates/node/package.json`](crates/node/package.json) and the `crates/node`
    entry in the root [`package-lock.json`](package-lock.json) to the same
    release version.
@@ -283,7 +281,7 @@ The release pipeline then:
      runs `cargo publish --package` for `nemo-relay-types`,
      `nemo-relay-plugin`, `nemo-relay-worker-proto`, `nemo-relay-worker`,
      `nemo-relay`, `nemo-relay-adaptive`, `nemo-relay-pii-redaction`,
-     `nemo-relay-switchyard`, `nemo-relay-ffi`, and `nemo-relay-cli` through
+     `nemo-relay-ffi`, and `nemo-relay-cli` through
      trusted publishing from
      the top-level workflow
    - `publish-python` downloads the `nemo-relay`, `nemo-relay-plugin`, and
@@ -354,8 +352,7 @@ After the release is live, verify:
 
 1. The `nemo-relay-types`, `nemo-relay-plugin`, `nemo-relay-worker-proto`,
    `nemo-relay-worker`, `nemo-relay`, `nemo-relay-adaptive`,
-   `nemo-relay-pii-redaction`, `nemo-relay-switchyard`, `nemo-relay-ffi`, and
-   `nemo-relay-cli` crates
+   `nemo-relay-pii-redaction`, `nemo-relay-ffi`, and `nemo-relay-cli` crates
    are visible on crates.io.
 2. The `nemo-relay` and `nemo-relay-cli-bin` wheels are visible on PyPI, and
    `pip install "nemo-relay[cli]"` exposes `nemo-relay`.

crates/cli/Cargo.toml

@@ -23,13 +23,11 @@ workspace = true
 [features]
 default = ["atof-streaming"]
 atof-streaming = ["nemo-relay/atof-streaming"]
-switchyard = ["dep:nemo-relay-switchyard"]
 
 [dependencies]
 nemo-relay = { workspace = true, features = ["guardrails-remote", "object-store", "worker-grpc"] }
 nemo-relay-adaptive = { workspace = true, features = ["redis-backend"] }
 nemo-relay-pii-redaction.workspace = true
-nemo-relay-switchyard = { workspace = true, optional = true, features = ["schema"] }
 async-stream = "0.3"
 axum = "0.8"
 base64 = "0.22"
@@ -83,8 +81,3 @@ syn = { version = "2", features = ["full", "visit"] }
 tempfile = "3"
 tokio = { version = "1", features = ["test-util"] }
 tower = { version = "0.5", features = ["util"] }
-
-[[test]]
-name = "switchyard_process_e2e"
-path = "tests/switchyard_process_e2e.rs"
-required-features = ["switchyard"]