docs: GLOSSARY + FAQ + interop README refresh + doc-map fixes

Fills four documentation gaps surfaced by the doc audit:

1. README "Documentation map" was missing VERIFICATION.md (the file
   that backs the proof-of-feature-completeness claims) and is now
   pointing at the new files added in this commit too — ARCHITECTURE,
   GLOSSARY, FAQ, examples/pvd_tool/ (the last two land next).

2. interop/README.md only documented secsgem-py.  Three of the five
   external validators (tshark, secs4j, libFuzzer) plus the E5 KAT
   were invisible from the directory's own README.  Rewritten as a
   complete index — what's external, what each catches, how to run,
   what bugs they've already surfaced, when to add a new validator.

3. GLOSSARY.md is new.  Every SEMI acronym used in the codebase or
   the docs gets one row: SVID, DVID, CEID, RPTID, ALID, ECID, PPID,
   MID, CARRIERID, PRJOBID, CTLJOBID, SUBSTID, OBJSPEC, OBJTYPE,
   MDLN, SOFTREV, EQPTYP, DATAID + every ACK code (COMMACK, ONLACK,
   OFLACK, HCACK, CMDA, ACKC5-7-10, DRACK, LRACK, ERACK, EAC, TIACK,
   GRANT, ALCD, OBJACK) + stream/function shorthand + HSMS terms +
   T-timers + E84 signals + the standards lineup + codebase shortcuts
   ("the model", "the router", "the proof", etc.).  Cuts week-1
   onboarding time.

4. FAQ.md is new.  Canonical answers to the questions that come up
   once per integration: why HSMS unencrypted, SVID vs DVID, PJ vs
   CJ, who fires FSM transitions, what runs on which thread, how to
   add a new SECS-II message, ASCII vs Binary, common MES quirks,
   how spool works, robustness fuzz vs libFuzzer, conformance vs
   interop, what's not implemented.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

README.md

@@ -88,9 +88,14 @@ through the data model.  Watch the logs interleave.
 |-----------------------------------------------|-------------------------------------------------------------------------|
 | [COMPLIANCE.md](COMPLIANCE.md)                | Per-capability audit against every SEMI standard implemented           |
 | [INTEGRATION.md](INTEGRATION.md)              | Vendor-side tutorial: YAML → callbacks → production deploy             |
+| [ARCHITECTURE.md](ARCHITECTURE.md)            | How the pieces fit + how to extend (new store / FSM / message)         |
+| [VERIFICATION.md](VERIFICATION.md)            | Test plan for the external validators behind the proof table           |
 | [BENCHMARKS.md](BENCHMARKS.md)                | Performance envelope (throughput, latency, memory) + how to re-run     |
 | [MES_INTEROP.md](MES_INTEROP.md)              | Day-1 punch list to run against your commercial MES (60+ test IDs)     |
 | [SECURITY.md](SECURITY.md)                    | Concrete configs: nftables, stunnel, minisign, SIEM audit-log schema   |
+| [GLOSSARY.md](GLOSSARY.md)                    | SEMI vocabulary: SVID, CEID, PPID, ALCD, HCACK, T-timers, …            |
+| [FAQ.md](FAQ.md)                              | Common questions and their canonical answers                            |
+| [examples/pvd_tool/](examples/pvd_tool/)      | Worked example: a realistic fictional PVD tool, YAML + C++ wiring      |
 | [LICENSE](LICENSE)                            | Proprietary license terms                                              |
 
 ---