[httpsphl]

What

The platform part of D4 (spec 24.7). Nothing calls it yet; the tools and the per-app option come in D4b.

• real_click, real_type and real_press, using SendInput:
  • Bringing the window to the front. An empty mouse move first makes Windows let the daemon call SetForegroundWindow. A minimized window is restored.
  • Checks before every step. The foreground window, up to its root, must be the app's. For a click, the window under the point (WindowFromPoint) must be the app's too. Otherwise nothing is sent, and the tool says the window is not in front or is covered.
  • Locked screen. No foreground window, or SendInput sending less than asked, means the screen is locked or takes no input.
  • Where clicks land. Either the center of a control, from UI Automation's BoundingRectangle (sessions are now per-monitor DPI aware, so the numbers are real pixels), or a point of the window's picture as fractions of its DWM frame. The move is absolute across all screens.
  • Typing uses Unicode (KEYEVENTF_UNICODE), so the keyboard layout does not matter. A newline is Enter.
• The owner takes over. Low-level mouse and keyboard hooks run only during the action, on a thread with their own message queue, and spot input not marked as injected, which is the owner's. The bot stops at once.
• Keys by name (keys.rs, pure code with tests): Enter, Tab, Ctrl+S, Shift+Tab, F5, letters and digits, with Ctrl, Alt and Shift.
  • Refused: the Windows key, Alt+Tab, Alt+Esc, Ctrl+Esc, Ctrl+Shift+Esc and Ctrl+Alt+Del.
  • Alt+F4 is allowed: it closes the app's window, as it would for the owner.
• Owner idle time (spec 24.8) now leaves the bot's own input out.
• Readings keep each control's place on the screen (rect). It is not shown to the bot.
• Spec 24.7 is updated.

Checks

• cargo fmt and clippy -D warnings pass. Desktop lib tests pass (27 here).
• Real input tests: these move the cursor and type, so they only run with BOTLOFT_REAL_INPUT_TESTS=1. CI sets it on the Windows runner, where nobody sits at the desktop. I have not run them locally, because that would move the owner's mouse.
  • Click a field, press Ctrl+A, type, read the new value.
  • Click Save and see the title change.
• The test that every control has its place on the screen runs everywhere.
• Not testable automatically: the owner's input stopping the bot. Any input a test sends is marked as injected, so it is a manual check, listed in spec 19.