feat(core): createMenuPress runs the menu press model without React; useMenuPress takes the menu's ref

.changeset/create-menu-press.md

@@ -0,0 +1,7 @@
+---
+'@astryxdesign/core': patch
+---
+
+[feat] `createMenuPress(menu, options)` runs the menu press model on any element without React: the row under a release acts, the highlight follows a held pointer, a mouse press on `trigger` opens the menu, and a finger held on it opens it after the long-press delay. `update(options)` merges new options, which apply from the next event without ending a press in progress. `startBehavior: 'items'` starts a press only on an item, so other content in the menu keeps its own clicks. `destroy()` removes every listener it added. `useMenuPress(menuRef, options)` is its React form: `triggerRef` names the trigger, and there is nothing to spread. Its press exists only while the menu element is mounted, so a menu that opens on a press of its trigger keeps its element mounted while closed. Deprecated (DEP-0019), and removed in 0.8.0: the options form, `useMenuPress({menuRef, …})` with its `menuProps` and `triggerProps`, which still works as before; and `DropdownMenuTriggerProps.onPointerDown` and `onContextMenu`: forward `ref` to the control instead: the menu listens on it, and an ancestor that stops the press-down hides it from the press. `astryx upgrade` moves calls to the ref form and drops redundant forwards of the two handlers. DropdownMenu, BreadcrumbItem, NavHeadingMenu, TopNavMenu and the SideNav and TopNav heading menus move to the ref form with no change in behavior. The press starts after the page's own press-down handlers, as a handler composed before it did, so a press-down that one of them stops, or cancels inside the menu, starts no press. One change follows: a DropdownMenu caller's `onPointerDown` now reaches the menu element, where the press used to replace it, and its `preventDefault()` keeps the press from starting.
+
+@vjeux

.changeset/long-press-detector.md

@@ -0,0 +1,7 @@
+---
+'@astryxdesign/core': patch
+---
+
+[chore] Internal: `useLongPress` runs its long-press detection through an internal detector with no React, so a press model that runs without React can share it. The hook and its handlers behave as before; `onLongPress` now also comes from the committed render. Not exported from the package entry point.
+
+@vjeux

.changeset/menu-press-codemod.md

@@ -0,0 +1,7 @@
+---
+'@astryxdesign/cli': patch
+---
+
+[feat] `astryx upgrade` moves `useMenuPress({menuRef, …})` calls to the ref form, `useMenuPress(menuRef, options)`, and drops the spreads of its `menuProps` and `triggerProps`. It also drops a DropdownMenu trigger's plain forwards of the deprecated `onPointerDown` and `onContextMenu`. Where it cannot prove the result, it leaves the code unchanged with a TODO.
+
+@vjeux

docs/specs/AST-055-caller-rendered-trigger/spec.md

@@ -150,16 +150,16 @@ INV2), so the decision lives here and those records cite it.
 
 ### Behavioral contract
 
