test(e2e): re-point Tier-C kiln blocker to the precise E5DC2 issue kiln#382 (#297)

[avrabe]

What

Re-points the Tier-C meld→kiln test (tier_c_fused_executes_on_kiln, #297) from kiln#375 to the more precise kiln#382, the root-caused E5DC2 issue kiln split out of #375. Test-annotation only; stays #[ignore]d.

Why

kiln#382 pinpoints the defect: resolve_command_entry treats the wasi:cli/run export's index as a defined-only index into parsed.instances, missing the -K instance-import offset. Corroborated from the meld side — the fused hello_c_cli --component --memory multi wrap imports K=13 instances before the defined run instance, so export.idx (~13+) overruns the defined-only vector → [ComponentRuntime][E5DC2] ...out-of-bounds component instance index. The same fused.wasm runs clean on wasmtime 41, so meld's output is spec-valid; the defect is kiln-side.

Dependency chain for #297 is now precise:

1. kiln#364 (_start gate) — resolved by kiln#374.
2. kiln#382 (E5DC2, -K offset) — the immediate blocker (this PR points here).
3. kiln#375 (cross-core user imports) — the next layer once #382 lands.

kiln#382 itself names tier_c_fused_executes_on_kiln as what its fix un-blocks.

Verification

• Pre-commit gate green (fmt, clippy, cargo-test).
• Test remains #[ignore]d; un-ignores when kiln#382 lands.

Refs #297, kiln#382, kiln#375.

🤖 Generated with Claude Code

[github-actions]

LS-N verification gate

✅ 58/58 approved LS entries verified

	count
Passed (≥1 test, all green)	58
Failed (≥1 test failure)	0
Missing (no ls_*_NN_* test found)	0

_{Approved loss-scenarios.yaml entries are expected to have a
regression test named ls_<letter>_<num>_* (e.g. LS-A-11 →
ls_a_11_*). The gate runs each prefix via cargo test --lib --no-fail-fast and aggregates pass/fail/missing.}

Failed LS entries

(none)

Missing regression tests

(none)

_{Updated automatically by tools/post_verification_comment.py.
Source of truth: safety/stpa/loss-scenarios.yaml.}