From 576eeca401d87ce4f88d5e454637fb237d3f24dd Mon Sep 17 00:00:00 2001 From: michael Date: Wed, 17 Jun 2026 18:06:58 -0700 Subject: [PATCH] =?UTF-8?q?docs(applet):=20finalize=20INSTALL.md=20M2=20ac?= =?UTF-8?q?ceptance=20=E2=80=94=20pin=20verdict=20log=20+=20UID=20(M2H.1?= =?UTF-8?q?=20final)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Updates the --step-up expected-output block to the actual STEP-UP M2 OK line emitted on 2026-06-12 verdict, and pins the verified card UID + log path. Memory step_up_implementation_notes.md filled in the 3 TODO markers (M2E + M2F + M2G.2 verdict) and added a J3R452 transient pool budget table (~2,835 / 3,120 B used post-M2G.2). --- applet/INSTALL.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/applet/INSTALL.md b/applet/INSTALL.md index 6643680..fab5812 100644 --- a/applet/INSTALL.md +++ b/applet/INSTALL.md @@ -209,9 +209,12 @@ Document round-trips byte-for-byte against the personalized blob. Successful output appends: ``` -STEP-UP M2: OK — Access Document round-trip verified, 272 bytes match +STEP-UP M2: OK — M2 step-up verified (EXCHANGE + ENVELOPE Access Document round-trip) ``` +Verified against J3R452 UID `04555A4A0B2190` on 2026-06-12 — full verdict +log at `docs/verdicts/2026-06-12-m2-pcsc-verdict.log`. + A `STEP-UP M2: FAIL` line means one of: SELECT-STEPUP didn't arm (no preceding AUTH1), GCM tag mismatch (key/counter divergence), or the recovered AD bytes don't match. The Expedited block above still