[objectstack-fleet]

Requested by Bill · project thread

domain:server#2 · os-bill · session_01Utp6Cai5CRdAs4u9gTipWU

Refs #30512 — package 3 of 11 (@objectstack/service-mailbox). The card stays open: the last PR of the series flips the bundle check to the platform locale table.

Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么： 邮箱三个对象（sys_mailbox、sys_mail_message、sys_mail_association）的名称、字段、选项、帮助文字和视图名补上 7 种语言：繁体中文、阿拉伯语、法语、巴西葡萄牙语、俄语、德语、韩语，共 11 种，与平台语言表一致。
• 为什么改： 平台语言表（Platform locale table (ruling F of #29349): one list of 11 languages in spec, complete on every surface #29428 裁决 F）要求每个界面带齐 11 种语言；这是第 3 期按包补齐的第 3 个包（75 条）。
• 风险与回滚： 只加翻译数据和注册行，不动逻辑、schema、接口；原有 4 种语言一字未改；无新的 stale-fill 巧合，基线未动。回滚即撤 PR。
• 先看： src/translations/index.ts（按表标签注册，zh-CN 在 zh-Hant 前），再抽看 ar.objects.generated.ts。
• 两分钟验证： node scripts/check-i18n-bundles.mjs 输出 services/service-mailbox in sync，node scripts/check-i18n-stale-fill.mjs 退出 0。
• 需要你做的： 无，席位落地。

What changes

• Seven new locales for the mailbox objects under the platform locale table's tags (zh-Hant, ar, fr, pt-BR, ru, de, ko): each a TAG.objects.generated.ts with all 75 leaves plus its TAG.source-hashes.generated.ts, written by the repo's own os i18n extract --fill=default --source-hashes and served through withSourceFallback like the existing three. zh-CN stays ahead of zh-Hant in index.ts.
• The extract command in scripts/i18n-extract.config.ts lists the seven tags and its merge baseline imports the seven bundles, so check:i18n covers them from this PR on.

Acceptance notes

• Quality bar ([Decision] Repeater row-property localisation: 604 catalog leaves across four locales — who authors the translated copy? #17508 / PR feat(spec): a repeater property panel names its columns in every locale, not only English #19345): every leaf written for the reader; placeholders, code spans and identifiers byte-identical, checked mechanically per leaf against en. Arabic is RTL prose with identifiers left in Latin script.
• Leaves equal to English, on purpose: the RFC 5322 header names Message-ID, In-Reply-To, References, Sender, Reply-To and the IMAP term UIDVALIDITY, in every locale, exactly as zh-CN already keeps them (a user matching a raw header needs the header's own name). Beyond those, native cognates only: fr Cc, Association, Message; pt-BR Cc; de Cc, Name. The extractor records each as a source copy (zh-Hant/ar/ru/ko 6 entries; pt-BR 7; de 8; fr 9).
• No cross-locale coincidence: check:i18n-stale-fill passes with the baseline untouched.

Verification

Package suite, typecheck, build (verify lock)

turbo build (12-package i18n closure incl. @objectstack/service-mailbox): 63 tasks successful, exit 0
pnpm --filter @objectstack/service-mailbox test && typecheck
 Test Files  10 passed (10)
      Tests  152 passed (152)
os-verify-lock: VERDICT command-exit 0

i18n gates

node scripts/check-i18n-bundles.mjs
  services/service-mailbox       in sync
check-i18n-bundles: OK (10 package(s) — all bundles in sync, no undeclared authoring keys).   EXIT 0
node scripts/check-i18n-stale-fill.mjs
check-i18n-stale-fill: OK (11 bundle set(s) — no new stale fills, 1 baselined).               EXIT 0
  (the 1 baselined entry is #30586's webhooks plural, already on main; none added here)

Derived gate families at head 34c094b (dispatch-gates --commands, reconciled with --ran)

dispatch-gates --ran: 56 derived famil(ies) accounted for — 56 run, 0 NOT-MEASURED (a DERIVED zero). Every family exit 0,
including pnpm check:i18n and pnpm check:i18n-stale-fill. Run at 1c191347 (base 2ffdb649); the head 34c094b3 is the same
tree re-based onto main 4831d500 after #30586 merged, re-checked there: check:i18n in sync, check:i18n-stale-fill OK.
eslint on the changed .ts files: exit 0 · check-nul-bytes: exit 0
changed lines 1481 (+1480 / -1), 17 files: under the 3000-line human-merge threshold

Full record: the seat's project folder, server-seat2/30512/gates-mailbox-ran.txt.

Dogfood: not run — content-only package PR, no ! in the title and no (narrowing) arm (dispatch order: package suite + check:i18n + typecheck suffice).

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/service-mailbox, touching 18 documentable anchor(s).

1 hand-written doc(s) NAME something this change touched and may need an implementation-accuracy re-verification:

• content/docs/permissions/system-context.mdx (via sys_mail_association (symbol, a field of const object arObjects; a field of const object deObjects; a field of const object frObjects; a field of const object koObjects; a field of const object ptBRObjects; a field of const object ruObjects; a field of const object zhHantObjects), sys_mail_message (symbol, a field of const object arObjects; a field of const object deObjects; a field of const object frObjects; a field of const object koObjects; a field of const object ptBRObjects; a field of const object ruObjects; a field of const object zhHantObjects))

What this run could not see

• the SDK route bridge reached 61 of 219 client-bound route-ledger rows — the other 158 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 158: 0 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 55 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 103 are undecided (no in-repo declaration, on a ledger that has other in-repo registrars — absence and an unreadable spelling are not distinguishable here). The rows themselves: node scripts/docs-audit/affected-docs.mjs --bridge-coverage
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 1 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 4831d5006ded46c123075c43b400c50bfea7d32d → packageMentionDocs.

Which tree this was computed on

This run read content/docs from 3aef68c48777b514fba887ce7a04b2b4fb3e23b6 — the merge of head 34c094b34e65020c225d57819c79e0d533b56016 into base 4831d5006ded46c123075c43b400c50bfea7d32d, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin 3aef68c48777b514fba887ce7a04b2b4fb3e23b6 && git checkout 3aef68c48777b514fba887ce7a04b2b4fb3e23b6
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin 4831d5006ded46c123075c43b400c50bfea7d32d 34c094b34e65020c225d57819c79e0d533b56016 && git checkout -B drift-repro 4831d5006ded46c123075c43b400c50bfea7d32d && git merge --no-ff 34c094b34e65020c225d57819c79e0d533b56016

node scripts/docs-audit/affected-docs.mjs --json 4831d5006ded46c123075c43b400c50bfea7d32d

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

Advisory only, and a precision-first one (#9192): a page is listed because it names a
symbol, wire route or SDK method this diff touched — not because it mentions a changed
package. Each row says which anchor put it there, so a wrong row is reportable rather than
merely annoying. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs 4831d5006ded46c123075c43b400c50bfea7d32d → pass the list as
args.docs, on the commit named under Which tree this was computed on.

[objectstack-fleet]

domain:server#2 · os-bill · session_01Utp6Cbvcmv8YWFhFJwzjKL

维护者速读

• 改了什么： 邮箱相关对象（邮箱、邮件、邮件关联等）补齐 7 种语言：繁體中文、阿拉伯语、法语、巴西葡语、俄语、德语、韩语，按平台语言表的标签注册，原有 4 种不动。
• 为什么改： 平台语言表定了 11 种语言（Platform locale table (ruling F of #29349): one list of 11 languages in spec, complete on every surface #29428 裁定 F），i18n phase 3 (platform metadata and built-in emails): extraction and bundle checks read PLATFORM_LOCALES; backfill the seven missing locales #30512 按包补齐，这是 11 个包中的第 3 个。
• 风险与回滚： 只加翻译内容和注册行，不改行为；没有翻译的请求照旧回落英文。回滚即撤本 PR。
• 先看： packages/services/service-mailbox/src/translations/index.ts 的注册行，再挑一种语言的 *.objects.generated.ts。
• 两分钟验证： pnpm --filter @objectstack/service-mailbox test。
• 需要您做的： 无，席位经合并队列落地（非受管面，1481 行，非 BREAKING）。
• 席位意见： ACCEPT。席位抽查了韩语和繁中译文，术语和已有三种一致；UIDVALIDITY、RFC 头字段名按 zh-CN 惯例保留原文，合理。

席位核对 — ACCEPT · domain:server#2 · head 34c094b34e65020c225d57819c79e0d533b56016

• 形态: draft, author objectstack-fleet[bot] (relay pr_create), no assignee, no review request; 17 files, +1480 −1; check-governed-merges --pr 30606: NOT governed, 1481 lines ≤ 3000. Title has no !. Refs #30512 (package 3 of 11; the card stays open).
• Review face: TIER_DEFAULT (Clause-②: no: translated content for locales the platform table already declares, plus registration lines), written here by the seat.
• Seat rulings held: table tags for the new files; existing zh-CN / ja-JP / es-ES untouched; zh-CN ahead of zh-Hant, as in packages 1–2. No stale-fill baseline entry.
• Seat read: index.ts and scripts/i18n-extract.config.ts register the seven bundles and their source hashes (existing check:i18n covers them; no new gate). Spot check: ko (메일함 / 동기화 폴더 / 마지막 동기화 UID), zh-Hant: consistent terms; UIDVALIDITY and RFC header names kept as written, matching the zh-CN convention; placeholders and quoted examples preserved.
• Dev readings (34c094b3): package tests 152/152, typecheck, check:i18n green; derived gates 56, all exit 0, 0 NOT MEASURED. Content-only package PR: full dogfood owed on the last PR of the series, per the order. os-dev-report 6665419818.
• 门禁 check-runs: in progress at ACCEPT; the seat queues once every check is green or an expected skip.
• 落地条款: Refs i18n phase 3 (platform metadata and built-in emails): extraction and bundle checks read PLATFORM_LOCALES; backfill the seven missing locales #30512. Ordinary queue landing by this seat: pr_ready + automerge_enable on this head; the card ticks service-mailbox when it merges.