0.2.32 — verification parity with Python

• verifyRecords no longer resumes from a record's self-declared hash after a mismatch: the chain anchor is always the recomputed value, and records after the first break are reported once, as an unverifiable tail. Mirrors bkuan001/halo-record#8, reported and fixed there by @lukiod through the SECURITY.md process; ported here with the same regression tests.
• VerifyResult now reports empty: true for zero-record chains — nothing to attest is its own state, distinct from a verified chain.
• Message parity with the Python verifier, including the canonical LIMITS reference.