The S1 adversarial boundary review found the off = (i*entry_size) % 512 arithmetic tested only for 128-byte entries. Add a test with 256-byte entries and the sole valid entry at index 1 (offset 256), exercising the non-zero-offset path. No code change — the parser was already correct (off is always a multiple of entry_size >= 128, so off + 128 <= 512); this closes the coverage gap.