INITIAL_ABOVE_DECLARED_MAX

initovermax.wat (82 bytes) — declares memory 32 16: an initial of 32 pages above the default 16-page cap, with an explicit max sitting exactly at the cap.

It is the only shape in which the oversize-initial guard could be the sole sandbox rule a module breaks: the max is present (so the no-max rule is satisfied) and within the cap (so the oversize-max rule is satisfied). Reaching it costs spec validity — min <= max is a WebAssembly validity condition, and wat2wasm needs --no-check to emit this — which is exactly the case the guard is for: an engine that does not check limits itself.

Measured, all three shipped engines do check, by three different mechanisms, so the guard is unreachable-as-sole-cause everywhere today. That is worth an executable record rather than a comment, and this vector is it. See WasmRuntimeConformanceSuite.loadRejectsOversizeInitialWhoseDeclaredMaxIsWithinTheCap for the per-engine measurements and what the property therefore does and does not pin.