docs: prune the Ray backend from the docs — only document what is real

The Ray executor is a NotImplementedError skeleton, so it doesn't belong in user-facing docs.
Removed docs/ray_backend.md ("planned interface"), the RayExecutor section of execution_backends.md,
the Ray line in philosophy.md, the mkdocs nav entry, and the README [ray] extras row. Fixed the
backend's error message that pointed at the deleted doc. (The skeleton class + [ray] extra remain in
the code, now undocumented — a candidate for full removal.)

Author: copparihollmann

README.md

@@ -93,7 +93,6 @@ aet compare --suite targetgen --plots
 |---|---|---|
 | `[viz]` | matplotlib, numpy | the figures (`plot`, `plot-sessions`, `compare --plots`) |
 | `[tracking]` | mlflow, opentelemetry | MLflow dashboards + OTel tracing |
-| `[ray]` | ray | parallel sweep execution (backend is a skeleton — see docs) |
 | `[docs]` | mkdocs, mkdocstrings | build the docs site (`mkdocs serve`) |
 | `[dev]` | pytest, ruff | development |
 | `[all]` | all of the above | |

docs/execution_backends.md

@@ -27,31 +27,10 @@ class LocalExecutor(ExecutionBackend):
         return [fn(spec) for spec in specs]
 ```
 
-## RayExecutor (skeleton)
-
-The Ray backend is a skeleton. It is not yet implemented. Any call to `submit` or `run_many` raises `NotImplementedError`.
-
-```
-aet run-suite --suite targetgen --methods agent_v1 --seeds 1,2,3 --execution ray
-# raises: NotImplementedError — use --execution local
-```
-
-Attempting to use `--execution ray` with `run-suite` will also raise `NotImplementedError` at the CLI level, before any run is started.
-
-To install the Ray extra (for future use):
-
-```
-pip install 'aet[ray]'
-```
-
-The `RayExecutor` class will import `ray` at construction time and raise `AetError` if it is not installed, rather than at call time.
-
-See `docs/ray_backend.md` for the planned interface.
-
 ## CLI Flag Reference
 
 | Flag | Values | Default | Applies to |
 |------|--------|---------|------------|
-| `--execution` | `local`, `ray` | `local` | `init-run`, `validate`, `run-suite` |
+| `--execution` | `local` | `local` | `init-run`, `validate`, `run-suite` |
 
-Use `--execution local` for all current work.
+The local executor is the only implemented backend.

docs/philosophy.md

@@ -31,7 +31,7 @@ The same principle applies to optional Python dependencies. `aet` has no require
 ## What aet Is Not
 
 - Not a training framework.
-- Not a job scheduler (Ray integration is planned but not yet active).
+- Not a job scheduler.
 - Not a dashboard (SigNoz is an optional viewer, not a dependency).
 - Not a replacement for your project's own test suite.
 

docs/ray_backend.md

@@ -45,7 +45,6 @@ nav:
     - GenAI semconv: genai_semconv.md
     - SigNoz (optional): signoz_optional.md
     - Execution backends: execution_backends.md
-    - Ray backend: ray_backend.md
   - Bundled suite (targetgen):
     - Overview: targetgen_suite.md
     - Metrics: targetgen_metrics.md

mkdocs.yml

@@ -19,12 +19,10 @@ def __init__(self, ray_address: str | None = None) -> None:
 
     def submit(self, spec: RunSpec, fn: Callable) -> Any:
         raise NotImplementedError(
-            "Ray execution backend is not yet implemented. Use --execution local.\n"
-            "See docs/ray_backend.md for the planned interface."
+            "Ray execution backend is not implemented. Use --execution local."
         )
 
     def run_many(self, specs: list[RunSpec], fn: Callable) -> list[Any]:
         raise NotImplementedError(
-            "Ray execution backend is not yet implemented. Use --execution local.\n"
-            "See docs/ray_backend.md for the planned interface."
+            "Ray execution backend is not implemented. Use --execution local."
         )