test(resource): #305 — opaque-rep construct+drop runtime oracle (resolved, no meld fix)

[avrabe]

Drove #305 to ground by building the repro and running it, rather than editing Tier-5 resource code blind.

Outcome: #305 is resolved; meld needs no change

• Built resource_floats_opaque.wasm from the wit-bindgen fork feat/opaque-rep-attribute (51eca6b6 — "user-supplied dtor for opaque-rep export resources").
• meld fuses the 3-component re-exporter chain (--output component, 163 KB, 695 funcs, 4 adapters) and construct+drop runs cleanly on wasmtime.
• The original drop-teardown trap was the wit-bindgen-side opaque-rep destructor (missing inner-handle forwarding); the fork's dtor fixes it. The suspected meld handle-table discrimination (merger.rs/fact.rs) was not required — verified empirically by running the repro.

What this lands

• test_runtime_wit_bindgen_resource_floats_opaque — fuses + construct+drop regression oracle. Fixture is gitignored (~11 MB; recipe added to tests/wit_bindgen/README.md), so it skips in CI when absent and is the load-bearing local oracle (same posture as other large fixtures).
• SR-43 proposed → verified.
• Cargo.lock synced to 0.34.0 (v0.34 release bumped Cargo.toml only).

No meld code change ⇒ this is verification closure, not a versioned release. Closes #305.

[github-actions]

LS-N verification gate

✅ 57/57 approved LS entries verified

	count
Passed (≥1 test, all green)	57
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.}