reactor-runtime 3.2.3__tar.gz → 3.2.4__tar.gz

{reactor_runtime-3.2.3 → reactor_runtime-3.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: reactor-runtime
-Version: 3.2.3
+Version: 3.2.4
 Summary: A Python framework for building real-time, interactive video models
 Author: Reactor
 Author-email: Reactor <team@reactor.inc>
@@ -30,7 +30,7 @@ Description-Content-Type: text/markdown
 
 **Build real-time AI models in Python.**
 
-[📖 Documentation](https://deploy-docs.reactor.inc) · [🚀 Quickstart](https://deploy-docs.reactor.inc/development/quickstart) · [🌐 Reactor](https://reactor.inc)
+[📖 Documentation](https://docs.reactor.inc/deploy/overview) · [🚀 Quickstart](https://docs.reactor.inc/deploy/development/overview) · [🌐 Reactor](https://reactor.inc)
 
 </div>
 
@@ -95,19 +95,19 @@ reactor run
 
 ## Install
 
-Everything runs through the [`reactor` CLI](https://deploy-docs.reactor.inc/platform/installation). There is nothing to install on your host but the CLI and Docker; the runtime ships inside the image the CLI builds for your workspace.
+Everything runs through the [`reactor` CLI](https://docs.reactor.inc/deploy/platform/installation). There is nothing to install on your host but the CLI and Docker; the runtime ships inside the image the CLI builds for your workspace.
 
 ```sh
 brew install reactor-team/tools/reactor-cli
 ```
 
-Not on macOS, or pinning a release in CI? See [Install the CLI](https://deploy-docs.reactor.inc/platform/installation).
+Not on macOS, or pinning a release in CI? See [Install the CLI](https://docs.reactor.inc/deploy/platform/installation).
 
 ## Learn more
 
-- [Quickstart](https://deploy-docs.reactor.inc/development/quickstart): from zero to a streaming model in 2 minutes
-- [Model anatomy](https://deploy-docs.reactor.inc/development/reactor-model/model-anatomy): every piece of a Reactor model, line by line
-- [The run loop](https://deploy-docs.reactor.inc/development/reactor-model/run-loop): emitting frames, batches, and frame rates
+- [Quickstart](https://docs.reactor.inc/deploy/development/overview): from zero to a streaming model in 2 minutes
+- [Model anatomy](https://docs.reactor.inc/deploy/development/reactor-model/model-anatomy): every piece of a Reactor model, line by line
+- [The run loop](https://docs.reactor.inc/deploy/development/reactor-model/run-loop): emitting frames, batches, and frame rates
 
 ## Development
 

{reactor_runtime-3.2.3 → reactor_runtime-3.2.4}/README.md

@@ -4,7 +4,7 @@
 
 **Build real-time AI models in Python.**
 
-[📖 Documentation](https://deploy-docs.reactor.inc) · [🚀 Quickstart](https://deploy-docs.reactor.inc/development/quickstart) · [🌐 Reactor](https://reactor.inc)
+[📖 Documentation](https://docs.reactor.inc/deploy/overview) · [🚀 Quickstart](https://docs.reactor.inc/deploy/development/overview) · [🌐 Reactor](https://reactor.inc)
 
 </div>
 
@@ -69,19 +69,19 @@ reactor run
 
 ## Install
 
-Everything runs through the [`reactor` CLI](https://deploy-docs.reactor.inc/platform/installation). There is nothing to install on your host but the CLI and Docker; the runtime ships inside the image the CLI builds for your workspace.
+Everything runs through the [`reactor` CLI](https://docs.reactor.inc/deploy/platform/installation). There is nothing to install on your host but the CLI and Docker; the runtime ships inside the image the CLI builds for your workspace.
 
 ```sh
 brew install reactor-team/tools/reactor-cli
 ```
 
-Not on macOS, or pinning a release in CI? See [Install the CLI](https://deploy-docs.reactor.inc/platform/installation).
+Not on macOS, or pinning a release in CI? See [Install the CLI](https://docs.reactor.inc/deploy/platform/installation).
 
 ## Learn more
 
-- [Quickstart](https://deploy-docs.reactor.inc/development/quickstart): from zero to a streaming model in 2 minutes
-- [Model anatomy](https://deploy-docs.reactor.inc/development/reactor-model/model-anatomy): every piece of a Reactor model, line by line
-- [The run loop](https://deploy-docs.reactor.inc/development/reactor-model/run-loop): emitting frames, batches, and frame rates
+- [Quickstart](https://docs.reactor.inc/deploy/development/overview): from zero to a streaming model in 2 minutes
+- [Model anatomy](https://docs.reactor.inc/deploy/development/reactor-model/model-anatomy): every piece of a Reactor model, line by line
+- [The run loop](https://docs.reactor.inc/deploy/development/reactor-model/run-loop): emitting frames, batches, and frame rates
 
 ## Development
 

{reactor_runtime-3.2.3 → reactor_runtime-3.2.4}/pyproject.toml

@@ -92,7 +92,7 @@ pythonpath = ["."]
 
 [project]
 name = "reactor-runtime"
-version = "3.2.3"
+version = "3.2.4"
 description = "A Python framework for building real-time, interactive video models"
 readme = "README.md"
 license = "Apache-2.0"

{reactor_runtime-3.2.3 → reactor_runtime-3.2.4}/pyproject.toml.orig

@@ -20,7 +20,7 @@ version = "1.20260814.7"
 
 [project]
 name = "reactor-runtime"
-version = "3.2.3"
+version = "3.2.4"
 description = "A Python framework for building real-time, interactive video models"
 readme = "README.md"
 license = "Apache-2.0"

{reactor_runtime-3.2.3 → reactor_runtime-3.2.4}/src/reactor_runtime/manifest.py

@@ -2,8 +2,8 @@
 
 The ``reactor.yaml`` manifest is the runtime's one configuration file:
 ``runtime.import`` names the model as a ``"module:Class"`` reference,
-``runtime.config`` points at the model's own config file, and the top-level
-``recording:`` block configures the recorder. This module turns that file into
+``runtime.config`` points at the model's own config file, and the
+``runtime.recording`` block configures the recorder. This module turns that file into
 a :class:`~reactor_runtime.core.RuntimeConfig` and the reference into the model
 class — and it is the only code that does either, so every entry point resolves
 the same model from the same directory.
@@ -32,8 +32,8 @@ def load_config(manifest: Path) -> RuntimeConfig:
 
     ``runtime.import`` — the ``"module:Class"`` model reference — and
     ``runtime.config`` — the path to the model's own config file — name the
-    model, ``model.name`` is the name it is published under, and the top-level
-    ``recording:`` block configures the recorder; the rest of the manifest
+    model, ``model.name`` is the name it is published under, and the
+    ``runtime.recording`` block configures the recorder; the rest of the manifest
     describes the model to the platform and is not the runtime's concern. The
     config path is passed to the model verbatim (resolved to an absolute path);
     the runtime never parses its contents.
@@ -65,7 +65,7 @@ def load_config(manifest: Path) -> RuntimeConfig:
         model_ref=model_ref,
         model_name=_model_name(document.get("model")),
         config_path=_resolve_config_path(runtime, manifest),
-        recording=_recording_from_manifest(document.get("recording")),
+        recording=_recording_from_manifest(runtime, document),
     )
 
 
@@ -110,19 +110,25 @@ def import_model_class(model_ref: str) -> type[ReactorCore]:
     return model_cls
 
 
-def _recording_from_manifest(block: Any) -> RecordingConfig:
+def _recording_from_manifest(runtime: dict[str, Any], document: dict[str, Any]) -> RecordingConfig:
     """Parse the manifest's ``recording:`` block into a :class:`RecordingConfig`.
 
-    A missing or non-mapping block leaves recording disabled at its defaults.
-    Unknown keys are ignored so a manifest can carry forward-looking settings
-    without breaking an older runtime.
+    The block nests under ``runtime:``. A top-level ``recording:`` block is
+    still honored for older manifests, and the nested block wins when both are
+    present. A missing or non-mapping block leaves recording disabled at its
+    defaults. Unknown keys are ignored so a manifest can carry forward-looking
+    settings without breaking an older runtime.
 
     Args:
-        block: The raw ``recording:`` value from the manifest, if any.
+        runtime: The manifest's ``runtime`` section.
+        document: The whole manifest document, for the legacy top-level block.
 
     Returns:
         The parsed recorder configuration.
     """
+    block = runtime.get("recording")
+    if not isinstance(block, dict):
+        block = document.get("recording")
     if not isinstance(block, dict):
         return RecordingConfig()
     raw_video = block.get("video")