File names: the DF-scoped spec dictionary + refreshed EF/SFI tables (v2.5.0)

- the file/DF/SFI dictionaries move to simtrace_analyser/ef_tables.py and are
  extracted from the pinned specs: TS 102 221 (MF, Annex H.1), TS 31.102
  (ADF USIM 4.2 and the child DFs 4.3/4.4/4.6, the H.1-H.12 SFI annexes, the
  Annex L.6 Relay Node/certificate files; Annex A/E as the ADF/DF file
  completeness cross-check), TS 31.103 and TS 51.011 - 20 DF tables (~370
  entries) and 14 SFI tables, up from ~180 flat names and 3 SFI tables
- names are DF-scoped: a FID reused across DFs resolves to the file its DF
  context names - 4F09 is EF_SUPI_NAI under DF_5GS but EF_PROSE_GC under
  DF_ProSe, 6F07 is EF_IMSI in the USIM/SIM but EF_IST in the ISIM, 6F4E is
  EF_EXT4 in DF_TELECOM but EF_EXT5 in the USIM ADF; the flat table keeps
  only names that are identical everywhere and is the fallback when no DF is
  known (the two names the old table had wrong there are fixed: 6F0A is
  EF_AC_GBAUAPI, 6F53 EF_LOCIGPRS)
- the SELECT-path decoder resolves the 7FFF children against the USIM ADF
  table, and the Files view names files DF-first - including files first seen
  only via their FCP (a select-only file used to keep the bare FID, e.g.
  ADF/6F3C is now ADF/EF_SMS (6F3C))
- tests/data/spec_files.json pins the extracted tables; tests/test_decode.py
  asserts the DF/ADF tables cover them, the SFI tables match them exactly and
  every flat name is a spec name for that FID; tests/extract_spec_tables.py
  regenerates the fixture from the PDFs and --check re-verifies the tables
- README/README_RUS document the dictionary and its sources; PWA_VERSION and
  pyproject/version.py 2.5.0, SW cache simtrace-analyser-v71

README.md

@@ -218,7 +218,8 @@ UPDATE operations seen in the trace; card-initiated ones are inferred when a
 read returns bytes differing from what the image already knew — bytes never
 seen before just fill the image (an observation, not a change).  Files reached
 by SFI share the entry of their path/FID accesses: the SFI ↔ FID relations come
-from the normative tables (TS 102 221 Annex H, TS 31.102 Annex H) and from every
+from the normative tables (TS 102 221 Annex H.1 and the TS 31.102 H.1–H.12
+annexes; the ISIM SFI rows come from TS 31.103) and from every
 surfaced FCP carrying the `88` DO, including the spec's "SFI = the 5 LSBs of the
 FID" rule when the DO is absent; an SFI used before its relation is learned
 stays provisional and merges into the resolved entry.  A file's DF context
@@ -229,6 +230,17 @@ image freezes past 64 KB of observed bytes per file (`image_truncated`) and the
 change log keeps the last 1000 events per file (`changes_total` keeps counting).
 Counters are returned by the API but not shown in this view yet.
 
+File names are **DF-scoped**: `simtrace_analyser/ef_tables.py` holds the complete
+per-DF file tables and SFI lists extracted from the pinned specs (TS 102 221,
+TS 31.102 including its H.1–H.12 SFI annexes, TS 31.103, TS 51.011), so a FID
+reused across DFs resolves to the file its DF context names — `4F09` is
+EF_SUPI_NAI under DF_5GS but EF_PROSE_GC under DF_ProSe, `6F07` is EF_IMSI in
+the USIM/SIM but EF_IST in the ISIM, `6F4E` is EF_EXT4 in DF_TELECOM but
+EF_EXT5 in the USIM ADF — with the flat table as the fallback when no DF is
+known.  `tests/extract_spec_tables.py` regenerates the pinned fixture
+(`tests/data/spec_files.json`) and `--check` re-verifies the tables against the
+PDFs.
+
 Server options:
 
 ```