From b18073cb97cd44cc77b439ef21993280c1d58643 Mon Sep 17 00:00:00 2001 From: Yige Date: Sun, 6 Sep 2026 10:11:20 -0400 Subject: [PATCH] =?UTF-8?q?docs(wecom-assistant):=20=E8=A1=A5=E4=BD=BF?= =?UTF-8?q?=E7=94=A8=E8=AF=B4=E6=98=8E=E5=B9=B6=E9=87=8D=E6=96=B0=20pin=20?= =?UTF-8?q?/=20add=20USAGE.md=20and=20repin=20(#136)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## 中文 企业微信助手的市场详情页「使用说明」区此前为空。内容仓库 [`desirecore-agent/wecom-assistant@047928a`](https://github.com/desirecore-agent/wecom-assistant/commit/047928afe1b46493fc48bda7d37031d6a3edd725) 新增 `USAGE.md`，本 PR 把条目重新 pin 过去。 ### 为什么要写这两条 它们都是**装之前**该知道、且**装完也改不了**的边界，正是 `USAGE.md` 的定位（ADR-143：与 `fullDesc` 分开，不进模型上下文）。 **1. 群聊历史目前仅对 ≤10 人企业开放。** 官方错误码 `853001` 的释义原文如此。实际触发返回相邻的 `853006`： ``` errcode: 853006 errmsg: this tool is not available for your corporation ``` 措辞是 **for your corporation**，不是「机器人未开通某品类」——所以让用户去找管理员开通品类是无效动作。本机实测复现，同一凭证下其余 12 个服务域全部正常，`chat` 是唯一被拒的域。上游 `WecomTeam/wecom-cli` #106 / #107 / #132 三个 issue 都在追这件事，截至提交时全部 OPEN、官方未回复。 **2. 同一条命令在不同规模的企业行为不同，而且不报错。** 上游维护者在 issue #64 确认：≤10 人「小团队模式」机器人以**授权用户身份**调用、继承其文档权限；>10 人「企业模式」机器人以**独立身份**调用、不继承。后果是同事分享给你的文档，小公司读得到、大公司读同一份返回 `851003`。这不是故障，但不写出来必然被当成故障反复重试。 顺带记入第三条与规模无关的边界：`wecom-cli identity whoami` 返回原文「只能写入或修改机器人创建或拥有的数据」——这是邮件署名固定为「XXX的机器人」、用户对助手所建文档反而没有管理权的根因。 ### 条目改动 pointer 条目的 `USAGE.md` 由客户端从内容仓库**按 pinned ref** 抓取（`sync/market.ts` 的 `pointerUsage` ← `code-repo/file-fetcher.ts`），所以只推内容仓库不改 ref 的话客户端看不到。四处一起改，保持 ADR-137 证据链自洽： | 字段 | 旧 | 新 | | --- | --- | --- | | `entry.source.ref` | `665ab1d2` | `047928a` | | `compliance.reviewedRef` | `665ab1d2` | `047928a` | | `compliance.reviewedAt` | 2026-09-04 | 2026-09-06 | | `timestamps.reviewedAt.value` | 2026-09-04 | 2026-09-06 | | `timestamps.catalogUpdatedAt.value` | 2026-09-04 | 2026-09-06 | `releasePublishedAt` **不动**——版本仍是 1.0.0，本次只增文档。 已核对：`reviewedRef === source.ref`、`timestamps.reviewedAt === compliance.reviewedAt`、`availability: installable`、`license.state: known`、compliance 五项必填齐全、ref 为 40 位 SHA、`repoUrl` 在官方前缀内。 ### 证据等级 | 结论 | 来源 | | --- | --- | | `853006` 错误原文与触发条件 | 本机实测复现 | | 「仅对 ≤10 人企业开放」 | 官方错误码 `853001` 释义 | | 小团队 / 企业模式身份差异 | 上游 issue #64 维护者确认 | | 「只能写入机器人拥有的数据」 | `identity whoami` 返回原文 | | 群聊 7 天限制 | `chat messages list` 的 `begin_time` 字段 schema | **未核实**：`853006` 的具体判定标准（是否严格按人数、有无灰度名单）与开通路径，官方未公开、上游 issue 未获回复。`USAGE.md` 里已如实标注。 ### 追加：一并修正 docs 的 853006 归因 同一 ref 里还带了内容仓库 [`047928a`](https://github.com/desirecore-agent/wecom-assistant/commit/047928afe1b46493fc48bda7d37031d6a3edd725) 的一处事实修正。原 docs 把 `853006` 写成「机器人未开通『群聊会话』品类」，并给出 「要让它可用：为机器人开通群聊会话品类」——**这是让用户去做一件做不成的事**。 改了 6 处（`04-群聊历史` 四处、`README` / `01-快速开始` / `99-风险与确认` 各处）， 只纠正群聊这一处的归因，**不动「能力按品类逐项开通」这条通则**——那条对 `850002` 依然成立。技能侧（`wecom-shared` / `wecom-workflows` / `wecomcli-message`）本就写的是 「企业级不可用」，本次是让 docs 与技能口径一致。 --- ## English The agent detail page's "Usage" section was empty for the WeCom assistant. The content repo now carries a `USAGE.md`; this PR repins the listing to it. It documents two limits that a reader needs **before** installing and cannot change afterwards: 1. **Chat history is currently limited to corporations of 10 people or fewer.** Official error `853001` states this; the actual response is `853006 this tool is not available for your corporation` — the wording is *corporation*, not *bot*, so asking an admin to enable a bot capability is a dead end. Reproduced locally; all 12 other service domains work under the same credential. Upstream issues #106 / #107 / #132 all remain OPEN with no official response. 2. **The same command behaves differently by corporation size, without erroring.** Per the upstream maintainer in issue #64, bots in ≤10-person "small team mode" call **as the authorizing user** and inherit their document permissions; in ">10 person" enterprise mode they call **under their own identity** and do not. A doc shared with you is readable in a small company and returns `851003` in a large one. A pointer listing's `USAGE.md` is fetched from the content repo **at the pinned ref**, so `source.ref` and the ref-bound compliance evidence are updated together to keep the ADR-137 chain self-consistent. `releasePublishedAt` is unchanged — still 1.0.0, docs only. --- agents/wecom-assistant/catalog-metadata.v1.json | 10 +++++----- agents/wecom-assistant/entry.json | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/agents/wecom-assistant/catalog-metadata.v1.json b/agents/wecom-assistant/catalog-metadata.v1.json index 0b329e4..bde18d0 100644 --- a/agents/wecom-assistant/catalog-metadata.v1.json +++ b/agents/wecom-assistant/catalog-metadata.v1.json @@ -36,7 +36,7 @@ "timestamps": { "catalogUpdatedAt": { "state": "known", - "value": "2026-09-04", + "value": "2026-09-06", "precision": "day" }, "releasePublishedAt": { @@ -46,7 +46,7 @@ }, "reviewedAt": { "state": "known", - "value": "2026-09-04", + "value": "2026-09-06", "precision": "day" }, "upstreamObservedAt": { @@ -59,7 +59,7 @@ "content": { "kind": "git", "url": "https://github.com/desirecore-agent/wecom-assistant.git", - "ref": "665ab1d2ca35155e60a10a8fb58ab0a3baef0e49" + "ref": "047928afe1b46493fc48bda7d37031d6a3edd725" } }, "governance": { @@ -82,8 +82,8 @@ "compliance": { "licenseEvidencePath": "LICENSE", "noticePath": "NOTICE", - "reviewedRef": "665ab1d2ca35155e60a10a8fb58ab0a3baef0e49", - "reviewedAt": "2026-09-04", + "reviewedRef": "047928afe1b46493fc48bda7d37031d6a3edd725", + "reviewedAt": "2026-09-06", "reviewedBy": "yi-ge", "upstreamEndorsed": true } diff --git a/agents/wecom-assistant/entry.json b/agents/wecom-assistant/entry.json index 1b71876..1668b50 100644 --- a/agents/wecom-assistant/entry.json +++ b/agents/wecom-assistant/entry.json @@ -35,6 +35,6 @@ "kind": "git", "repoUrl": "https://github.com/desirecore-agent/wecom-assistant.git", "repoBranch": "main", - "ref": "665ab1d2ca35155e60a10a8fb58ab0a3baef0e49" + "ref": "047928afe1b46493fc48bda7d37031d6a3edd725" } }