Fix Enterprise WeChat workbench enable_webview_click null handling

[Copilot]

The enable_webview_click setting in Enterprise WeChat custom workbench was not working properly when H5 elements inside the webview needed to capture click events. The issue occurred because null Boolean values were being serialized as "enable_webview_click": null in the JSON payload instead of being omitted entirely.

Problem

When enableWebviewClick or hideTitle Boolean fields were null in WxCpAgentWorkBench, they were being serialized as explicit null values in the JSON:

{
  "webview": {
    "enable_webview_click": null,
    "hide_title": null
  }
}

This caused the WeChat Enterprise API to not properly handle the webview click functionality, preventing H5 element click events from being captured even when the setting appeared to be configured correctly.

Solution

Added null checks for Boolean fields in both handle() and handleBatch() methods, following the same pattern already used for replaceUserData:

if (this.enableWebviewClick != null) {
  webview.addProperty("enable_webview_click", this.enableWebviewClick);
}
if (this.hideTitle != null) {
  webview.addProperty("hide_title", this.hideTitle);
}

Now when these fields are null, they are omitted from the JSON entirely, allowing the WeChat API to apply proper defaults. When explicitly set to true or false, they work as expected.

Fixes #3697.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.