getting-started/quick-tour 第 1 节(三语)整节失实:落地页不是 CRM Overview 而是 Executive Overview,5 条要点里 4 条不对应任一块仪表盘的 tile #971

发现自 #960 / PR #968 的实施过程(把同一页 :35-:44 的导航表按 src/apps/crm.app.ts 写实时顺带读到第 1 节)。

基线 origin/main = 4705aed5(平台 17.0.0-rc.3)。不与 #960 / PR #968 重叠:那单的面严格限定在第 2 节那张导航表,完全不碰第 1 节。

事实

content/docs/getting-started/quick-tour.mdx:10-20(zh-Hans 同址 :10-:20,zh-Hant :10-:18,三语同形):

## 1. The home dashboard

The first thing you see is the **CRM Overview** dashboard. It tells you:

- How many **open leads** you have.
- How many **opportunities** are in your pipeline.
- Any **cases** awaiting your response.
- Top accounts by pipeline value.
- Recent activity (last calls, meetings, emails).

落地页认错了

src/apps/crm.app.ts:33-39 的 nav_home 是 type: 'dashboard'、dashboardName: 'executive_dashboard',源码注释写明 "Pinned landing — single executive view, single click from launcher."。而 executive_dashboard 的 label 是 Executive Overview(src/dashboards/executive.dashboard.ts:25-26;zh-CN 语言包为「高管总览」)。

叫 CRM Overview 的是另一块:crm_overview_dashboard(src/dashboards/crm.dashboard.ts:27-28),它挂在 group_insights 下的 nav_crm_dashboard(src/apps/crm.app.ts:151)——而 group_insights 未声明 expanded,默认收起,所以新用户既不会"第一眼看到"它,默认也点不到。

5 条要点里只有 1 条对得上

executive_dashboard 的 8 个 widget title(src/dashboards/executive.dashboard.ts):Total Revenue (YTD)、Active Accounts、Total Contacts、Open Leads、Revenue Trend、Revenue by Industry、New Accounts、Accounts by Industry。

即:整节描述的是一块并不存在的"混合盘"——名字取自 crm_overview_dashboard,要点取自 service / activity 等其他几块盘,而用户真正落到的 executive_dashboard 有 8 个 tile,页面只说中了 1 个。

为什么要紧

这是《快速上手》的第一句话。#960 / PR #968 刚把同页第 2 节的导航表按源码整表写实并加了守卫 test/docs-quick-tour-navigation.test.ts;那张表里 Home 一行现在明确写着它打开的是 Executive Overview,与第 1 节首句直接冲突——同一页自相矛盾,而第 1 节还在最前面。

边界与口径建议

• 面:content/docs/getting-started/quick-tour{,.zh-Hans,.zh-Hant}.mdx 第 1 节,三语同步;src/ 零改动。
• 口径沿用 docs(automation): 按 flow 源码写实内置流程表两行，并修 opportunity_won_alert 的 description (#851) #870 / docs(flows): name what the flow nodes do, not what they were once meant to do #877 / docs(service): 按 flow 与 hook 写实 SLA 页的升级说明(#876) #885 / docs: 清扫 automation 页之外的「工作流规则」并写实 cases 两条虚构通知 (#850, #887) #894 / docs(service): 把 service/index 的升级与通知五条说法按 flow / hook 写实(#904) #913 / docs(service): write the sla page's views, report dimensions and business-hours claims to source (#917) #924 / docs(service): write the index page's 《Where to find things》 list to the real navigation (#927) #932 / docs(marketing): name Products in the index page's "Where to find things" (#938) #942 / docs(revenue): write the index page's "Where to find things" section to the real navigation (#943) #953 / docs(getting-started): write the quick tour's navigation table to the real app (#960) #968:label 逐字以源码为准,要点按 executive_dashboard 的真实 tile 重写;CRM Overview 这个名字读者会带着来,应指向它真实所在(group_insights 下,且默认收起),不静默删名。
• 已有守卫可直接扩:test/docs-quick-tour-navigation.test.ts 已导入 CrmApp 与 ExecutiveDashboard,加一段按 widget title 比对第 1 节的断言即可,模式与 test/docs-service-index-analytics.test.ts(service/index 的《Standard dashboards & reports》四行全部失实：仪表盘描述里的 top agents / oldest open cases 不存在，三张报表名与 case.report.ts 的 label 都对不上 #948)相同。
• 产品判断不预判(SLA policy matrix: per-priority × tier clocks, first-response stamping, escalation that reassigns #595 / Case intake: round-robin assignment + triage view so web-to-case never lands ownerless #596 同族):落地页该绑哪块盘、该不该加工单/活动 tile 是产品决定,本单只记录当前形状。

Refs #960 #968 #948 #955