@lotics/ui 11.8.9 → 11.8.10

package/docs/ai_patterns.md

@@ -74,6 +74,22 @@ review; the human presses Send. The canvas template
 ([`tpl_dieline`](../examples/tpl_dieline.tsx)) uses it this way; while running the host swaps
 `Composer` for `AgentProgress` (same pill geometry, so it reads as a morph).
 
+## The trigger — a paid action is pressed exactly once
+
+A CTA that starts an agent run (or any paid/mutating action) must make the PRESS itself the
+transition — never leave a live button waiting on a network round-trip:
+
+- **Same-tick feedback.** On press, synchronously close the dialog / swap to the run surface
+  (`AgentRun` with its streaming state) so there is nothing left to click. A button that stays
+  pressable while an attach/start request round-trips invites double-fires — observed in
+  production as stacked paid runs.
+- **Single-flight in app code too.** Guard the handler with a ref (state alone races the
+  re-render): first press wins, later presses no-op until the flow settles.
+- **The SDK backstops runs, not workflows.** `useAgentRun().run()` is single-flight by default
+  (a duplicate call joins the in-flight run; `replace: true` is the deliberate restart) — but
+  `useWorkflow` calls are NOT deduped (rapid distinct calls are legitimate), so a workflow CTA
+  must disable itself (`loading`) while pending or a double-click writes twice.
+
 ## Show the work — `AgentRun`
 
 `AgentRun` (`@lotics/ui/agent_run`) is a live feed of the agent's work as a TIMELINE. The prop is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/ui",
-  "version": "11.8.9",
+  "version": "11.8.10",
   "type": "module",
   "exports": {
     "./tokens": "./src/tokens.ts",