docs: the E-1608 source kind, its probe readings and its unverified commands

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

docs/claude/probe-readings.md

@@ -1827,8 +1827,9 @@ are unrealized and measure 0x0.
 ## `[source-kinds]`
 
 ```
-[source-kinds] kinds=udps,probe
+[source-kinds] kinds=udps,e1608,probe
 [source-kinds] form udps: round_trip=1 valid=1
+[source-kinds] form e1608: round_trip=1 valid=1
 [source-kinds] form probe: round_trip=1 valid=1
 [source-kinds] panel disconnected: panels=1 present=1 sensitive=0
 [source-kinds] panel connected: panels=1 present=1 sensitive=1
@@ -1840,10 +1841,10 @@ are unrealized and measure 0x0.
 source-plugin path from the registry to the producer thread. The variable also registers the test-only `probe`
 kind, so a run without it never shows that kind. The `form` line appears once per registered kind.
 
-- `kinds=udps,probe`: a missing kind means `register_builtin_sources()` was not called before `parse_args()`,
+- `kinds=udps,e1608,probe`: a missing kind means `register_builtin_sources()` was not called before `parse_args()`,
   or the env var gate is wrong.
 - `round_trip=0`: a form's `write` and `read` disagree about a key -- a renamed `SourceConfig` key, or an
-  absent key that was not defaulted. `valid=0` is a default configuration the form refuses.
+  absent key that was not defaulted. `valid=0` is a default configuration the form refuses. The e1608 form's sample sets address, port, scan_rate, mode, ai1, trigger, dir1 and plot0; a mismatch names one of those.
 - `panel disconnected: sensitive=0 present=1`: **disable, don't hide.** `present=0` is a panel that was hidden
   or never added; `sensitive=1` is a panel that stays live with no source behind it.
 - `panel connected: sensitive=1`: anything else means `apply_source_panels` acted on the wrong widget (it must
@@ -1856,6 +1857,53 @@ kind, so a run without it never shows that kind. The `form` line appears once pe
 
 The UDPS run has no `source-` page in `side_stack`, because the UDPS kind has no panels.
 
+## `[e1608]`
+
+```
+[e1608] panel ao: present=1 sensitive=1 connected=1
+[e1608] panel dio: present=1 sensitive=1 connected=1
+[e1608] actions: ao0_level=1 do1=1 counter_reset=1
+[e1608] stream: connected=1 signals=4 expect=4 names=AI0,AI1,DI0,Counter frames=274 rate=1000.000 ok=1
+[e1608] calibration: ai0_mean=0.5000 expect=0.5000 ok=1
+[e1608] capture button: present=1 sensitive=0
+[e1608] state: connects=1 message=''
+[e1608] decode: ok=1
+[e1608] scan socket closed by the board
+[e1608] reconnect: connects=2 connected=1 ok=1
+[e1608] resumed: frames_before=612 frames_after=662 ok=1
+```
+
+`UDPSCOPE_PROBE_E1608=1500` (the first eight lines; `frames=` and the exact mean vary) and
+`UDPSCOPE_PROBE_E1608_RECONNECT=8000` (the last two) run as `--source e1608` against `tools/mock_e1608.py`
+with the options in `verification.md`. The ninth line is the source's own stderr message about the drop, not a
+probe line (its text is the error the source met, once per distinct message). `connected=0` throughout, with
+`actions: skipped (not connected)`, is the no-board run; it is a reading and not a failure, and it also prints
+the one `[e1608] handshake with ...: Connection refused` line, `stream: ... signals=0 expect=1 ... ok=0`,
+`calibration: ai0_mean=nan ... ok=0` and `state: connects=0 message='handshake with ...'`.
+
+- `panel ...: present=1 sensitive=<connected>`: **disable, don't hide.** `present=0` is a panel that was never
+  added; `sensitive` that differs from `connected` is `apply_source_panels` acting on the wrong widget.
+- `actions: ao0_level=1 do1=1 counter_reset=1`: each control was found by its widget name (`e1608-ao0-level`,
+  `e1608-do1`, `e1608-counter-reset`). A `0` is a renamed widget, or (`do1`) `dir1=o` missing from the run. The
+  effects are read off the **mock's log**, not here: a DAC write near 2.5 V (within 0.01), `DOUT 0x02`, `COUNTER_RESET`.
+  A control that was found but whose effect is missing is a command that `post()` did not deliver or `poll()`
+  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.
+- `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
+  run that never got AI0 (not connected, or AI0 not enabled).
+- `capture button: present=1 sensitive=0`: a source with no datagrams leaves the capture UI disabled, not hidden.
+- `state: connects=1 message=''`: a non-empty message at this point is a refusal that happened (for example
+  `calibration memory refused; using nominal values`), which the stream then ran through.
+- `decode: ok=1`: a fixed raw buffer against hand-computed volts (intercept 100, BIP10V and BIP5V, the code
+  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.
+
 ## `[prefs-probe]`
 
 ```