Mystic stable A48 BinkP TLS qualification

PASS native Linux amd64 Mystic 1.12 A48 with cryptlib 3.4.5.
The exact same converter-generated PKCS#15 keyset used by A49 passed:
- exact input leaf DER presented by MIS
- test CA and localhost verification
- TLS 1.2 with encrypted BinkP M_NUL receive/send
- actual cryptlib mapping and unchanged keyset
- isolated loopback-only namespace; no production files or services

A48 fixture was configured using its matching developer record definitions.
The shipped A48 data-change marker is 1.12 A47.
This does not qualify native Windows A48 protocol handshakes.

Stock A48/A49 expose no ssl.cert password field in RecConfig or ServerInfoRecord.
RecEchoMailNode.CryptKey encrypts Netmail content and is not this setting.
The current converter CLI uses explicit label and protected password-file inputs.

Official archive SHA256: fb427b57d9627ef93008c561df807991bdd288b4a1fc1757dfb5bb5434f286a3
MIS SHA256: 9e5405d6b11ef2f5c0b694760685ca0baf61ef563ee9a3930a0db905d62b33c8
records.112 SHA256: 7aec6ca491c5868d7c43d33298c910d092e8b2902df02ff634cef6bfe2cb99ef

https://github.com/geosone/mpemtrans/blob/master/docs/mystic-binkp-qualification.md