Clarification on Streaming Boot vs Cold Boot Behavior in xtask Emulator

[Radioactive-67]

I’m trying to understand how --streaming-boot in cargo xtask runtime differs from the default cold boot flow in the software emulator.

From the Caliptra Subsystem Streaming Boot (Flashless/Recovery) specification, streaming boot involves:
I3C recovery interface usage
INDIRECT_FIFO_CTRL/DATA/STATUS registers
payload_available and image_activated signaling
Recovery state transitions via DEVICE_STATUS and RECOVERY_STATUS

My questions:
In the software emulator, does --streaming-boot model this full recovery/I3C FIFO-based flow?
Or is it a higher-level abstraction that injects the runtime image without modeling I3C hardware semantics?
Architecturally, how does emulator streaming boot differ from emulator cold boot?