# M6 buffered evidence — round-trip fixtures

Wire-byte fixtures cited in `docs/M6-buffered-evidence.md` (F44 evidence walk
of buffered/Suspend captures `077, 079-082, 094`). Each `.bin` is the inner
body of an NMX subscription callback message (post-46-byte transfer envelope)
copied verbatim from the named capture's `frida-events.tsv`.

| File | Source | Content |
|---|---|---|
| `094-line145-datatupdate-recordcount2.bin` | `captures/094-frida-buffered-separate-writer/frida-events.tsv:145` | `0x33` DataUpdate, `record_count = 2`, Int32 records. **Truncated by Frida 4 bytes shy of `inner_length=61`** — record 2's value bytes are absent. The decoder accepts this and records record 2's `value = None`. |
| `094-line48-datatupdate-recordcount2-status.bin` | `captures/094-frida-buffered-separate-writer/frida-events.tsv:48` | `0x32` SubscriptionStatus, `record_count = 2`, the supervisory advise reply that established the buffered subscription. Two records, both Int32. Reference shape for the multi-record path. |

The fixtures exist to:

1. Demonstrate the F44 walk's evidence is reachable from the test harness
   without requiring access to the full capture tree.
2. Round-trip through `NmxSubscriptionMessage::parse_inner` in unit tests
   (`subscription_message::tests::data_update_capture_094_truncated_record_errors`
   asserts the F44 contradiction of R2; `data_update_multi_record_round_trip`
   covers the typed multi-record decode path that landed with F44).

Bytes are stored as raw binary, no metadata. The TSV row offsets in the source
column are the canonical citations.