守卫单语缺口：「内置共享规则表」口径规则只读英文页，三语的另两份表无人检查

[yinlianghui]

在实现 #790 + #791 时发现，作为观察记录立单，不在该 PR 里顺手改 —— 那次的守卫扩面已明确限定为 OWD 表（全对象集）与相关列表表（中文两页），把第三条规则一并扩掉属于判据变更。

现象

test/sharing-coverage.test.ts 有三条读文档的口径规则，全部读常量 SHARING_DOC（英文页）：

1. the built-in rules table lists exactly the shipped sharing rules
2. every documented rule states the object, access level and position it really grants
3. the related-list table tells the truth about each account child

#790 的 PR 把第 3 条按语言另立了一份（describe('the related-list table names the same account children on the Chinese pages')），并把 OWD 表守卫扩到三语全对象集。第 1、2 条仍然只看英文页。

content/docs/administration/sharing-and-security.zh-Hans.mdx:87-95 与 .zh-Hant.mdx:87-95 各有一份同样的九行内置共享规则表，规则名是英文（Account Team Sharing 等），但对象列与授予列是翻译过的（客户 / 客戶、编辑 / 編輯、读取 / 讀取）。今天这两份表逐条核对下来与 src/sharing/ 一致 —— 九条规则、对象、访问级别、岗位全对。

为什么现在不是活的缺陷

上面这句是实测：本单立单前把两份中文表与 src/sharing/index.ts 逐行比过，零漂移。所以今天没有读者会踩到假规则表 —— 这是休眠的覆盖缺口，按 observation-class 归类（finding，不带 pm:queue）。

它值得记下来的原因与 #725 一样：这一类缺陷在本仓历史上真的以中文页形态发生过（#791 的整页口径漂移、#592 漏掉的 | Events | 行都是），只是碰巧这张表干净。下一次有人增删一条 sharing rule，英文页会被守卫逼着改，两份中文表不会。

可选的修法

#790 落地的 PAGES 表已经是「按语言 authored 的 RegExp / 字面量」这一套基建，ROW_LABEL 里也已有全部 17 个对象的三语标签。所以扩第 1、2 条只需要：

• 规则名列：语言无关，直接复用；
• 对象列：查 ROW_LABEL[rule.object][locale]，已有；
• 授予列：新增一张很小的 ACCESS_WORD: Record<Locale, Record<'read' | 'edit', string>>；
• 岗位列：反引号里的岗位名语言无关，直接复用现有断言。

即一张三行的新 ledger，不引入新风格。

Related: #725（同形状，docs-drift.test.ts 的磁贴散文规则）、#791。

[os-sam]

Graded: promote → pm:queue. Coverage gap re-verified on origin/main, and it is still open.

PM seat repo:hotcrm (objectstack#10282), round 2, first-touch grading under the maintainer's standing authorisation of 2026-08-20 (verbatim 「finding 你可以自己定级」).

Premise re-measured on eef112b, rather than trusted from the card:

• test/sharing-coverage.test.ts:288 — describe('the admin docs describe the sharing the app actually ships') still opens with const doc = DOC(SHARING_DOC), and SHARING_DOC (line 51) is the English page alone. So rules 1 and 2 — the built-in rules table, and the object/access/position claims — remain single-locale.
• The locale infrastructure the card proposes reusing is present and has grown since: PAGES (line 520) now drives the OWD table (634), the related-list table on the Chinese pages (821), and a per-locale parent-derived-reach ledger (897), with a second PROFILE_PAGES ledger (1044) for claim wording.

So the gap is real, and the fix is genuinely the small one the card describes — a third ledger over machinery that already exists, not new machinery.

Why promote a gap that is measurably dormant today

The card is scrupulous that nothing is broken right now: both Chinese tables were compared row-by-row against src/sharing/ at filing and matched. Under the startup-focus principle (axis ④, this lane's primary filter) a dormant gap normally loses to real defects, so this deserves its reasoning stated rather than waved through.

It promotes on two grounds:

1. The defect class is not hypothetical here — it has fired repeatedly. sharing-and-security 的 zh-Hans / zh-Hant 停在 PR #699 之前：仍承诺「看得到父记录才看得到子行」，相关列表表还缺 Events #791 (a whole-page drift on the Chinese pages), Activity model: first-class meetings/events + call logging on every sales object #592 (a dropped | Events | row), docs-drift 的 **Name** tile 散文规则只在英文页开火——zh 页正文里的磁贴引用无人检查 #725 (the same shape in docs-drift.test.ts). The tables are clean today by luck of timing, not by construction.
2. The asymmetry is the actual defect. The English page is forced correct by a guard; the two Chinese pages are not. The next person to add or remove a sharing rule will be made to update one table and silently allowed to leave two stale — and this is a reference app whose documentation is part of the product it demonstrates. An exemplar whose security documentation quietly diverges from its shipped rules teaches every reader, human or AI, a wrong thing about the platform.

That is the "restore an invariant" shape, which the grading rules queue rather than hold.

Scope for whoever takes it

Rules 1 and 2 only, extended over the existing PAGES ledger — rule names are language-invariant, ROW_LABEL already carries all 17 objects in three locales, the position names are language-invariant inside backticks, and the one genuinely new thing is a small ACCESS_WORD map for the granted-access column (编辑/編輯, 读取/讀取). ⛔ Do not widen this into the tile-prose rules of #725 — same shape, different file, its own card.

Grading batch 2 continues with #806 and #837, not reached this round.

---

Generated by Claude Code