GeezerVison

What changed

• FloatingPopover (hub-ui) resolves the outermost ancestor that forms a containing block for position: fixed descendants and <Teleport>s its panel into that ancestor's parent. With no such ancestor, it renders in place as before.
• Select (json-render-ui) gains native, rendering a real <select> instead of FormSelect/FormCombobox. It has no icon, description or searchable support.
• SelectPropsSchema (json-render) gains the matching native field, so a spec can opt an element into it and the tsnapi API snapshot is updated.
• New Storybook story (EscapesTransformedAncestor) demonstrating the escape fix against a transformed, overflow-clipping ancestor.

Why it changed

A position: fixed panel is positioned relative to its nearest ancestor carrying a non-none transform/filter/contain, not the viewport, and is clipped by that ancestor's overflow. Any of FloatingPopover's current consumers — the dock overflow panel, group popover, context menu, edge-position dropdown — would be mispositioned and clipped if rendered inside such an ancestor. Escaping the outermost rather than the nearest such ancestor matters because escaping one can land inside another. Walking parentElement (not parentNode) naturally stops at a shadow root's boundary, so the teleport target stays inside the dock's shadow root — where its stylesheet is scoped — rather than escaping to document.body and losing its styling.

native on Select is an escape hatch worth having regardless: the browser draws a native option list outside the page's layout, so no ancestor can clip or misposition it at all — the dependable choice for a Select embedded in a host layout this component doesn't control.

Porting notes

This ports vitejs/devtools#518 ("fix(core): FloatingPopover escapes a transformed ancestor's containing block; native Select mode" by @dvcolomban), per #205. That PR targeted packages/core/src/client/webcomponents/** in vitejs/devtools, which moved here as packages/hub-ui/src/client/components/floating/** and packages/json-render-ui/src/components/Select.ts in the v0.9 migration.

Adapted rather than ported verbatim:

• The original PR's surface prop on FloatingPopover (tooltip | menu) and Select's dropdown switching to surface="menu" don't have an equivalent here — this fork's Select renders through @antfu/design's FormSelect/FormCombobox (reka-ui popovers), not through FloatingPopover, so there's no consumer to point a menu surface at. FloatingPopover's own five menu-style consumers (dock overflow, group popover, context menu, edge-position dropdown) are left as-is — restyling their padding is a separate, visually-verifiable change I didn't want to bundle into a positioning bug fix.
• native's styling is written against this fork's design-system semantic classes (border-base, bg-base, color-base, …) per this repo's conventions, rather than the upstream fix's inline styles.
• Worth flagging: @antfu/design's FormSelect/FormCombobox (reka-ui SelectPortal/ComboboxPortal) default to portalling into document.body, which suffers the same class of positioning/clipping bug inside a shadow root or transformed ancestor. Fixing that is out of scope here (it's an upstream dependency, not first-party code) but may be worth its own follow-up issue.

Credit to @dvcolomban for the original fix and rationale.

Closes #205

Prepared with the help of an agent.