fix(wasix): use strict LLVM memory semantics

[f0rr0]

Summary

Based on #218; independent of #241.

• Disable LLVM's nonvolatile-memory optimization in embedded WASIX AOT and the Postmaster compiler; retain the readonly funcref optimization.
• Align compiler settings, artifact identities and validators, and reject conflicting producer overrides.
• Cover the policy with compiler-profile and manifest tests.

This preserves Wasm memory semantics but can increase query latency. Existing nonvolatile AOT artifacts must be rebuilt, not relabelled. Fresh performance and cross-platform artifact qualification remain outstanding.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
oliphaunt-docs	Ready	Preview	Oct 5, 2026 7:26am UTC

[f0rr0]

Rebased onto main 207fcfa5 through refreshed #218. Current head: 14326fe818cc5a702a8ab568aa106dadfe7b2fd6.

Fresh CI is running for that exact head.

Run 37243820019 predates #253. That merged change addresses the Swift/React Native carrier mismatches and Linux/macOS Node-API runtime-version mismatch. The strict-memory patch is unchanged; its five AOT manifest tests, Rust formatting and locked Cargo metadata checks pass locally. The shared packaging and workflow checks also pass.

The separate Windows recovery failure remains: client_compat exits with 0xe06d7363 on Wasmer 7.2/MSVC. Neither rebasing nor changing LLVM memory semantics repairs exception handling. It remains tracked in #208; no recovery test or platform gate was disabled. Fresh CI must qualify this head.