test(e2e): Tier C — meld→kiln execution seam (#297), #[ignore]d on kiln#364#317
Merged
Conversation
…ln#364 golden_e2e Tier A/B prove behavioural equivalence under wasmtime but disclose the boundary "NOT on the synth/kiln MCU target". #297 asks to close it. Adds Tier C: fuse a wasi:cli command fixture (--output component), execute it on kilnd, and assert it runs — with the unfused original as the on-kiln baseline so a fused failure is attributable to fusion. The seam is currently BROKEN: kiln's component executor requires a core-instance _start, which meld's multi-core-module wrap (stubs, fused, fixup, caller modules with a deferred start) doesn't expose — it fails with "No core instance exports _start". The same artifact runs under wasmtime via wasi:cli/run (Tier A/B green), so meld's output is spec-valid. Filed kiln#364. So the test is #[ignore]d with that reason; verified it fails for exactly the documented cause (baseline ran on kiln, fused did not). Un-ignore when kiln#364 lands and it pins the meld-to-kiln seam green. kilnd is located via MELD_KILND or the conventional ../../kiln debug build; absent -> skip. Refs: #297, kiln#364. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
LS-N verification gate✅ 58/58 approved LS entries verified
Approved Failed LS entries(none) Missing regression tests(none) Updated automatically by |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Closes the test side of #297 — adds Tier C to
golden_e2e.rs: execute a meld-fused component on kiln (the MCU-target runtime), not just wasmtime (Tier A/B). This is the "honest boundary" Tier A/B explicitly disclose ("NOT on the synth/kiln MCU target").The seam is currently broken — kiln#364
Standing up the test immediately surfaced a real meld→kiln interop blocker (grounded repro on #297):
--componentoutput preserves the exact component WIT (export wasi:cli/run@0.2.6) and runs under wasmtime via the canonical entry (Tier A/B green)._start, which meld's multi-core-module wrap (stubs / fused / fixup / caller, deferred start) doesn't expose →✗ No core instance exports _start.Filed kiln#364 (suggested fix: run components via their
wasi:cli/runcanonical entry, like wasmtime).This PR
wasi:clicommand fixture, runs it onkilnd, and asserts execution — with the unfused original as the on-kiln baseline so a fused failure is attributable to fusion (not a missing-fixture/kiln-absent case).#[ignore]d with the kiln#364 reason, so normal CI stays green. Verified it fails for exactly the documented cause (baseline ran on kiln, fused did not). Un-ignore when kiln#364 lands and it pins the meld→kiln seam green.kilndlocated viaMELD_KILNDor the conventional../../kilndebug build; absent → skip.Normal
golden_e2esuite: 4 pass, Tier Cignored. clippy clean.Refs: #297, kiln#364.
🤖 Generated with Claude Code