[Improve] Discover and connect team tools during setup

[roomote-roomote]

​Created by Roomote. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

Related issue

Requested setup improvement; no linked GitHub issue.

Why this PR exists

• A maintainer explicitly invited this PR in the linked issue or discussion
• I am a maintainer / this is internal Roomote work

Make integrations a natural, optional part of first setup so teams can connect useful context beyond source code without delaying activation or changing starter work.

What changed

• Ask briefly about documents, monitoring/product analytics, and project tracking, one topic at a time, in priority derived from the existing homepage integration order. Skip questions already answered or skip the whole conversation early.
• Show only eligible supported tools the user said they use, with every match visible and no catalog expansion or unmentioned suggestions. If there are no eligible matches, automatically continue without showing an empty card.
• Reuse secure configuration dialogs with automatic connection-status refresh. Use default Connect buttons and an outline Keep going action with an arrow, regardless of connection state. Remove badges, Available labels, manual refresh, and unnecessary explanatory copy.
• Reuse the catalog and exclude source-control, communications, sandbox, and inference providers. Keep the Vercel deployments connector distinct from Vercel AI Gateway inference; do not apply a separate auth-provider exclusion. Homepage ordering and separate provider setup remain unchanged.
• Persist optional continuation through the setup input contract, preserve setup context on normal replies, and prevent readiness events from interrupting discovery. Existing setup sessions and starter-task definitions/selection/launch behavior remain intact.
• Record privacy-safe exposure, continuation, and configuration-entry events. Existing integration lifecycle events continue to measure connections; no answer text or credentials are added to analytics.
• Update public setup documentation.

How it was tested

• Latest iteration: 142 web client tests (including 15 dedicated card cases) and 7 setup prompt tests passed. The unchanged backend/shared contracts were previously validated by 40 web server, 21 shared types, and the remaining 257 Fast service/schema tests. Coverage includes named-tools-only rendering, zero-match auto-skip, many matches without collapse, automatic status refresh, ordering, unsupported matching, provider exclusion, Vercel eligibility, old persisted input, ownership, and secure-dialog cancellation.
• Pre-push checks passed: oxlint, web/worker ESLint, full pnpm check-types:fast, and pnpm knip. Changed files passed the formatting hook and git diff --check. Public docs validation and broken-link checks passed.
• Real Session UI inspected at desktop 1440x1000 and mobile 390x844 with five named matches shown without collapse. Opened and cancelled the existing Notion secret form. Clicked Keep going without connections and verified persistence. A second zero-match request automatically persisted its response and advanced without a suggestion card or click.
• Browser state used synthetic pending requests and a temporary setup-session linkage in the sandbox database. Queries, renderer, form, and continuation mutation were real; the seed and linkage were cleaned up. This does not prove live model-led discovery or external OAuth/provider connections. No credentials were entered or saved. Full monorepo test suite and live external auth were not run. Existing transcript tests emit non-failing React act warnings.

Checklist

• The PR title follows the repo convention: [Fix], [Feat], [Improve], [Refactor], [Docs], or [Chore] followed by a user-facing description
• This PR is small and scoped to one change
• pnpm lint and pnpm check-types pass locally
• I added tests or included a clear manual validation note above
• I removed secrets, tokens, private keys, and customer data from code, logs, and screenshots
• If this change should appear in the changelog, I ran pnpm changeset

The exact full commands in the checklist were not run; their fast pre-push variants and changed-file formatting passed. No changeset was added.

Screenshots

All screenshots use the seeded local Session state described above, not a live model-generated onboarding conversation.

Desktop optional integration setup:

Mobile optional integration setup:

Existing secure configuration form, with no credential entered:

Zero-match automatic continuation, showing the existing sandbox setup:

[roomote-community]

No new code issues found. See task

_{Reviewed b2849f6}