@factorialco/f0-react 11.8.0 → 11.9.0

package/dist/component-status.js

@@ -4,7 +4,7 @@ import { useCallback as i, useEffect as a, useRef as o, useState as s } from "re
 import { jsx as c, jsxs as l } from "react/jsx-runtime";
 //#region \0virtual:f0-component-status-data
 var u = {
-	generatedAt: "2026-10-28T20:40:10.108Z",
+	generatedAt: "2026-10-29T00:29:53.980Z",
 	stats: {
 		total: 312,
 		byStatus: {

package/dist/experimental.d.ts

@@ -6184,7 +6184,7 @@ type F0ChatStatus = "connecting" | "ready" | "reconnecting" | "offline" | "error
  * wins, so a host with a poster passes `{ canSend: true }` and gets exactly
  * that. See `utils/capabilities.ts`.
  *
- * When no action survives, the message shows no react button and right-click
+ * When no action survives, the message shows no menu button and right-click
  * keeps the browser's menu.
  */
 type F0ChatCapabilities = {
@@ -6279,10 +6279,9 @@ type F0ChatSurface = "panel" | "page";
  * {@link F0ChatRuntime.toggleReaction}, which receives identical arguments from
  * all of them. */
 type F0ChatReactionSource =
-/** One of the most-used emoji: in the hover pill or the pill over the
- * right-click menu. */
+/** One of the most-used emoji, in the pill over the message menu. */
 "quickRow" |
-/** The full picker, opened from either pill's last button. */
+/** The full picker, opened from the pill's last button. */
 "menuPicker" | "existingPill" | "inlinePicker";
 /** How files reached the composer. Same story as {@link F0ChatReactionSource}:
  * {@link F0ChatRuntime.uploadFiles} cannot tell these apart. */