fix(integrations): keep the Atlassian coverage hint visible, and trim comments

Cursor Bugbot: `ChipModalField` hides a `hint` whenever that field shows an
`error`, so the multi-product coverage sentence vanished the moment the domain
format check fired — exactly when someone mid-form most needs it. The sentence
also describes the token, not the domain, so it read as domain guidance.

Moves it to the API token field, which surfaces its errors through
`ChipModalError` at the bottom rather than its own `error` prop, so the hint
cannot be displaced.

Also drops rationale comments that restated the code they sat above.

Author: waleedlatif1

apps/sim/app/workspace/[workspaceId]/integrations/[block]/integration-block-detail.tsx

@@ -67,12 +67,9 @@ export function IntegrationBlockDetail({ integration, workspaceId }: Integration
   useScrollRestoration(scrollContainerRef, { ready: !credentialsLoading })
 
   /**
-   * Credentials that authenticate this integration. Matching goes through
-   * `credentialProviderMatchesService` so a family service account lists on
-   * every product it powers — one Atlassian token covers Jira, Jira Service
-   * Management, and Confluence. Comparing resolved `providerId`s instead would
-   * hide it from all three, since `atlassian-service-account` resolves to its
-   * own pseudo-service rather than to any product.
+   * Matches on the service's own id *or* its service-account id, so a family
+   * credential lists on every product it powers. Comparing resolved
+   * `providerId`s instead hides it from all of them.
    */
   const connectedCredentials = useMemo(() => {
     if (!oauthService) return []

apps/sim/app/workspace/[workspaceId]/integrations/components/connect-service-account-modal/connect-service-account-modal.tsx

@@ -62,10 +62,11 @@ function openDocs(url: string): void {
 const ATLASSIAN_DOMAIN_HINT_REGEX = /^[a-z0-9-]+\.atlassian\.net$/i
 
 /**
- * States the site-wide reach of the token up front. Users reaching this modal
- * from the Jira page were left unsure whether they had connected Jira or Jira
- * Service Management; the credential covers both, plus Confluence. Derived from
- * the catalog so it cannot drift as Atlassian integrations are added.
+ * States the token's reach up front — the ambiguity this modal exists to remove.
+ * Sits on the API token field, not Site domain: it describes the token, and
+ * `ChipModalField` hides a `hint` whenever that field shows an `error`, which
+ * would drop it exactly while the user is correcting a domain typo. Derived
+ * from the catalog so it cannot drift as Atlassian integrations are added.
  */
 const ATLASSIAN_COVERAGE_HINT = getServiceAccountCoverageSentence(
   ATLASSIAN_SERVICE_ACCOUNT_PROVIDER_ID
@@ -502,7 +503,7 @@ function AtlassianServiceAccountModal({
         Add {serviceName} service account
       </ChipModalHeader>
       <ChipModalBody>
-        <ChipModalField type='custom' title='API token' required>
+        <ChipModalField type='custom' title='API token' required hint={ATLASSIAN_COVERAGE_HINT}>
           <SecretInput
             value={apiToken}
             onChange={(value) => {
@@ -535,7 +536,6 @@ function AtlassianServiceAccountModal({
               ? 'Atlassian sites usually look like your-team.atlassian.net.'
               : undefined
           }
-          hint={ATLASSIAN_COVERAGE_HINT}
         />
 
         <ChipModalField

apps/sim/app/workspace/[workspaceId]/integrations/components/connect-service-account-modal/use-service-account-connect.ts

@@ -28,11 +28,8 @@ import { isHiddenUnder, overlayVisibility } from '@/blocks/visibility/context'
 export interface ServiceAccountConnectTarget {
   serviceAccountProviderId: ServiceAccountProviderId
   /**
-   * Name the setup surface is titled with. For a family service account this is
-   * the vendor ("Atlassian"), not the product page you came from — one Atlassian
-   * token authenticates Jira, Jira Service Management, and Confluence alike, so
-   * calling it a "Jira service account" is what made users think they had
-   * connected the wrong product.
+   * Name the setup surface is titled with — the vendor ("Atlassian") for a
+   * family service account, not the product page you opened it from.
    */
   serviceName: string
   serviceIcon: ComponentType<{ className?: string }>

apps/sim/app/workspace/[workspaceId]/integrations/connected/[credentialId]/connected-credential-detail.tsx

@@ -96,12 +96,6 @@ export function ConnectedCredentialDetail({
     [oauthServiceNameByProviderId]
   )
 
-  /**
-   * Service, brand tile, and copy all come from the shared resolver so this
-   * page, the integrations list, and the Cmd-K search agree on how a credential
-   * is named and branded — a family service account reads as its family
-   * ("Atlassian"), not as whichever product the provider walk happened to hit.
-   */
   const display = useMemo(
     () => (credential ? resolveCredentialDisplay(credential) : null),
     [credential]