[integration] static fast-interpreter/P2 component profile + multi-module hardening

[matthargett]

Purpose

This is the WAMR integration line for the statically linked snqr Apple host. The target guest format is component-model wasm32-wasip2 on the stable WASI Preview 2 0.2.6 package set.

Existing core-Wasm guests and their raw import aliases remain available only for parity validation while canonical component bindings are adopted. Those legacy guests are not described as components.

Static Apple product profile

The checked profile builds a single full-LTO static archive with:

INTERP=1, FAST_INTERP=1, DEBUG_INTERP=0, MINI_LOADER=0
AOT=0, JIT=0, FAST_JIT=0, WAMR_COMPILER=0
COMPONENT_MODEL=1, LIBC_WASI_P2=1
LIBC_WASI=0, LIBC_UVWASI=0, LIBC_BUILTIN=0
THREAD_MGR=1
SHARED_MEMORY=0, LIB_PTHREAD=0, LIB_WASI_THREADS=0
MULTI_MODULE=1
SIMD=1, RELAXED_SIMD=1, EXCE_HANDLING=1, REF_TYPES=1
-O3, -Werror, -flto=full

All product host interfaces and component dependencies are statically linked. Dynamically loaded components remain forbidden. MULTI_MODULE=1 is retained solely for existing core-Wasm compatibility guests and their helper modules during the parity sweep; it is not a component plug-in system.

Because the shipping profile enables the core-module registry for those legacy helpers, the ownership hardening is part of the product contract: the registry owns copied names, module-reader buffers remain runtime-owned until safe destruction, callers have an explicit unregister/ownership transfer, and component-owned embedded core modules are immediately removed from the global registry.

Host-owned execution threads remain supported through the thread manager. Guest shared memory, guest pthreads, and WASI threads remain disabled. This permits the main component interpreter and separately started/stopped WebAudio worker or audio-node execution contexts without introducing dynamically loadable WASI components.

Integrated component and Preview 2 work

• Preview 2 can be built without Preview 1, while legacy component defaults still select Preview 2.
• Built-in standard WASI interfaces declare the implemented 0.2.6 package version and accept compatible patch-level imports in the correct direction.
• Callback-scoped canonical-memory access and exact callback-state queries fail closed outside the active host callback.
• Prepared flattened export calls provide reusable scratch storage and explicit post-return handling for allocation-free steady-state host calls.
• Raw native component dispatch preserves and restores callback context.
• Embedded core-module ownership is transferred back to the component tree so repeated component load and unload does not accumulate registry entries.
• Fast-interpreter relaxed SIMD, exception handling, component parsing, canonical ABI, Apple portability, and failure cleanup remain integrated from the earlier stack.
• Public API documentation uses the actual exported parameter names.

Focused Airbus-lineage changes remain split for review in airbus-forks#10 through bytecodealliance#17. The current-upstream registry lifetime stack is staged separately in review/multi-module-unregister-unload for upstream triage.

Local product proof

Final head: f0c9b78d8cd11ad52b586f0cdfafc330c0d83396.

• The current dev/cm_wasip2_complete base was merged without changing the tested integration tree, preserving every focused commit.
• Signed macOS and iOS Release builds completed from the static fast-interpreter profile.
• An exact Rust wasm32-wasip2 command component ran with host=0 guest=0 on the local Mac and a physical iPhone XS.
• The Dodeca guest rendered visibly on both targets and was verified with screenshots from each device.
• Release archive verification passed for arm64, Preview 2-only component support, fast-interpreter-only engine selection, full LTO, and MULTI_MODULE=1.
• Post-merge component parser tests passed 58/58; component execution tests passed 13/13.
• Repeated component load/instantiate/add/deinstantiate/unload passed all eight cycles without retained embedded modules.
• Registry ownership tests passed under macOS ASan and Linux GCC ASan with leak detection; static analysis reported no findings.
• The raw WAMR bit-crusher plus WebAudio worker start/stop lifecycle sanitizer passed.
• Clang-format 14 coding-guideline checks passed for the focused and integration commits.
• The consolidated Linux unit job passed 867/867, including explicit rejection of all seven checked-in rustc 1.94.1 / WASI 0.2.9 fixtures, null-module unload, and the formerly aborting unknown-module-type case.

CI policy for this update

The product batch was pushed only after the local component, sanitizer, static-analysis, LTO, Mac, and physical-device proof was green. One merge-only update resolved the current base conflict after the same parser, execution, and Apple archive checks passed on the merge head.

The first automatic matrix exposed two integration-specific unit failures: the multi-module ownership change had made wasm_runtime_unload(NULL) unsafe, and seven older checked-in Rust test binaries actually require WASI 0.2.9. The null path is a no-op again with a direct regression test; the newer binaries are now honest negative compatibility cases without weakening the 0.2.6 ceiling. Both fixes were locally validated and pushed together once. The null guard is also staged for current-upstream review on fix/null-module-unload, and the Airbus-lineage compatibility/error-reporting changes are included in airbus-forks#17.

A separate NuttX failure was hosted-runner disk exhaustion during checkout; configure and build never ran, the identical matrix slot was green previously, and no source workaround was added. No full hosted workflow was manually dispatched or re-run.

Final hosted result

The final automatic batch completed successfully without a manual dispatch or rerun: 11/11 workflows passed, representing 504/504 successful check records (470/470 distinct displayed check names). There are no failed, cancelled, skipped, queued, or pending checks on f0c9b78d8cd11ad52b586f0cdfafc330c0d83396.