admin/isphere-ai-bridge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify rpa fallback priority

Browse Source
This commit is contained in:
zhaoyilun
2026-07-12 01:29:07 +08:00
parent 341f08b7be
commit 0bb07c7754
5 changed files with 24 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/go-mcp-runbook.md
View File

@@ -563,6 +563,7 @@ Current short answer:
- 已完成：搜索联系人、搜索群组、收消息基础读取、收文件列表。
- 可预览：发消息 preview、发文件 preview。
- A-route/RPA 是备选兜底，不是主线；主线仍是 B-route running-client sidecar / in-process connector / existing API。
- A-route 已具备 UI 动作能力：显式配置后可以对聊天窗口写入文本并点击发送按钮；本地还可打开真实离线 `frmP2PChat` 验证窗口/输入框/按钮定位。
- 阻断：在线业务送达、真实文件下载、生产发文件。离线点击不等于服务端发送成功。
@@ -577,7 +578,7 @@ They are generated under ignored `runs\` and are not committed.
## 18. A-route UIA send connector
A-route is the UI Automation fallback for text sending when the B-route sidecar cannot be tested. It is function-first: there is no human approval ID gate inside the connector. The digital employee layer is responsible for deciding when to call production mode.
A-route is the UI Automation fallback for text sending when the B-route sidecar cannot be tested. It is function-first, but it is not the primary architecture. Prefer B-route running-client sidecar / in-process connector / existing API evidence whenever that route is available. There is no human approval ID gate inside the connector; the digital employee layer is responsible for deciding when to call production mode.
Local verification uses a synthetic WinForms window: