[httpsphl]

The owner asked to see the bot's mouse on their own screen, not only in the panel beside the chat (spec 24.9).

What changes

• The outline's window (feat(desktop): outline in the bot's color around the window it uses #184) now also draws the bot's cursor over the window in use. It is drawn with GDI, without antialiasing because of the see-through color key.
  • It is an arrow in the bot's color, outlined in white, with the bot's name in a pill beside it, plus "•••" while it types.
  • It glides in 350 ms to each action's point: the x and y of DesktopAction (feat(desktop): bot cursor on the desktop panel, and the panel opens by itself #182).
  • A ring in the bot's color grows where it clicked.
  • A 16 ms timer runs only while it moves.
• The daemon task carries the cursor: the bot's name, the last point in that window and the action kind.
  • Reading leaves it where it was.
  • Another window starts without one.
  • A new action shows right away, not at the next 250 ms tick.
• The owner's real mouse never moves for this. Everything stays click-through, and the outline stays right above the app in z-order.

Tests

• Unit tests: easing, and the cursor following the last action while reading leaves it in place.
• The real-window outline test still runs on CI. I did not run the window tests locally, because the owner is using the PC.

Manual

• Ask a bot to click something in Notepad or Chrome. Its arrow and name should glide to the control on the real screen and a ring should show on the click. Bring another window in front of the app and the cursor should be covered with the outline.