refactor(hub)!: drop the docker and e2b sidecar backends; process is the only provisioner (CL-8330)

.env.example

@@ -56,16 +56,8 @@ PRINCIPAL_KEY_ENCRYPTION_KEY=111111111111111111111111111111111111111111111111111
 # Markdown-to-PDF rendering through a Gotenberg server.
 # GOTENBERG_URL=http://localhost:3000
 
-# Where sidecars run: comma-separated ids, first is the default.
-# process (default, no config) | docker | e2b. See docs/sidecar-provisioners.md.
-# SIDECAR_PROVISIONERS=process
-# DOCKER_PROVISIONER_IMAGE=
-# E2B_API_KEY=
-# E2B_TEMPLATE=
+# Sidecars run as child processes of the hub. Both optional.
 # PROCESS_PROVISIONER_SIDECAR_ENTRY=
 # PROCESS_PROVISIONER_RUNTIME=
-# ws(s):// address sidecars dial back to; required for docker and e2b.
+# ws(s):// address sidecars dial back to.
 # HUB_SIDECAR_WEBSOCKET_URL=
-# JSON array of {"provider","specifier","export"} replacing the sidecar's
-# default inference adapter manifest.
-# SIDECAR_ADAPTER_MANIFEST=

AGENTS.md

@@ -107,7 +107,5 @@ passing; rebuilding coverage for the area it covered happens under CL-8150.
   disagrees with it is wrong until a review changes the doc
 - [docs/GLOSSARY.md](docs/GLOSSARY.md) — product-term to platform-term mapping
 - [docs/local-dev.md](docs/local-dev.md) — running fully local with Ollama
-- [docs/sidecar-provisioners.md](docs/sidecar-provisioners.md) — choosing
-  and configuring where sidecars run
 - [docs/package-migrations.md](docs/package-migrations.md) — how a
   package's own database migrations are written and applied

IMPLEMENTATION.md

@@ -34,10 +34,8 @@ upstream first, then gets re-vendored.
 Deployment mechanics are not yet settled:
 
 - Target hosting platform and process topology (one hub, how many
-  sidecars, where they run) are undecided.
-- The sidecar provisioner an install uses in production (`process`,
-  `docker`, or `e2b`) is a per-deployment choice — see
-  [docs/sidecar-provisioners.md](docs/sidecar-provisioners.md).
+  sidecars, where they run) are undecided. Sidecars run as child
+  processes of the hub; there is no other provisioner backend.
 - Secrets management for `CREDENTIAL_ENCRYPTION_KEY` and
   `PRINCIPAL_KEY_ENCRYPTION_KEY` in a real deployment is undecided.
 - Migration/rollout ordering across `hub`, `sidecar`, and `web` on deploy

apps/hub/package.json

@@ -48,7 +48,6 @@
     "arktype": "catalog:",
     "better-auth": "catalog:",
     "drizzle-orm": "catalog:",
-    "e2b": "^2.36.1",
     "hono": "catalog:",
     "postgres": "catalog:",
     "simple-icons": "^16.28.0"