pub struct Reply {
pub id_evidence: Box<[IdEvidence]>,
pub ok: bool,
pub error: Option<String>,
pub retryable: bool,
pub png_base64: Option<String>,
pub screenshot_unsupported: bool,
pub capture_revision: Option<u32>,
pub fast_animations: Option<bool>,
pub capture_pending: bool,
pub data: Option<Value>,
pub memory_sample: Option<Box<MemorySample>>,
pub main_thread_stalled: bool,
}Fields§
§id_evidence: Box<[IdEvidence]>§ok: bool§error: Option<String>§retryable: boolSet on failures that may succeed after a wait (element not found yet, assert pending).
png_base64: Option<String>§screenshot_unsupported: bool§capture_revision: Option<u32>Acknowledged render checkpoint. Absent when talking to an older app or when freshness can only be established by an in-process snapshot.
fast_animations: Option<bool>App-side policy acknowledgment. Older apps omit it; runners must retain animation pauses until the app confirms that fast motion is active.
capture_pending: boolInternal retry cadence: frame checkpoints can complete on the next display tick.
data: Option<Value>A step’s structured answer (tests, run_tests, memory_usage).
memory_sample: Option<Box<MemorySample>>Unsolicited telemetry on a connection that explicitly enabled memory_watch.
main_thread_stalled: boolThe step never ran: the app’s main thread did not pick it up within the engine’s budget. Every later step would wait the full budget and fail the same way, so a runner abandons the flow on this rather than on the error text. Older apps omit it.