{
  "_hint": "KiCad has NO log file and in GUI mode its errors go to DIALOGS, not stderr — so this is where a GUI failure reason lives. Read-only: nothing is clicked or raised. THREE channels, use all three: (1) this verb; (2) kicad_log_tail for what bypasses wxLog — crashes, asserts, stdio; (3) kicad_screenshot_all when the first two say nothing and the result is still wrong — the pixels have no preconditions and remain the floor under any automation loop. Dismiss with kicad_dismiss_dialogs (which DOES foreground, so caption first).",
  "_timeoutHint": "ab waits up to 130s for this verb before the request times out. If it's a long operation (cloud open / download / export), DON'T treat a timeout as failure — the work usually keeps running on the bridge. Poll `kicad_status` until it reports done.",
  "_userFocusRestored": false,
  "bridgeVersion": "0.9.349",
  "count": 0,
  "dialogs": [],
  "durationMs": 344,
  "error": "",
  "kicadVersionUsed": "10.0",
  "output": "",
  "schemaVersion": 1,
  "status": "ok",
  "statusVerb": "kicad_status",
  "success": true,
  "timeoutSeconds": 130,
  "windowSource": "ad:desktop_list_windows"
}