Module drive 

The deterministic driver (R11): live drivers record one Action before the reducer or render work runs; replay consumes those actions and re-runs the SAME production handlers with native launches suppressed by the tape. Service interleaving is the consumption order at the single delivery boundary — never worker-completion wall time.

Structs

StartupOpen

Enums

Action

Every external step a replay reproduces. Event carries the shared typed AppEvent (terminal input, paste, resize, quit intent, and every completed worker/service result), so the live handler and the replayed handler are one function.

Functions

replay

Replay a recorded forensic node stream end to end. The seed is taken first, the pure editor is reconstructed, and every recorded action is consumed through the shared body until the deliberate End; any divergence, gap or unexpected residue is an error, never a warning. The frame renderer replay checks recorded cells against; installed by the caller since cell-grid production lives outside the engine.