Header 7542eff271b522a79e45348cca4509ff was reported with three strides, 76, 92
and 104. It is not one type with a variable stride, and not a misparse.
It appears three times per level, always with record count 9, always in the
same order at the same offsets within the region:
offset stride count first last
863842 92 9 928 1640
867554 76 9 912 1520
872866 104 9 1000 1832
The offsets are 3712 apart each time and the strides differ, so these are three
separate chunks sharing 16 header bytes.
Consequence for the type ID: 64 distinct headers for 66 distinct record
layouts, not 64 for 64. The header is nearly a type ID but does not uniquely
determine the layout. Not excluded: a distinguishing byte sits outside the 16
captured, or the layout varies within a type.
This does not change "63 of 64 headers imply one stride", which remains true,
but the mapping is not a bijection and should not be used as one. Worth
checking before the parser is extended to dispatch on header alone.
ReaperOfVeriod
1d84562e88