docs: customer-ready sweep + README restructure + tshark CI fix

Audit pass over the public-facing surface so a customer can read it
end-to-end without tripping on stale numbers or self-contradictions.

README + docs accuracy:
- Test counts 426 → 445, assertions 2 557 → 2 753 (verified via
  doctest run); E5 row was missing test_e5_kat (19 cases)
- Interop checks 24 → 31, COMPLIANCE.md message count 149 → 164,
  COMPLIANCE.md "291 cases / 1515 assertions" → 445 / 2 753
- README "60+ test IDs" for MES_INTEROP → actual 59
- PVD example counts: 32 SVIDs/17 CEIDs → 29/21, "~40 handlers
  in ~200 lines" → 51 in ~460, "~700 lines" → ~1,100; main.cpp
  header table-of-contents resynced with the actual 7 sections

Out-of-scope honesty (COMPLIANCE.md §8 + FAQ.md):
- Removed HSMS-GS (was both ✅ implemented in §1 and "out of scope"
  in §8; INTEGRATION.md §7 documents using it)
- Removed multi-block SECS-I (split_message/assemble_message exist
  with 4 dedicated tests)
- Added serial-port wiring as the genuine open ⬜ item — FSM is
  tested end-to-end over TCP; only the asio serial_port glue is
  deferred
- COMPLIANCE.md intro now lists E42 and notes "E37 (SS + GS)"

README restructure:
- Moved the 8-command proof table and per-standard test-coverage
  table to a new PROOFS.md (72 lines)
- README now leads with what / Quick start / Documentation map,
  then a one-paragraph "How it's proved" linking to PROOFS.md
- Updated cross-refs in FAQ.md, GLOSSARY.md, VERIFICATION.md, and
  interop/README.md to point at PROOFS.md

CI fix — tshark-dissector job:
- interop/tshark_validate.sh hardcoded /app/build/secs_server etc.
  which only works inside the docker image.  Now derives ROOT from
  the script's own location and accepts BUILD/SERVER/CLIENT/DATA
  env overrides, so CI can run it from the workspace dir
- Verified still passes in docker (69 frames, 0 malformed)

.gitignore:
- Added build-fuzz/ and build-tsan/ (were showing as untracked)

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

FAQ.md

@@ -210,7 +210,7 @@ Both are necessary; neither replaces the other.  See VERIFICATION.md.
 ## How do I bring this to a customer site?
 
 Run through the five external proofs in
-[README's proof table](README.md#proof-of-feature-completeness) at
+[the eight commands in PROOFS.md](PROOFS.md) at
 the customer's network.  Then walk MES_INTEROP.md against their
 actual MES.  Then deploy per [SECURITY.md](SECURITY.md) for the
 nftables / stunnel / signing setup.  Then page on the metrics from
@@ -219,7 +219,9 @@ INTEGRATION.md §6.4.
 ## What's not implemented?
 
 See [COMPLIANCE.md](COMPLIANCE.md) §8 ("Explicitly out of scope")
-for the honest list.  The short version: multi-block SECS-I
-transfers (irrelevant on HSMS), tool-specific Equipment Processing
-States (the engine is there, vendors plug in their states), and
-GEM RTS certification (paid third-party gate, not a code feature).
+for the honest list.  The short version: tool-specific Equipment
+Processing States (the engine is there, vendors plug in their
+states), the serial-port driver for SECS-I (the FSM is wired
+end-to-end over TCP, the asio `serial_port` glue is a deferred
+follow-up), and GEM RTS certification (paid third-party gate, not
+a code feature).