replay
This program answered from a recorded run: the effects the trace's program performed, with the responses they got, in order, and nothing else handled. The program's own code computes the result from the responses, so the handlers of the recorded run are not needed, and what they did on the side, the log lines and the writes, does not happen. The first effect that differs from the recording fails, naming both, as does a program that finishes before the recording does or performs an effect the recording has no answer for. The effect the recording left unanswered, because its handler ended the run, is passed on unanswered here too, to whatever handler is applied next. A trace read from text answers with the literals the text keeps typed and fails on a response it only describes.
This program answered from one path of its tree, as replay of a trace: the path's answers in order, a failure the path stops at passed on unanswered, and the value the path returns checked against the program's.