v3.18.3: the test-run card-exchange log

Verifying a script from the log was impossible: the runner wrote no card
lines, SCP80's plaintext C-APDU / secured packet / PoR landed only in the
report, and a menu selection logged nothing (the interactive path showed just
"STATUS poll (menu-select 9000)" / "STATUS -> 9000").

Every step now writes a `TEST-RUN step N:` line family to stderr, request
before response:

- generic actions: the APDU/raw event data sent and the SW/RESP received
  (`APDU TX=...`, `ENVELOPE(Event Download) ... data=...`, `READ/UPDATE ... -> SW=...`);
- SCP80: `C-APDU=` (or `SP=`), `SECURED=<hex> (N B) TAR=... SPI1=... SPI2=... CNTR=...`,
  the response SW, and the PoR - `PoR[inline] status=... TAR=... CNTR=... raw=...`
  plus `R-APDU SW=... data=...` (with the bad-format note);
- expectations: `FETCH=<apdu> -> SW=... <raw>`, `CMD 0x.. <NAME> qual=..`,
  `TR=<apdu> -> SW=...`, and `PoR[sms-submit] ...` + `R-APDU` for the SEND
  SHORT MESSAGE transport;
- status: `STATUS 1/N -> <sw>` per attempt;
- menu selection: `MENU-SELECT ENVELOPE=<apdu> item=<id> ('<text>') -> SW=...`
  (both the runner action and /api/menu-select; the old STATUS lines stay as
  context).

The shared secured-packet sender logs each segment's answer
(`OTA SEND: ENVELOPE i/N -> <SW>`), the scp80 step's report `sent` now carries
the C-APDU/SP hex, and `--apdu-trace` remains the raw transport view.

help EN/RU and docs/test-scripts.md gained the "reading the run log" note.
Tests: 816 frontend + 718 Python; sw cache simple-v385.

docs/test-scripts.md

@@ -93,6 +93,34 @@ PoR-in-submit:
 5. **Counters**: the run starts from the preset's stored counter and persists
    each accepted packet's next value; consecutive runs continue correctly.
 
+### Reading the run log
+
+Every step writes a semantic line to the server log under its step number,
+request before response:
+
+```
+TEST-RUN step 1: SCP80 C-APDU=80E2900000
+TEST-RUN step 1: SCP80 SECURED=0100…1A2B (N B) TAR=B00001 SPI1=16 SPI2=21 CNTR=0000000A
+TEST-RUN step 1: SCP80 -> SW=9000
+TEST-RUN step 1: PoR[inline] status=por_ok TAR=B00001 CNTR=0000000A raw=0271…aabb
+TEST-RUN step 1: R-APDU SW=9000 data=AABB
+TEST-RUN step 2: STATUS 1/2 -> 9102
+TEST-RUN step 3: FETCH=8012000002 -> SW=9000 D03C8103012500…
+TEST-RUN step 3: CMD 0x25 SET UP MENU qual=00
+TEST-RUN step 3: TR=81030125008202828183020000 -> SW=9000
+TEST-RUN step 4: MENU-SELECT ENVELOPE=80c2000009d30702020181900101 item=1 ('One') -> SW=9103
+```
+
+- A PoR delivered as SEND SHORT MESSAGE is logged on the step that fetches it:
+  `PoR[sms-submit] …` followed by the same `R-APDU` line.
+- Other actions log their send/response pair too (`APDU TX=… -> SW=…`,
+  `ENVELOPE(Event Download) … -> SW=…`, `READ MF/… -> SW=…`).
+- The shared secured-packet sender logs each segment's answer
+  (`OTA SEND: ENVELOPE i/N -> <SW>`).
+- `--apdu-trace` adds the raw transport view
+  (`APDU-TRACE(…): <cmd> → SW: … RESP: …`) for every APDU, including the
+  file-manager reads and pySim's auto-handler traffic.
+
 ## Document shape
 
 ```json