loadRejectsModuleWithNoMaxAndOversizeInitialMemory

A module that breaks the no-max rule and the size-cap rule at once is still one clean WasmLoadException — and that is the entire claim, because this vector cannot say which rule rejected it.

WasmKernelFixtures.OVERSIZE_INITIAL_MEMORY declares memory 32: 32 initial pages, no max. An impl that dropped the initial check entirely still rejects it on the no-max guard, so this property is green either way — measured, not argued (#2315). It is named for what it holds rather than for the guard it was once thought to pin, because an unisolatable property that reads as isolated is worse than no property: a reader stops checking.

What actually pins the two rules is elsewhere, one vector each: loadRejectsModuleDeclaringMemoryWithNoMax (memory 1 — in-cap initial, so only the no-max rule can fire) and loadRejectsModuleWithOversizeDeclaredMax (memory 1 64). The initial arm is the awkward one, and loadRejectsOversizeInitialWhoseDeclaredMaxIsWithinTheCap explains why.