TIMEOUT: the test never got an answer in time. That is not proof the application is broken, and it is not proof it works: the run cannot tell. A navigation that ran out of time is a TIMEOUT, because it started and the page was slow.
UNREACHABLE: the host could not be reached at all. DNS or the connection failed before any page was observed, as with a name that did not resolve, a refused connection or an offline machine. A certificate error is not here: that one is a finding.
BLOCKED: the site defended itself with a 403, a 429, a block page or a bot challenge. When a defense was on screen, metadata.json names it. A real Android phone that fell asleep or is locked is BLOCKED too, as an unmet prerequisite.
CRASHED: the browser or the process died, for example a closed page, a DevTools protocol error or a dead WebDriver session. It is infrastructure: look at the machine and the driver.
The verdicts guide lists the exact error patterns behind each one.
