[REA-6855] Read the runtime.step_results block from the manifest

[Dere-Wah]

Why

Whether each finished step is kept as a folder of files is the model's choice, the same way recording is: it decides what is worth keeping and how to encode it. So it belongs in the model's reactor.yaml, next to runtime.recording, and not in a session option a client could switch.

What Changed

The manifest gains a runtime.step_results block:

runtime:
  step_results:
    enabled: true
    video: {codec: h264, preset: veryfast, crf: 23}   # or codec: h265
    audio: {codec: aac, bitrate_kbps: 128}
    queue: 8

It names no tracks: every track of a step's output is kept as its own stream. queue bounds how many steps may wait to be saved, so a model that steps faster than its steps encode never waits on saving; a queue below 1 fails the load, because an unbounded queue is what that value would otherwise mean. A missing or malformed block leaves step results off at their defaults, and unknown keys are ignored, as for the recording block.

The block parses into a StepResultsConfig on RuntimeConfig, and the README documents it where the manifest is introduced, so the authoring surface lands with its documentation. Nothing is saved yet: the writer, the store, and the routes follow in the next PRs, and the session descriptor reports "step_results" only from #238, where steps are saved, so it never promises folders the runtime does not write.

[github-actions]

[codex-review] - [P1] runner.py: Descriptor advertises enabled retention although no results are saved.

• [P2] manifest.py: New authoring surface is missing the required README documentation.

Scope: full (c0f4bc9..498bd52).

View workflow run.

[Dere-Wah]

• [REA-6855] Serve saved step folders over HTTP #239
• [REA-6855] Save each reported step as a folder of files #238
• [REA-6855] Write one step's output as a single MP4 file #237
• [REA-6855] Read the runtime.step_results block from the manifest #236 👈 (View in Graphite)
• [REA-6854] Close a session when it reaches its steps #235
• [REA-6854] Report each finished step to the runtime with complete_step() #234
• [REA-6854] Apply a session's starting input, sent by a system client #233
• [REA-6854] Read starting_input and steps from the start body #232
• [REA-6854] Deliver commands and reactor events to the model in posted order #231
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[tempusfrangit]

Approved with a nonblocking documentation follow-up: please move the runtime.step_results README documentation from #239 into this PR so it lands with the manifest surface, as noted in the existing inline comment. The configuration parsing looks sound.

[Dere-Wah]

@tempusfrangit done in fcfd87c: the runtime.step_results README documentation now lands here with the manifest surface (#239 keeps only the routes), and the descriptor no longer advertises step_results until #238 saves steps.

[Dere-Wah]

Merge activity

• Oct 5, 6:07 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Oct 5, 6:24 PM UTC: Graphite rebased this pull request as part of a merge.
• Oct 5, 6:25 PM UTC: @Dere-Wah merged this pull request with Graphite.