Add a sandboxed WASM runtime as a separate, optional LamBoot module so third parties can ship diagnostic modules without recompiling LamBoot or being linked into core.
Design constraints (non-negotiable)
- Separate module (
lamboot-wasm.efi), never linked into core LamBoot.
- Loaded at menu time via the existing
lamboot-modules/ discovery path, subject to module signing (release-signed / MOK-trusted / dist-trusted / none).
- Read-only host-call ABI: no host writes, no file creation, no NVRAM writes, no protocol installation from a WASM module.
- Resource caps: fuel + wall-clock + memory + report-size.
Dependency
Gated on the health/metrics/SMART infrastructure (#13) landing first — otherwise the host-call ABI for modules would need rework once that infrastructure exists. Targeted for v1.1, after v1.0 stabilizes.
Add a sandboxed WASM runtime as a separate, optional LamBoot module so third parties can ship diagnostic modules without recompiling LamBoot or being linked into core.
Design constraints (non-negotiable)
lamboot-wasm.efi), never linked into core LamBoot.lamboot-modules/discovery path, subject to module signing (release-signed / MOK-trusted / dist-trusted / none).Dependency
Gated on the health/metrics/SMART infrastructure (#13) landing first — otherwise the host-call ABI for modules would need rework once that infrastructure exists. Targeted for v1.1, after v1.0 stabilizes.