Please address the comments from this code review:

## Overall Comments
- Consider using `mi.rcWork` instead of `mi.rcMonitor` so that `ensure_window_on_screen` keeps the client area within the usable desktop region and avoids moving content under the taskbar or other reserved areas.
- Since `ensure_window_on_screen` is called on every screencap, you could short‑circuit before the more expensive client/frame calculations (e.g., first check if the current window/client rect already lies within the monitor bounds) to reduce redundant WinAPI calls in the common case.

## Individual Comments

### Comment 1
<location path="source/MaaWin32ControlUnit/Screencap/HwndUtils.hpp" line_range="82-84" />
<code_context>
+        return false;
+    }
+
+    RECT monitor_rect = mi.rcMonitor;
+    int monitor_w = monitor_rect.right - monitor_rect.left;
+    int monitor_h = monitor_rect.bottom - monitor_rect.top;
</code_context>
<issue_to_address>
**suggestion (bug_risk):** Using rcMonitor instead of rcWork may place the client under taskbars or reserved areas.

If the goal is to keep the client visible to the user, this should likely use `mi.rcWork` so it respects the taskbar and other reserved areas. If you do intend to allow content under the taskbar, please document that explicitly and verify that downstream consumers are OK with potentially obscured regions.

```suggestion
    // Use the monitor work area so the client remains visible and is not placed
    // under the taskbar or other reserved areas.
    RECT monitor_rect = mi.rcWork;
    int monitor_w = monitor_rect.right - monitor_rect.left;
    int monitor_h = monitor_rect.bottom - monitor_rect.top;
```
</issue_to_address>

### Comment 2
<location path="source/MaaWin32ControlUnit/Screencap/HwndUtils.hpp" line_range="159-160" />
<code_context>
+    int new_window_w = new_client_w + frame_left + frame_right;
+    int new_window_h = new_client_h + frame_top + frame_bottom;
+
+    LogInfo << "Moving/resizing window to keep client area on screen" << VAR(new_window_x) << VAR(new_window_y)
+            << VAR(new_window_w) << VAR(new_window_h);
+
</code_context>
<issue_to_address>
**suggestion:** Logging every move/resize at info level may be noisy for frequent screencap calls.

Because this runs before every screencap, this log may generate excessive noise, especially at high capture rates or when the window frequently moves. Consider lowering the level (e.g., debug/trace) or only logging when the computed rect meaningfully changes from the last value to keep logs useful.

```suggestion
    LogDebug << "Moving/resizing window to keep client area on screen" << VAR(new_window_x) << VAR(new_window_y)
             << VAR(new_window_w) << VAR(new_window_h);
```
</issue_to_address>