Record STQ-02 byte preservation evidence

docs/release-testing-0.7.md

@@ -107,7 +107,7 @@ inputs and outputs is absent from the ZIP.
 | ID | Test | R1 | R2 | R3 |
 | --- | --- | --- | --- | --- |
 | STQ-01 | New users receive independent stores and standard folders | [PASS](test-evidence/0.7-r1.md#stq-01) |  |  |
-| STQ-02 | Local message survives Queue-to-Store delivery byte-for-byte |  |  |  |
+| STQ-02 | Local message survives Queue-to-Store delivery byte-for-byte | [PASS](test-evidence/0.7-r1.md#stq-02) |  |  |
 | STQ-03 | Queue free-space calculation is correct on 32/64-bit and reserves space |  |  |  |
 | STQ-04 | Full-disk and unreadable-spool failures defer safely without mail loss |  |  |  |
 | STQ-05 | Retry, expiry, bounce, listing, hold/release, and deletion |  |  |  |

docs/test-evidence/0.7-r1.md

@@ -1409,3 +1409,40 @@ Bongo configuration were used. Clearly named test accounts and their empty
 standard collections were intentionally retained for later Store, Queue,
 quota, and protocol rows. No external mail was sent. The service remained
 active/running as manager PID 1182382 with systemd result `success`.
+
+## STQ-02
+
+Result: **PASS**
+
+Commit `febe35c3` added binary-safe Queue message retrieval, explicit
+diagnostic target selection, direct local recovery delivery, Queue deletion,
+and binary Store export to the maintained administration clients. Unit tests
+cover target bounds, declared-length binary reads, malformed sizes, `QADDM`,
+and deletion. The complete rebuilt suite passed 84 of 84 tests in 10.81
+seconds.
+
+The same commit was pushed to `master`, installed as
+`mail-mta/bongo-9999::bongo` with GCC 15.3.0, and used by the live test on
+2026-07-23. The fixture created target-999 entry `999-a61b246`, retrieved its
+exact Queue-owned message, and delivered it through Queue's `QADDM` local
+Store path to `stqqueue` INBOX document `0000000000000013`. The comparison
+includes the intentional Queue-generated `Received` trace header.
+
+Both sides contained exactly 533 bytes and produced the same digest:
+
+```text
+Queue SHA-256  0f6e37cbeef09d41eb62517fe34489c35188f42bde3b761912174f47bdcf3a9e
+Store SHA-256  0f6e37cbeef09d41eb62517fe34489c35188f42bde3b761912174f47bdcf3a9e
+```
+
+```sh
+./contrib/testing/queue-store-byte-check.sh
+```
+
+The test always deletes its held target-999 Queue entry; the delivered Store
+object remains as release evidence. The service finished active/running as
+manager PID 1196959 with systemd result `success`. The installed suffixless
+configuration and aliases readable to the test runner had aggregate
+fingerprint
+`2bd12226858159f3d6565c2368210b6e57a916257e0943317efa3f34bedfe5cc`.
+No external mail, SMTP relay, collector source, or LMTP endpoint was used.