You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
scry-3.2.4-wasm32-wasip2.wasm (cosign-verified from pulseengine/scry) is a wasi:cli command component.
kilnd --wasi --wasi-version preview2 --component scry.wasm correctly refuses: "kiln runs core modules; lower it first with meld fuse (RFC build(deps): bump wast from 228.0.0 to 229.0.0 #46)" — good error.
kilnd --wasi --wasi-version preview2 scry.core.wasm --wasi-arg --version → "[ERROR] No entry point found (_start or P3 fused entries)" / E07DA — the fused module carries cabi_realloc/wasi internals but no _start and no P3 entry kilnd's discovery matches.
So the RFC #46 path (component → meld fuse → kilnd) breaks specifically for wasi:cli command components: the wasi:cli/run export doesn't become an entry kilnd finds. Either meld should synthesize a _start trampoline onto wasi:cli/run when fusing a command component, or kilnd's entry discovery should recognize the fused form of run. Cross-tool contract — filing here since kilnd owns entry discovery; meld may be the right place for the fix.
Context: varve wants scry (wasm-only) in toolchain layers, dispatched via the layer's own kilnd — blocked on exactly this.
🤖 Filed per report-tool-friction from the varve layer-composition work.
Repro (all tools from varve layer 2026.08.1)
scry-3.2.4-wasm32-wasip2.wasm(cosign-verified from pulseengine/scry) is a wasi:cli command component.kilnd --wasi --wasi-version preview2 --component scry.wasmcorrectly refuses: "kiln runs core modules; lower it first withmeld fuse(RFC build(deps): bump wast from 228.0.0 to 229.0.0 #46)" — good error.meld fuse scry.wasm -o scry.core.wasm→ "Fusion complete!"kilnd --wasi --wasi-version preview2 scry.core.wasm --wasi-arg --version→ "[ERROR] No entry point found (_start or P3 fused entries)" / E07DA — the fused module carriescabi_realloc/wasi internals but no_startand no P3 entry kilnd's discovery matches.So the RFC #46 path (component → meld fuse → kilnd) breaks specifically for wasi:cli command components: the
wasi:cli/runexport doesn't become an entry kilnd finds. Either meld should synthesize a_starttrampoline ontowasi:cli/runwhen fusing a command component, or kilnd's entry discovery should recognize the fused form ofrun. Cross-tool contract — filing here since kilnd owns entry discovery; meld may be the right place for the fix.Context: varve wants scry (wasm-only) in toolchain layers, dispatched via the layer's own kilnd — blocked on exactly this.
🤖 Filed per report-tool-friction from the varve layer-composition work.