v3.32.7: drop the pySim JSON disclosure from the file manager

The decoded view is the client-side EF decoder's table over the raw
read's bytes.  The collapsed "pySim JSON (server)" block was an
unrelated second decode - opening it ran another /api/read with mode
'decoded' (pySim's read_binary_decoded/read_records_decoded on the
card) - and it existed only when our decoder covered the file, so it
could not serve as a cross-check where one would matter.

/api/read keeps mode 'decoded' for API callers.  Help, READMEs and the
project notes now state the table is built in the browser from the same
raw bytes; ef_decode.test.js pins the view's output and that no
mode 'decoded' read remains in the PWA.

1016 Python + 955 frontend green; simple-v465.
This commit is contained in:
2026-10-23 09:50:09 +03:00
parent ded63c94e4
commit 9411fd775d
10 changed files with 39 additions and 31 deletions
+15
View File
@@ -9,6 +9,21 @@ every change carries a descriptive commit message.
## [Unreleased]
## [3.32.7] — 2026-10-23
### Removed
- The file manager's decoded view no longer carries the collapsed **pySim JSON
(server)** disclosure — the view is the client-side EF decoder's table only. The
disclosure was an unrelated *second* decode: opening it issued another `/api/read` with
`mode: 'decoded'` to run pySim's `read_binary_decoded`/`read_records_decoded`, and it
was reachable only when our decoder covered the file (`Read decoded` is decoder-gated),
so the one case where a second opinion would matter — a file our decoders do not
cover — never offered it. `/api/read` keeps `mode: 'decoded'` for API callers; the
help, READMEs and project notes now say the decoded table is built in the browser from
the same raw bytes. `ef_decode.test.js` pins the view's output and the absence of the
lookup.
## [3.32.6] — 2026-10-23
### Fixed