Clear the open minors: lost marking and overrun logging, form teardown guard, line breaks and ERANGE in config, probe strength

The E-1608 source marks every restart as lost and logs each overrun; its form stops touching
siblings after the chooser destroys them; the link skips command id 0, retries a full-buffer
discover send and ignores a zero-length scan read. Session files escape \n and \r; get_int and
get_double reject out-of-range values; the UDPS port spin reports changes; a skipped source panel
says why on stderr. The E-1608 probe now checks the signal names and the reconnect itself.

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

docs/claude/probe-readings.md

@@ -1890,7 +1890,8 @@ the one `[e1608] handshake with ...: Connection refused` line, `stream: ... sign
   did not run.
 - `stream: signals=4 expect=4 rate=1000.000 ok=1`: the enabled channels plus the plotted digital lines plus the
   counter, at the scan rate. `signals` below `expect` is a signal the source did not declare; `rate` off by a
-  factor is the pacer computed from the wrong aggregate.
+  factor is the pacer computed from the wrong aggregate. `ok` also requires `names=` to be the enabled analog
+  inputs, then the plotted digital lines, then `Counter`, in that order: swapped channels read `ok=0`.
 - `calibration: ai0_mean=0.50xx ok=1`: the mock's AI0 is 0.5 V under a 5 Hz sine of 0.1 V, read through
   non-trivial factory coefficients; the mean over two periods lands on 0.5 V only when `decode()` applies them.
   About `0.2043` is the **uncalibrated** reading (the calibration read failed, or `calibrate=0`); `nan` is a
@@ -1902,7 +1903,9 @@ the one `[e1608] handshake with ...: Connection refused` line, `stream: ... sign
   clamp at both ends). It needs no board; `ok=0` is a change to the calibration arithmetic.
 - `reconnect: connects=2 connected=1`, `resumed: ok=1`: the mock dropped both links at about 3 s; the source
   reported it, retried after 2 s and the frame count moved on. `connects=1` is a source that never noticed the
-  drop (neither the scan read nor the status check raised it), `resumed: ok=0` is a reconnect that did not restart the scan.
+  drop (neither the scan read nor the status check raised it), `resumed: ok=0` is a reconnect that did not restart
+  the scan (it also reads 0 when `connects` is still 1, since a frame count that grows on a link that never dropped
+  proves nothing).
 
 ## `[prefs-probe]`