{"id":"torn-length-prefix-causes-silent-skip","text":"If a torn write corrupts the 4-byte length prefix in `wal.py:_read_record`, the reader interprets garbage as `record_length`, reads that many bytes (consuming valid subsequent records as data), then returns `None` on short read — no error is raised and no resync is attempted","truth_value":"IN","source":"entries/2026/05/29/topic-block-aligned-wal-records.md","source_url":"","source_hash":"","justifications":[],"dependents":[],"metadata":{},"explanation":{"steps":[{"node":"torn-length-prefix-causes-silent-skip","truth_value":"IN","reason":"premise"}]}}