Please address the comments from this code review:

## Overall Comments
- The custom controller extra info is currently returned as a JSON string nested under the `info` field (e.g. Python `get_custom_info` -> `_c_get_info_agent` -> `CustomControlUnitMgr::get_info`), so consumers see `info` as a stringified JSON instead of a merged object; consider parsing and merging the custom info into the top-level `json::object` or updating the API/docs to reflect the actual structure.
- In `ControllerAgent::run_action`, `control_unit_->get_info()` is called twice per action (once before execution and once on completion) and the result is embedded in both notifications; if `get_info` can be expensive or has side effects, consider caching the result per action or only recomputing when needed.

## Individual Comments

### Comment 1
<location path="source/MaaCustomControlUnit/Manager/CustomControlUnitMgr.cpp" line_range="238" />
<code_context>
+{
+    json::object info;
+    info["type"] = "custom";
+    info["info"] = get_info_from_controller();
+    info["connected"] = connected();
+
</code_context>
<issue_to_address>
**issue (bug_risk):** Controller-provided JSON is stored as a raw string instead of parsed JSON, which makes `info["info"]` inconsistent with other controllers.

Here `get_info_from_controller()` returns a `std::optional<std::string>` that is assigned directly to `info["info"]`, so consumers will see a JSON string instead of an object, unlike other controllers whose `get_info()` returns structured `json::object`s. This will require special-casing custom controllers.

To keep the API shape consistent, either parse the returned JSON string before assigning (e.g. `info["info"] = json::parse(*opt);`) or, if you intentionally store a string, clearly document that `info["info"]` is JSON-encoded rather than a nested object.
</issue_to_address>

### Comment 2
<location path="test/python/binding_test.py" line_range="396-401" />
<code_context>
         assert isinstance(resolution, tuple), "resolution should be a tuple"
         assert len(resolution) == 2, "resolution should have 2 elements"

+        # 测试 info
+        info = controller.info
+        print(f"  info: {info}")
</code_context>
<issue_to_address>
**suggestion (testing):** Add tests for `CustomController.get_custom_info` / custom controller `info` integration

This only exercises the built-in debug controller. Since the PR introduces `CustomController.get_custom_info` that should be merged into the base `info`, please add a test with a simple custom controller overriding `get_custom_info`, and assert that `controller.info` contains both the base fields (like `"type"`) and the custom keys to verify the merge and callback wiring.

Suggested implementation:

```python
    # 测试 info
    info = dbg_controller.info
    print(f"  info: {info}")
    assert isinstance(info, dict), "info should be a dict"
    assert "type" in info, "info should contain 'type'"
    assert info["type"].startswith("dbg_"), "dbg controller type should start with 'dbg_'"

    # 测试 CustomController.get_custom_info / info 合并逻辑
    class _TestCustomController(CustomController):
        def get_custom_info(self):
            # 使用几个简单的自定义字段，便于在 info 中断言
            return {
                "custom_key": "custom_value",
                "answer": 42,
            }

    # 注意：这里假设 CustomController 的无参初始化是合法的，
    # 如有需要请根据实际构造函数调整参数（见 <additional_changes>）
    custom_controller = _TestCustomController()
    custom_info = custom_controller.info
    print(f"  custom info: {custom_info}")

    # 1. info 仍然应为 dict
    assert isinstance(custom_info, dict), "custom info should be a dict"

    # 2. 包含基础字段（例如 type）
    assert "type" in custom_info, "custom info should contain base 'type' field"
    assert isinstance(custom_info["type"], str), "custom info 'type' should be a string"

    # 3. 包含 get_custom_info 返回的自定义字段，验证 merge & callback wiring
    assert custom_info.get("custom_key") == "custom_value", "custom info should contain merged 'custom_key'"
    assert custom_info.get("answer") == 42, "custom info should contain merged 'answer'"

    # 测试输入操作
    dbg_controller.post_click(100, 100).wait()
    dbg_controller.post_swipe(100, 100, 200, 200, 100).wait()

```

）
    custom_controller = _TestCustomController()
    custom_info = custom_controller.info
    print(f"  custom info: {custom_info}")

    # 1. info 仍然应为 dict
    assert isinstance(custom_info, dict), "custom info should be a dict"

    # 2. 包含基础字段（例如 type）
    assert "type" in custom_info, "custom info should contain base 'type' field"
    assert isinstance(custom_info["type"], str), "custom info 'type' should be a string"

    # 3. 包含 get_custom_info 返回的自定义字段，验证 merge & callback wiring
    assert custom_info.get("custom_key") == "custom_value", "custom info should contain merged 'custom_key'"
    assert custom_info.get("answer") == 42, "custom info should contain merged 'answer'"

    # 测试输入操作
    dbg_controller.post_click(100, 100).wait()
    dbg_controller.post_swipe(100, 100, 200, 200, 100).wait()
>>>>>>> REPLACE
</file_operation>
</file_operations>

<additional_changes>
1. 确保在 `test/python/binding_test.py` 顶部导入 `CustomController`，例如：
   `from your_module_path import CustomController`
   将 `your_module_path` 替换为实际定义 `CustomController` 的模块路径。
2. 如果 `CustomController` 的构造函数需要参数（例如设备、连接信息等），请将
   `custom_controller = _TestCustomController()` 替换为带有正确参数的初始化调用。
3. 如果基础 `info` 字段中除了 `"type"` 还有其他需要保证存在的字段（例如 `"version"` 等），
   可以在该测试中追加对应的 `assert` 来进一步验证 merge 逻辑。
</issue_to_address>

### Comment 3
<location path="test/agent/agent_child_test.py" line_range="271-275" />
<code_context>
         assert isinstance(resolution, tuple), "resolution should be a tuple"
         assert len(resolution) == 2, "resolution should have 2 elements"

+        # 测试 info
+        info = controller.info
+        print(f"  info: {info}")
+        assert isinstance(info, dict), "info should be a dict"
+        assert "type" in info, "info should contain 'type'"
+
         # 测试基本输入操作
</code_context>
<issue_to_address>
**suggestion (testing):** Strengthen remote-controller `info` assertions to validate controller type or key fields

Currently this only checks that `info` is a dict with a `"type"` key. Since this goes through the remote agent path, please also assert something about the actual contents—for example, that `info["type"]` matches the expected debug controller prefix (e.g. starts with `"dbg_"`), or that a controller-specific field like `"image_count"` / `"record_count"` is present. This better verifies that `ControllerGetInfo` is correctly forwarded and that the structured payload survives the round-trip.

```suggestion
        # 测试 info
        info = controller.info
        print(f"  info: {info}")
        assert isinstance(info, dict), "info should be a dict"
        assert "type" in info, "info should contain 'type'"

        # info["type"] 应该是调试控制器类型前缀，例如 "dbg_*"
        assert isinstance(info["type"], str), "info['type'] should be a str"
        assert info["type"].startswith("dbg_"), "info['type'] should start with 'dbg_' for debug controllers"

        # 至少要包含一个控制器特定字段，验证结构化 payload 是否完整
        assert (
            "image_count" in info or "record_count" in info
        ), "info should contain at least 'image_count' or 'record_count'"
```
</issue_to_address>

### Comment 4
<location path="docs/en_us/2.3-CallbackProtocol.md" line_range="89" />
<code_context>
 - `uuid`: Unique identifier (string)
 - `action`: Action type (string)
 - `param`: Action parameters (object)
+- `info`: Controller information (object), see [MaaControllerGetInfo](2.2-IntegratedInterfaceOverview.md#maacontrollergetinfo)

 #### `Controller.Action.Succeeded`
</code_context>
<issue_to_address>
**nitpick (typo):** Consider fixing the comma splice in the `info` field description for better grammar.

"Controller information (object), see ..." is a comma splice. Consider changing to "Controller information (object); see ..." or "Controller information (object). See ..." for correct grammar.

```suggestion
- `info`: Controller information (object). See [MaaControllerGetInfo](2.2-IntegratedInterfaceOverview.md#maacontrollergetinfo)
```
</issue_to_address>