From c859fa08e0133fa7fe4649a16011d009a92c041a Mon Sep 17 00:00:00 2001 From: Lann Martin Date: Tue, 25 Aug 2026 12:41:53 -0400 Subject: [PATCH] findings: park the wasmparser case-folding entry until the wasmtime 49 bump Operator decision: upstream is actively reworking strongly-unique post-CM#703, so re-verify the bundled wasmparser at the 49 toolchain bump instead of building shim-side enforcement now. Revisit protocol recorded on #238. --- upstream-component-model-repo-findings.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/upstream-component-model-repo-findings.md b/upstream-component-model-repo-findings.md index 761c6fe..e40af35 100644 --- a/upstream-component-model-repo-findings.md +++ b/upstream-component-model-repo-findings.md @@ -149,7 +149,11 @@ entry on resolution — see git history.) post-#703 Explainer.md before filing. Consequence for us: spec-invalid method/static and interface-name case-collisions can reach the runtime's conventions layer — one of the triggers tracked in #185; translator-side - enforcement is #238. + enforcement is #238. **Deferred 2026-08-25 (operator): parked until the + wasmtime 49 toolchain bump** — upstream is actively reworking this corner + post-#703, so re-verify the bundled wasmparser then (probes in #238); if it + folds, the bump closes #238 and this entry dies, otherwise implement + shim-side and re-raise the filing question. [WebAssembly/component-model]: https://github.com/WebAssembly/component-model