Summary
Any hyphenated tag is claimed by the file-based component resolver at parse time (it tries to load <name>.stx from disk), which makes it impossible to render a Web Component / custom element — the resolver wins before the browser ever sees the tag. This blocks hosting third-party imperative widgets the idiomatic way.
Impact (real app)
bench integrates a third-party rich-text editor (ts-medium-editor). It cannot use a <rich-text-editor> custom element because stx intercepts the hyphenated tag and looks for rich-text-editor.stx. The documented workaround (resources/components/Bench/RichTextEditor.stx:1-8) is to drop to a plain <div data-richtext-host> found via document.querySelectorAll('[data-richtext-host]'), plus a body-level MutationObserver (:479-492) to catch instances that appear inside toggled :if blocks — an entire imperative component built by hand.
defineCustomElement / ClientOnly / onClient are all exported, but they can't help here because the parse-time resolver claims the tag first.
Ask
Provide an escape hatch so a registered/known custom element (or an explicitly-marked tag) is passed through to the browser instead of being resolved as an .stx component — e.g. a <ClientOnly> raw-passthrough boundary, or a resolver skip-list for tags registered via defineCustomElement.