tine replay

Replay has two explicit modes. Cache mode reuses recorded work. Rerun mode executes through a native runtime or selected harness.

Terminal

# Reuse recorded steps without model or tool calls
tine replay result.tine --mode cache --save replayed.tine

# Inspect the replay plan without writing
tine replay result.tine --inspect

# Execute again through a harness
tine replay result.tine --mode rerun --harness codex --save rerun.tine

Deterministic identity is not live determinism

Cache replay preserves known outputs and provenance. In v0.4 its fork identity is deliberately deterministic, but that does not claim a live provider would return the same result today.

Rerun is scoped

A live rerun requires the state and execution interface supplied by a native runtime or harness. It executes a fresh run with a new run ID; it does not reuse the cached replay's fork identity. A flat external trace does not automatically become resumable.