The -03 normative text and the unchanged rev8 corpus directly contradict each other on whether snippet_sha256 may be absent for unpinned entries. Filing both unchanged makes the claimed conformance reference internally inconsistent.
blocker correctness: Section 5.3.2 says snippet_sha256 MUST be present on every entry and classifies its absence on an unpinned entry as malformed (snippet_sha256_member_absent), while four named rev8 vectors omit that member and require acceptance. The independent checker reproduces the conflict: 40/44 pass under the stated rule and all 44 pass only after removing that rejection rule.
Fix: Before filing, either change/strike the universal snippet_sha256 MUST and absent-member malformed rule, or regenerate the four corpus vectors to include snippet_sha256 and expect the normative behavior.