docs(agents): 记录微信本人免配对主分支集成
This commit is contained in:
@@ -27,16 +27,18 @@ Accepted / implemented,2026-09-11 集成。产品范围、三端分工、创
|
||||
|
||||
## Personal WeChat Publication(2026-09-13 accepted / implemented)
|
||||
|
||||
- Published cloud agents expose a native personal WeChat panel: create/adopt account, local QR rendering, verification, self pairing/invitations, access revocation, enable/pause, route switch, disconnect, safe activity and failed-file retry.
|
||||
- Published cloud agents expose a native personal WeChat panel: create/adopt account, local QR rendering, login verification, direct use by the scanning owner, contact invitations, access revocation, enable/pause, route switch, disconnect, safe activity and failed-file retry. Creator self-pairing codes are removed, including stale recovery presentation; invited contacts still receive a complete invitation command.
|
||||
- Renderer uses typed Host operations. Main owns credentials, network, per-account durable original operations and file saving. Verification codes never enter the recovery journal; uncertain mutations require explicit recovery.
|
||||
- QR payloads are encoded locally. Account or Provider-generation changes clear transient state. Enable confirmation shows the actual published version, audience and task/daily budget, including zero.
|
||||
- Own WeChat conversations use dedicated Yuxi session endpoints for approval, stop/new session, complete history pagination and automatically refreshed deliverables. The creator cannot browse invited callers' content.
|
||||
- Scheduled result notification requires an explicit paired self target. Execution completion and WeChat delivery status remain distinct; retrying a failed file part does not run the model again.
|
||||
- The scanning owner's first message establishes their history and available notification conversation. Scheduled result notification requires an explicitly selected self target. Execution completion and WeChat delivery status remain distinct; retrying a failed file part does not run the model again.
|
||||
|
||||
Source `2e710db0fb512f276fda8ae8a3939d366b34a972`, [source task](../30-worklog/tasks/20260913-agentbus-channels-ml-3ec75b90.md). Final 81 focused tests, typecheck, production build and 2 Electron scenarios passed, with independent review PASS. Tests use local Host fixtures; real WeChat, billing, packaging and deployment acceptance remain pending.
|
||||
|
||||
## Evidence And Limits
|
||||
|
||||
The creator no-code change explicitly replaces the earlier pairing step. See [reviewed source task](../30-worklog/tasks/20260913-wechat-auto-self-ml-3679bce2.md): 64 focused tests, typecheck, build, scoped lint and an inspected Electron scenario passed; independent review passed. Main remains the network boundary and Yuxi/AgentBus establish identity. Compatible backend and client deployment is required; historical connections missing scanning identity need one reconnect. No real WeChat acceptance or installer was produced by this change.
|
||||
|
||||
源:WS `0f1fb8af`、Yuxi `1df0142`、MakeLore `303f262`;本仓库见 [源任务](../30-worklog/tasks/20260910-personal-agent-platform-d15b2559.md)。本批独立 Reviewer 最终 PASS。源验证包含 WS 113 passed / 1 skipped 和预算 PG 4 passed,Yuxi 1985 non-slow unit / 19 HTTP-存储 integration 及归档最后补丁 3 integration,MakeLore 39 unit / Renderer tsc / build / Electron 1 passed。模型授权/供应商及沙盒释放有明确替身;MakeLore Main 全仓保留 61 项既有类型诊断。
|
||||
|
||||
真实收费模型对账、完整服务/ARQ/provisioner 与重启、安装包/协议/跨设备、生产迁移和部署仍待验收。并行 OSS 替换与远程 Milvus 部署由各任务集成和验收;本决策不接受其尚未合入的存储实现。
|
||||
|
||||
Reference in New Issue
Block a user