docs(connections): rename Unknown status badge to View in {provider}

[george-dilthey]

What changed

Updated docs/connections-and-integration-accounts.md and docs/clay-ads.md to replace the stale Unknown connection status badge label with the new View in {provider} label (e.g. "View in Slack", "View in Meta") shipped in this deploy. Also added the tooltip text that appears on hover: "Status for this connection is only available in {provider name}."

Why

A code change in this deploy (clay-run/clay-base 87ac155...19ad5db) renamed the gray "Unknown" status badge shown for connections that cannot be automatically verified. The badge is now labeled View in {provider name} with a hover tooltip explaining the limitation. The existing docs referenced the old "Unknown" label in two places: the step-by-step verification instructions in connections-and-integration-accounts.md and a Meta-specific note in clay-ads.md. Both are now stale and would mislead customers looking for the badge they see in the UI.

Source link(s)

• Deploy: https://github.com/clay-run/clay-base/actions/runs/33195189534
• Diff: https://github.com/clay-run/clay-base/compare/87ac155b76711173f355fa132a9aa9fc6695b260...19ad5db937a918fa14c01b43beffa59751b78b09
• Specific commit: db1cb69210d4abc90dd42410818c5fce08a6b4a6 — fix(connections): rename Unknown status badge to View in {provider} (#51584)
• Verifier evidence: connection-status-utils.ts:34 — getUnverifiableStatusLabel returns View in ${getProviderDisplayName(appAccountType)}; ConnectionStatusCell.tsx:176 — tooltip is Status for this connection is only available in ${getProviderDisplayName(appAccountType)}.; no feature flag found — shipped to all customers

Uncertainties

None. The verifier returned PASS with file:line evidence. No feature gate. Shipped to all customers unconditionally.

Related observations

• The feat(audiences): add hard delete to admin reset panel commit (19ad5db9) is explicitly internal-only per its PR description. No doc update needed.
• The feat(enrichment-2.0): create enrichment workflows from fields commit (cde90231) adds a new entrypoint in the Data Hub to create enrichment workflows from a specific field. The audiences/enrichment docs do not currently document the workflow creation flow in detail so this is not a regression.
• docs/clay-ads.md also had a reference to "Unknown" status badge (Meta-specific note) which this PR also updates to View in Meta. PRs docs(clay-ads): add FAQ for sending a Find People workbook list to an ad platform #2363, docs(clay-ads): add audience size glossary entry and match rate vs audience size FAQ #2287, docs(clay-ads): add Audience size glossary entry, update Match rate definition, add match rate vs audience size FAQ #2286, docs(clay-ads): explain Ad sync vs Legacy ad sync difference #2256, docs(clay-ads): add EEA consent, platform fields, delete-recreate behavior, match rate clarification #2251, docs(clay-ads): clarify Enterprise has unlimited active recurring ad syncs #2218 are open on clay-ads.md but none touch the badge label — my change is a distinct, non-overlapping fix.

Confidence: high

Closes DOC-2164

[linear-code]

DOC-2164