批处理中没执行的分支输出，测试环境与线上环境返回值不一致

批处理中一个注册分支会返回`{code, msg, data}`的数据
当没走这个分支时，批处理输出预期得到的register_reponse_list应该是
```
[
null,
null,
...
]
```

测试也是这个结果，但是通过api调用时，得到的输出却是
```
[
{"code": null, "msg": null, "data": null},
{"code": null, "msg": null, "data": null},
...
]
```

API返回的debug_url打开看到的也是和测试的一样的结果，但是API的结构就是不一样

调试结果

API结果

Start by locating the batch-processing registration branch and comparing its test output with the API response path. Reproduce the case where the branch is skipped, then trace why the API changes null entries into objects. Done means the API response matches the expected list of null values, with tests covering both paths.

Written by the indexing model from the issue text.