Capture The orchestrator routed you here. This atom owns the full recording lifecycle: launch a target, execute an interaction script, collect raw outputs. You should already have a driver atom loaded (tuistory, true-input, or agent-browser) and optionally a target atom (droid-cli). This atom layers the recording discipline on top. Inputs The command that invoked you should have provided: - Target : what to launch and on which branch(es) - Interaction script : the sequence of actions to perform - What to capture : recordings (.cast/.mp4), screenshots, text snapshots, byte sequences - Keystrok…