[zhuangjianguo]

Requested by Steedos · project thread
Fixes #384
Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么:删除 ja/de/es/fr/ko 五个语言的全部 50 个译文页(每语言 10 页,全部过时);五个语言的 configure/permissions/meta.<locale>.json 补上 hierarchy-visibility,与英文 meta.json 的 pages 完全一致,译名标题保留。
• 为什么改:其他语言分阶段计划的第 0 阶段(2026-10-29 09:44Z 维护者同意)。过时译文比缺失更糟:缺失时显示正确的英文,过时时显示英文已不再声称的内容。
• 风险与回滚:只删译文、改 5 个侧栏文件,不动 en、zh-Hans、zh-Hant 和代码;这些页面回退为英文并显示「尚未翻译」提示。回滚即 revert 本 PR。
• 先看:content/docs/configure/permissions/meta.ja.json(其余四个同改)。
• 两分钟验证:打开 /ja/docs/configure/storage,正文为英文、界面为日文、顶部有未翻译提示;/ja/docs/configure/permissions/hierarchy-visibility 在侧栏「権限」下可见。
• 需要你做的:无,席位落地。

What changes

Files	Change
50 × content/docs/**/*.{ja,de,es,fr,ko}.mdx	Deleted. The same 10 pages in each locale: build/ai-skills, build/interface/views, build/marketplace, configure/api-access, configure/authentication, configure/permissions/permission-sets, configure/permissions/record-access, configure/storage, configure/system-settings, configure/webhooks. Every one was stale on d10d817.
5 × content/docs/configure/permissions/meta.{ja,de,es,fr,ko}.json	pages gains hierarchy-visibility between record-access and field-level-security, so it equals the English meta.json. The translated title stays.

The other 50 five-locale meta.*.json files already had pages equal to English and are untouched. Nothing in en, zh-Hans, zh-Hant or apps/ changes. A deletion is the one locale change a human PR may make (AGENTS.md, Translation workflow step 3), and the meta edit removes a sidebar gap rather than adding a translation.

Tests

Content-only diff. Local gates on c60f8aa:

• check-translations: ja, de, es, fr, ko each 0 stale, 98 missing, 0 guide-stale; zh-Hans 0/0/0; gate passed.
• check-translation-ownership --files <name-status>: 55 translation artifacts, 0 other files (reports only while TRANSLATION_BOT_LOGIN is unset).
• check-translation-output --files: no findings, and 0 pre-existing findings left in the corpus (the ~85 old ja/de/… findings lived in the deleted files).
• gen-zh-hant --check clean (115 files), check-doc-samples, turbo run type-check, build, test, check-locale-surface, check-positioning, check-search-locales all green.
• Rendered with next start: /ja/docs/configure/storage and /ja/docs/configure/permissions/hierarchy-visibility (desktop 1280) and /de/docs/configure/webhooks (mobile 390) return 200 with html lang set to the locale, English page content, the locale's chrome and the "not yet translated" banner; the ja sidebar lists Hierarchy Visibility under 権限.

Acceptance notes

• Phase 1 (ja entry path, ~20 pages, on the translation routine) follows as its own card once this lands.

---

Generated by Claude Code

[objectstack-fleet]

席位核对 · ACCEPT · 2026-10-29T09:54Z · session_01QsR2jTaZ2GeyfjANMwstiw · seat repo:docs.objectos.ai#1

1. Shape. Draft PR against main d10d817, head c60f8aa. 55 files, all under content/docs: 50 deletions (D) of *.{ja,de,es,fr,ko}.mdx and 5 edits (M) to configure/permissions/meta.{ja,de,es,fr,ko}.json. The body says Fixes #384. Claim 6493463626, branch claude/project-thread-fnk6ro. The seat's --name-status read finds no path outside the five locales.
2. Content. The deletions are the 10 stale pages per locale that Other locales, phase 0: delete the 50 stale ja/de/es/fr/ko pages so readers get correct English, and sync the locale sidebars to the English page lists #384 names. Each meta edit only inserts hierarchy-visibility between record-access and field-level-security, so the pages array now equals the English one. The other 50 five-locale meta files already matched English.
3. Gates, seat re-run at c60f8aa. check-translations: ja, de, es, fr and ko each at 0 stale, 98 missing (fallback to English). zh-Hans stays at 0/0. Check-runs: build success · Node floor success · Ownership & freshness success. The dev's rendered check of /ja/docs/configure/permissions/hierarchy-visibility shows English content with ja chrome, the untranslated banner, and the new sidebar entry.
4. Landing. Tier none. This is phase 0 of the maintainer-approved locale plan (09:44Z). It goes through the merge queue under the standing go-ahead, serially. The post-merge live smoke covers the localized routes.