-| ID  | Invariant                                                                                                                                                                                                                                                                                                                                                                                                                  | Basis                                                                                                | Verification state                       |
-| --- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | ---------------------------------------- |
-| FR1 | A component that lets a caller supply the control which opens its overlay MUST take that control as a render prop named `renderTrigger` (DEC-5): a function the component calls with one props object, whose returned element the component renders as given. The component MUST NOT wrap the returned element in an element of its own, and MUST NOT require a particular tag or a particular Astryx component.           | DEC-1; `spec:AST-002` FR4                                                                            | Accepted; jsdom evidence pending         |
-| FR2 | Spreading the handed-back props onto one element MUST be the whole integration. The object MUST carry the ref or anchor the overlay positions against, the `id` AR1 needs, every handler that opens, toggles, and closes the overlay from that control on the component's supported input paths, and the disclosure attributes of AR1. The object's type MUST be exported from the component's public entry point.         | DEC-1; `architecture:public-component-api` INV1, INV5                                                | Accepted; jsdom evidence pending         |
-| FR3 | A caller-supplied control MUST NOT be taken as a `ReactNode` slot that the component renders inside an interactive element of its own. Callers routinely pass an interactive component, and that shape nests one interactive element inside another (AR2). A content slot rendered inside a component-owned control remains valid for non-interactive content and is unchanged.                                            | DEC-1; AR2                                                                                           | Accepted; jsdom evidence pending         |
-| FR4 | The caller's control MUST own a box. A component MUST NOT render it inside a wrapper with no box of its own (`display: contents`), and MUST NOT depend on such a wrapper where it paints or offsets a focus indicator on the trigger, or positions the overlay against the trigger's rect: there is no rect to anchor to and no box on which to paint. FR1 removes the need for any wrapper.                               | DEC-2; `architecture:layer-runtime` anchor contract                                                  | Accepted; real-browser evidence required |
-| FR5 | Hover, pressed, and every other pointer paint on the caller's control MUST remain the caller's own CSS. The component MUST NOT write paint onto an element it does not render. The component MUST publish the overlay's open state on the handed-back props as `aria-expanded`, so a caller styles the open state from the rendered attribute and no additional public API is added for it.                                | DEC-3; `spec:AST-002` FR1, FR2                                                                       | Accepted; jsdom evidence pending         |
-| FR6 | The prop's consumer documentation MUST show styling the open state from `aria-expanded` on the caller's control, and MUST state that a pressed look keyed to `:active` is not a substitute, because `:active` does not behave the same under a finger, and press paint follows `spec:AST-094` FR11's profiles instead.                                                                                                     | DEC-3; no current core component styles off `aria-expanded`, so callers have no example to copy      | Accepted; documentation evidence pending |
-| FR7 | Where a component offers both a built-in control and this prop, exactly one control MUST render. The caller's control MUST win, identically in every presentation the component supports, and a development warning MUST fire; the component's own chrome for the replaced control MUST NOT render. Silently ignoring a supplied prop, or rendering both, is rejected.                                                     | `spec:AST-002` FR15 (never silently render a broken state); `architecture:public-component-api` INV3 | Accepted; jsdom evidence pending         |
-| FR8 | A hook that returns props for a trigger — `triggerProps` and `getTriggerProps` on `useLightbox`, `usePopover`, `useMenuHover`, and `useHoverCard` — follows hook conventions and is unchanged by this record. Those return-value names are NOT precedent for a component prop's name or shape. This record does not require a hook to grow a render prop, nor a component to republish its trigger props as a hook return. | DEC-4                                                                                                | Settled by DEC-4; no code change         |
+| ID  | Invariant                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | Basis                                                                                                | Verification state                       |
+| --- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | ---------------------------------------- |
+| FR1 | A component that lets a caller supply the control which opens its overlay MUST take that control as a render prop named `renderTrigger` (DEC-5): a function the component calls with one props object, whose returned element the component renders as given. The component MUST NOT wrap the returned element in an element of its own, and MUST NOT require a particular tag or a particular Astryx component.                                                                   | DEC-1; `spec:AST-002` FR4                                                                            | Accepted; jsdom evidence pending         |
+| FR2 | Spreading the handed-back props onto one element MUST be the whole integration. The object MUST carry the ref or anchor the overlay positions against, the `id` AR1 needs, every handler that opens, toggles, and closes the overlay from that control on the component's supported input paths (or the ref, where the component listens on the control itself), and the disclosure attributes of AR1. The object's type MUST be exported from the component's public entry point. | DEC-1; `architecture:public-component-api` INV1, INV5                                                | Accepted; jsdom evidence pending         |
+| FR3 | A caller-supplied control MUST NOT be taken as a `ReactNode` slot that the component renders inside an interactive element of its own. Callers routinely pass an interactive component, and that shape nests one interactive element inside another (AR2). A content slot rendered inside a component-owned control remains valid for non-interactive content and is unchanged.                                                                                                    | DEC-1; AR2                                                                                           | Accepted; jsdom evidence pending         |
+| FR4 | The caller's control MUST own a box. A component MUST NOT render it inside a wrapper with no box of its own (`display: contents`), and MUST NOT depend on such a wrapper where it paints or offsets a focus indicator on the trigger, or positions the overlay against the trigger's rect: there is no rect to anchor to and no box on which to paint. FR1 removes the need for any wrapper.                                                                                       | DEC-2; `architecture:layer-runtime` anchor contract                                                  | Accepted; real-browser evidence required |
+| FR5 | Hover, pressed, and every other pointer paint on the caller's control MUST remain the caller's own CSS. The component MUST NOT write paint onto an element it does not render. The component MUST publish the overlay's open state on the handed-back props as `aria-expanded`, so a caller styles the open state from the rendered attribute and no additional public API is added for it.                                                                                        | DEC-3; `spec:AST-002` FR1, FR2                                                                       | Accepted; jsdom evidence pending         |
+| FR6 | The prop's consumer documentation MUST show styling the open state from `aria-expanded` on the caller's control, and MUST state that a pressed look keyed to `:active` is not a substitute, because `:active` does not behave the same under a finger, and press paint follows `spec:AST-094` FR11's profiles instead.                                                                                                                                                             | DEC-3; no current core component styles off `aria-expanded`, so callers have no example to copy      | Accepted; documentation evidence pending |
+| FR7 | Where a component offers both a built-in control and this prop, exactly one control MUST render. The caller's control MUST win, identically in every presentation the component supports, and a development warning MUST fire; the component's own chrome for the replaced control MUST NOT render. Silently ignoring a supplied prop, or rendering both, is rejected.                                                                                                             | `spec:AST-002` FR15 (never silently render a broken state); `architecture:public-component-api` INV3 | Accepted; jsdom evidence pending         |
+| FR8 | A hook that returns props for a trigger — `triggerProps` and `getTriggerProps` on `useLightbox`, `usePopover`, `useMenuHover`, and `useHoverCard` — follows hook conventions and is unchanged by this record. Those return-value names are NOT precedent for a component prop's name or shape. This record does not require a hook to grow a render prop, nor a component to republish its trigger props as a hook return.                                                         | DEC-4                                                                                                | Settled by DEC-4; no code change         |
 
 ### Accessibility contract