e1608: do not fight a hardware trigger, stop the scan on a failed connect, daemon drop timer in the mock

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

README.md

@@ -137,7 +137,8 @@ whether the handshake may answer status 2 ("code ignored"; one reference accepts
 source accepts it); the first frame id; and the maximum frame size. Two further things
 are worth a look on a board even though the mock's header does not flag them: the calibration memory layout and
 its coefficient type, and the status word's bits, in particular whether the "scan running" bit stays set while the
-board waits for a trigger (the source restarts a scan that reads as stopped when auto-restart is on). The DIFF input
+board waits for a trigger (with auto-restart on, the source restarts a scan that reads as stopped only when no
+trigger is configured, so as not to reset the wait for the edge; this is unverified on hardware). The DIFF input
 numbering (channel + 8) and the filler byte after scan start are agreed by both references. The scan overrun count
 is approximate: the board does not say how many scans it dropped, so the frame after a restart reports one lost.
 Errors (no device, a rejected connection code, a timeout, the scan socket closing) are written to stderr as