docs(zh-Hant): name the Setup app in English where it had no arrow

[os-sales]

Fixes #1538

Seven sites on five zh-Hant pages spelled the Setup app 設定 with no arrow. Every replacement is the label the page's English twin already uses, taken verbatim rather than translated back. A denial stays a denial — only the app name changes.

The seven sites, with the twin string each one took

site	before	after	English twin
administration/sandbox-and-releases.zh-Hant.mdx:44	「不是本租戶設定裡的某一頁；設定裡唯一與雲相關的入口是 Setup → Cloud Connection」	「不是本租戶 Setup 裡的某一頁；Setup 裡唯一與雲相關的入口是…」	"not a page inside this tenant's Setup; the only cloud entry Setup ships is Setup → Cloud Connection"
administration/sandbox-and-releases.zh-Hant.mdx:155	「把團隊指向儲存庫，而不是設定頁。」	「把團隊指向儲存庫，而不是 Setup。」	"Point your team at the repository, not at Setup."
reference/performance-and-limits.zh-Hant.mdx:297	「設定裡真正提供的是 Setup → System Overview」	「Setup 裡真正提供的是…」	"What Setup does ship is Setup → System Overview"
reference/security-and-compliance.zh-Hant.mdx:75	「設定裡沒有 SCIM 頁面。」 (whole sentence bolded)	「Setup 裡沒有 SCIM 頁面。」	"Setup ships no SCIM screen."
administration/setup.zh-Hant.mdx:112	「不在任何設定畫面上」	「不在任何 Setup 畫面上」	"not on a Setup screen"
service/sla-and-escalation.zh-Hant.mdx:33	「不在任何設定頁面上」	「不在任何 Setup 頁面上」	"The matrix lives in the hook rather than on a Setup screen"
service/sla-and-escalation.zh-Hant.mdx:162	「不在任何設定頁面上」	「不在任何 Setup 頁面上」	"not on a Setup screen"

Three of the seven were self-contradicting inside a single sentence, spelling the app 設定 and then citing a path through it in English on the same line.

The three judgement-call lines resolved the same way: change

administration/setup.zh-Hant.mdx:112 and service/sla-and-escalation.zh-Hant.mdx:33 / :162 read as generic ("any settings screen") on their own, and #1538 left them open on purpose. All three twins settle it: each writes a Setup screen with a capital S, on pages whose neighbouring sentences use the same word as the app (There is no Setup → Lead Settings screen, there is no Setup → Opportunity → Stages page, Neither recipient list is configurable on a Setup screen). The generic sense is spelled differently in the same files and is left alone — the twin of 「租戶級的營業時間設定」 is lowercase "no tenant business-hours setup behind it", and the verb 設定 in 「在介面裡能設定的是 SSO」 is "SSO is the part you configure in the UI".

The graded sweep — all 297 occurrences, not just the place form

設定 is also the ordinary Chinese word for configure, so a raw count is not a finding. Every occurrence of 設定 across the 67 zh-Hant pages was graded — 297 occurrences, and the eight below are the whole defect class. (工作室, for Studio: 0 occurrences, so the Studio app is never named in Chinese on this surface.)

grade	occurrences	example
權限設定檔 — Profile, or a config file	87	「六種內建權限設定檔」
the verb 設定, or the noun "a setting / a config change"	187	「正在設定系統」, 「設定變更」, 「沒有可設定的上限」, 「在管理設定中切換開關」 (twin: "in admin settings")
docs-site page titles and cross-links	8	設定清單 = Setup Checklist, 「[管理 › 設定]」 — documentation navigation, translated in every locale by design, and the subject of the open decision #1545
an unshipped Settings page the twin itself marks (not shipped)	3	guides/email-and-calendar.zh-Hant.mdx:56/62/64, twin Settings → Email Templates
偏好設定 — preferences	1	「個人資料偏好設定」
the audit-event category, twin Configuration	1	「| 設定 | ✅ 已核實 | config_change 記錄」
the defect class — 7 lines	8	the table above; sandbox-and-releases:44 carries two
defect class, outside this PR's file surface	2	filed as #1559

87 + 187 + 8 + 3 + 1 + 1 + 8 + 2 = 297.

Measurements

• The guard is green before and after, and did not move. test/docs-setup-navigation-names.test.ts — 1 file, 18 tests passed on the untouched tree, and 18 tests passed on the edited tree. That is the expected result: rule 1 bans only names the platform ships nowhere, and 設定 is both a live zh-CN label and an ordinary word, so it can never be listed there; rules 2 and 3 need a bold **App → …** path and this shape has no arrow. The guard going red here would have meant Four more zh-Hant sites name the Setup app in Chinese with no arrow — a shape all three rules of the navigation guard are structurally unable to see #1538's model was wrong.
• pnpm verify green at b0496914 — the full chain, validate && typecheck && lint && lint:i18n-gate && hygiene && hygiene:tokens && build && test: ✓ Validation passed (1577ms) · tsc --noEmit clean · objectstack lint clean · ✓ i18n lint gate: 0 i18n/missing-* issues · ✓ source hygiene clean · ✓ source token ratchet clean · ✓ Build complete (2185ms) · Test Files 159 passed (159), Tests 3344 passed | 1 skipped (3345).
• Nothing was ablated, because nothing behavioural changed — this PR is prose. What is proved instead is that each edit landed: per file, the blob hash before and after, and anchored counts on both the removed and the injected text (each of the seven anchors matched exactly once, each file's blob hash changed). The five blob ids in this commit are the same five those counts were taken against, so the green run above is a reading about this tree.

Two things the card had slightly wrong, reported not corrected in place

1. The SCIM site is on reference/security-and-compliance.zh-Hant.mdx, not administration/. Four more zh-Hant sites name the Setup app in Chinese with no arrow — a shape all three rules of the navigation guard are structurally unable to see #1538 and its dispatch claim both name administration/security-and-compliance.zh-Hant.mdx; no such file exists. The site itself is real and matches the quoted text exactly. This matters for the fence the claim declares over Security page's zh siblings call two-factor 「双因素」, but the platform's zh-CN pack says 「两步验证」 #1514 — the fence holds, on the reference/ path.
2. The zh-Hans sibling carries the same shape, and is deliberately untouched. reference/security-and-compliance.zh-Hans.mdx:75 reads 「设置里没有 SCIM 页面。」. That is out of this claim's surface, and it is not obviously a defect at all: 设置 is what the console actually renders for a Simplified reader, so a Simplified page naming a Simplified-rendered app in Chinese is the convention working, not failing. Left for whoever rules on it.

Not in scope here

No guard change. Whether any rule can catch this shape at all is #1553, which stays open — a rule keyed on the place form would have to survive the ~289 correct generic uses graded above, and nothing here shows that it can.

Two further sites are in the same class but outside this PR's declared file surface, and are filed as #1559: 「設定 UI」 on administration/index.zh-Hant.mdx:40 (twin: Setup UI), and the Setup app's nine navigation groups still listed in Traditional on guides/integrations.zh-Hant.mdx:33 — the same roster PR #1537 converted on the other page that carries it, where the sixth entry 設定 names Configuration, not Setup.

🤖 Generated with Claude Code

https://claude.ai/code/session_019hUuCQStzXGMFSX4dzww5t

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
hotcrm	Ignored		Sep 3, 2026 11:50am UTC