Rolling out revealed that the first implementation would not have worked in
production: Element Call ships only as the embedded npm package, and that build
sets publicDir: false because upstream's public/ holds nothing but a favicon.
With that value everything builds, standalone works, and the filter is dead only
inside the widget — verified, not assumed.
Fixed in threadnet-call d270e0c and confirmed end to end: the widget URL resolves
to the model path and the CI artifact carries the assets, not just the local build.
Also corrects a number I gave when asking for the asset decision: the package goes
from 41 to 66 MB, not from 2 to 25 — it already contained source maps and the
crypto and vision wasm.
publish_npm stays manual by design and is sorb's to trigger.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Thore CimbalandClaude Opus 4.8
0f908143b1