Notes
- Renders
<WaitForEvent event={id} output={schema}>internally. - Async waits show in
smithers_external_wait_async_pending{kind="event"}. - Delivering a signal does not resume a suspended run on its own. From the CLI, send the payload with
bunx smithers-orchestrator signal RUN_ID user-feedback --data '{...}'(the second argument is the signal name, which equals the<Signal>id), then resume the run withbunx smithers-orchestrator up workflow.tsx --run-id RUN_ID --resume true. This is the keeper-loop pattern from the CLI overview. - Run both commands from the workspace root, the directory that holds
.smithers/. The CLI resolves the run database (smithers.db) from the nearest.smithers/anchor walking up from the current directory, so a different working directory points at a different (or missing) database.