User interface functions for output, logging, and user interaction.

Context Warnings for Interactive UI

Interactive UI functions (confirm/1, choose/2, prompt/1) can cause deadlocks when called from certain contexts and must be wrapped appropriately.

GenServer Callbacks

Use UI.Queue.run_from_genserver/1 to prevent deadlocks:

def handle_call(:delete_item, _from, state) do
  confirmed = UI.Queue.run_from_genserver(fn ->
    UI.confirm("Delete this item?")
  end)
  # ...
end

Services.Globals.Spawn.async and Spawned Processes

Use UI.Queue.run_from_task/1 when tasks need to participate in an existing UI interaction:

task = Services.Globals.Spawn.async(fn ->
  UI.Queue.run_from_task(fn ->
    UI.confirm("Process this item?")
  end)
end)

Creating UI Components

Use UI.interact/1 to group multiple UI operations into a single atomic component:

def confirm_with_details(item) do
  UI.interact(fn ->
    UI.info("Item details: #{item.name}")
    UI.puts("Size: #{item.size}, Modified: #{item.date}")
    UI.confirm("Delete this item?")
  end)
end

Non-interactive functions (info/2, warn/2, error/2, puts/1, say/1) are safe to call directly from any context.

Interactive vs Non-Interactive Functions

Interactive (require context wrappers in GenServer/Task contexts):

• confirm/1 - waits for yes/no input
• choose/2 - waits for selection
• prompt/1 - waits for text input

Non-interactive (safe to call directly from any context):

• info/2, warn/2, error/2, debug/2 - just output
• puts/1, say/1 - just output
• interact/1 - groups operations but doesn't itself interact