yj dZddlZddlmZmZddlmZmZddeedefdZ dd d id d Z ej dd e dddS)uRead which OS window sits directly underneath the Hermes desktop window. The window list lives with the OS, so this tool round-trips through the gateway's blocking-prompt bridge — the same one `read_terminal` uses: tui_gateway emits ``window.read.request``, the desktop renderer asks its main process (which owns native window enumeration) and answers with ``window.read.respond``. This module is just schema + a thin dispatcher over the platform-injected callback. N)CallableOptional)registry tool_errorcallbackreturncz|tdS |}n)#t$r}td|cYd}~Sd}~wwxYw|stdS tjtj|dS#t t f$r(tjdt|idcYSwxYw)z@Return the window underneath the Hermes window as a JSON string.Nz>read_window_below is only available in the Hermes desktop app.z!Failed to read the window below: zCould not determine the window underneath (the desktop app did not answer, or window enumeration is unavailable on this system).F) ensure_asciitext)r Exceptionjsondumpsloads TypeError ValueErrorstr)rrawexcs >>> z "BBBz63s88,5AAAAAABs)  A?AA'B6B:9B:read_window_belowuIdentify the application window directly underneath (behind) the Hermes desktop window — what the user is working in behind this app. Returns JSON: {window: {app, title, bounds{x,y,width,height}, id}, frontmost: {app, title}, platform}. `title` may be empty when the OS withholds window titles (e.g. macOS without the Screen Recording permission — never prompted for, noted in `note`). Other Hermes windows are skipped: the nearest non-Hermes window is reported. Returns {error, platform} instead where the OS cannot enumerate windows at all (e.g. a Wayland session); `error` says what would fix it, so relay it rather than retrying. Metadata only; this never captures pixels or content of other windows.object)type properties)name description parameters desktop_uic Ht|dS)Nr)r)rget)argskws rr#Es5rvvj?Q?QRRRu🪟)rtoolsetschemahandleremoji)N) __doc__r typingrrtools.registryrrrrREAD_WINDOW_BELOW_SCHEMAregisterr$rr/s %%%%%%%%////////BBXh%7B3BBBB4  Q,   # R R  r$