- the P3 row read "0x02 — 2 bytes" for both kinds of P3; the decode now marks
it (p3_kind): a command that carries data has Lc (the command-data length),
a case-2 command (APDU_SPEC 'le', e.g. READ BINARY/RECORD, GET RESPONSE,
SEARCH…) has Le (the expected response length). The detail row appends
"· Lc (command data length)" / "· Le (expected response length)"
(«Lc (длина данных команды)» / «Le (ожидаемая длина ответа)»)
- a SEARCH RECORD without an SFI searched the current EF (TS 102 221
§11.1.7.1) but showed no file at all; it now resolves like READ/UPDATE:
the SFI's declared file when SFI-addressed (an unresolved SFI stays marked
"SFI n"), otherwise the current selection — with the stale-selection note
when that EF is not a record file. Verified on session 193: the 5.371 s
search (P2=0x04, no SFI) now shows 4FA1, the 5.434 s one (SFI 2) shows 4F3A
- tests: p3_kind cases (Le/Lc/none) and the SEARCH target cases (current EF,
SFI-resolved, unknown SFI, transparent selection); a Node pin for the P3
row and the two new Russian strings; 540 Python + 77 Node tests
- PWA_VERSION/pyproject/version.py 2.7.9, SW cache simtrace-analyser-v89
catarrh
b743c6621d