Plugins can draw pressable buttons that fire a new press event back to the plugin.
Button elements and the ui.press event are fully built, but whether plugin-drawn UI is reachable is unresolved in this build.
What's wrong with this entry?
A Button element joins the plugin drawing vocabulary alongside Box, Text and span, written as <Button key label onPress> with both props required as strings and the label length capped. The terminal renders it as an interactive [ label ], and pressing one dispatches a new ui.press event through the owning plugin's chain, subject to a handler-budget timeout. Neither the event nor the element exists in 2.1.246. Whether plugin-drawn UI is reachable at all depends on the plugin render API's own gate, which is not resolved in this build.
- Each button handler is stamped with a plugin and handle address and held per module across redraws.
- A press whose handle is no longer held is logged and ignored rather than dispatched.
- Validator, renderer and dispatch are all wired, so nothing in the button path itself is switched off.
Button props must be { key, label }, both strings, ui.press
Strings lifted out of the shipped bundle, so the claim above can be checked against them.