docs(faq): stop troubleshooting connectors that do not exist

[os-steve]

Fixes #1402

The FAQ's 🔌 Integrations section troubleshot two connectors that do not exist, in the imperative. Both answers are rewritten in the shape PR #1401 gave the neighbouring Stripe answer on this same page: say what actually ships, point at Integrations, and drop the troubleshooting steps for a connector that cannot be misconfigured because it is not there. Three locales.

What was wrong, re-measured on this branch's base (main @ 1486ec0, not the 021db54 the card quotes)

line	claim	measured
150 (all three locales)	"The Gmail / Outlook connector is connected (Settings → Email)"	No connector. And no Settings app: the shipped apps are HotCRM (src/apps/crm.app.ts) plus the platform's SETUP_APP / STUDIO_APP / ACCOUNT_APP, labelled Setup / Studio / Account
151–152	"a known contact (matched by email)" · "isn't on your excluded list"	Both describe the unshipped inbox connector — guides/email-and-calendar.mdx files address-matched logging under How email logging works (not shipped yet) and says exclusion lists are "not shipped"
154 / 156 (all three locales)	"Check the DocuSign integration log (Setup → Integrations → DocuSign → Activity)"	grep -rn 'DocuSign' src/ → 0 (reverse control: grep -rn 'crm_lead' src/ → 198). No connector, therefore no log and no webhook to retry

Setup → Integrations itself is real — it resolves live as a Setup group label — but as this app ships it holds exactly the two platform-contributed entries, Connect an Agent and Datasources, and no vendor mounts anything under it. Ground truth re-read off content/docs/guides/integrations.mdx (the page #756 fixed) rather than taken from a summary.

What the answers say now

• Email. Nothing logs an inbound message, by address match or otherwise, and there is no exclusion list. What ships is the outbound half — Send Email on a contact, which writes the message as a record and leaves an entry on that contact's Activity timeline, is hidden on a contact with Email Opt Out ticked (src/actions/contact.actions.ts, visible: record.email_opt_out == false), and delivers only through the mail transport a deployment configures. Links Email & Calendar and Integrations.
• DocuSign. No integration log to open, no webhook delivery to retry. The DocuSign row on Integrations is design intent, not a switch. Until it ships, a quote's or a contract's status is a field someone sets by hand and the signed document is a file someone attaches.

Headings are untouched, so anchors and the search paths a reader arrives on are unchanged, and a reader who searches "DocuSign" still lands on the answer — which now tells them it does not exist.

What the checks establish, and what they do not

pnpm test — 159 files, 3380 passed, 1 skipped, exit 0. apps/docs (its own lockfile, outside the root pnpm project; docs-app.yml): pnpm install --frozen-lockfile + pnpm run types:check + pnpm run build all exit 0, 201 doc paths prerendered.

Named guards, read before committing and re-read after:

• docs-locale-callouts — blockquote runs per locale trio: 0 / 0 / 0 at HEAD, 0 / 0 / 0 after. The trio stays balanced, and all three files stay the same length (194 lines each).
• docs-view-rosters — the FAQ carries no ## Standard list views section in any locale, so this guard has nothing to count here. Green, and green over nothing.
• docs-anchor-links — every new internal link is unanchored, so this guard does not judge them; the four target pages were checked to exist by hand, in each locale.
• docs-setup-navigation-names — this one does see the new text: rule 2 parses the bold **Setup → Integrations** (en/zh-Hant) and **设置 → 集成** (zh-Hans) citations and resolves the second segment live against the shipped roster.

Reverse verification of that last claim (the ablation), because a green guard is not evidence on its own. Predicted direction: red on mutation.

before: 'Setup → Integrations**' = 1   'Integrationz' = 0
after : 'Setup → Integrations**' = 0   'Integrationz' = 1     ← mutation proven on disk
mutated run  → exit 1:  content/docs/reference/faq.mdx: 'Setup → Integrationz'
restored     → git diff HEAD empty; blob fd6bd23 == HEAD blob fd6bd23
restore leg  → exit 0, 18 passed

⚠️ No gate can confirm the sweep was complete. Neither defect fixed here was a bold **App → …** citation, so #853's navigation rule never parsed either one and #1117's widening does not reach them. Every green above is evidence about the trio's structure, the docs build, and the new bold citations — not about whether more prose on this page names machinery that does not exist. The count below is a hand sweep, and it is the only evidence for that.

The #756 sweep of the rest of reference/faq*.mdx

Swept all three locales for connector and integration claims (connector|integrat|webhook|Slack|Zapier|Stripe|Twilio|…) and for every navigation path in the file, resolving each first segment against the platform roster.

• Other guides/integrations.mdx 把 10 类连接器列为「Built-in」、guides/index.mdx 仍把邮件页描述为 Gmail/Outlook 双向同步——仓库里没有任何连接器元数据 #756 residue found: 0. The Stripe answer three lines below was already corrected by Resolve this app's own sidebar citations, and ban a Stripe action that never existed #1401; nothing else on the page claims a connector, a sync or an integration log. No locale carries residue its siblings do not.
• Two findings of a different class, filed rather than swept in — both outside this card's file-surface question and both needing ground truth this card did not establish: The FAQ's AI Copilot answers cite a Setup → AI group that does not exist — Setup ships no AI group, and the guard cannot see either line because both are italic #1591 (the AI Copilot answers cite Setup → AI → Health and Setup → AI → Knowledge Bases → Refresh; Setup ships no AI group — it is a Studio group) and Twelve links inside localized docs pages drop the locale prefix, so a Chinese reader clicking them lands on the English page #1592 (12 site-absolute /docs/… links inside localized pages, 2 of them left on this page by Resolve this app's own sidebar citations, and ban a Stripe action that never existed #1401, that drop a Chinese reader onto the English page).

Scope

content/docs/reference/faq{,.zh-Hans,.zh-Hant}.mdx + the changeset — the dispatched surface exactly, no src/, no test/. No guard entry was added: a rule-1 ban on the retired names would live in test/docs-setup-navigation-names.test.ts, which is off-surface, and the card is explicit that the reader-facing correction is the deliverable.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DuzfS5chho38Yx1jxx9DEj

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated
hotcrm	Ignored		Sep 5, 2026 3:47pm UTC