[Feat] Add linked identities for source-control providers

apps/docs/source-control.mdx

@@ -53,6 +53,19 @@ the Roomote identity otherwise. A workspace containing any public or
 unresolved repository uses the public-safe identity for all new commits because
 Git author configuration applies across the workspace.
 
+Linked GitLab and Gitea accounts retain the username verified by that provider,
+scoped to the configured source-control host. Bitbucket does the same only when
+its profile API returns a username; a nickname is not treated as a public
+handle. Azure DevOps
+accounts retain their verified display name for Settings and private-repository
+context, but public attribution remains generic because Azure DevOps does not
+provide a stable non-email public handle. GitLab.com can also provide a verified
+`noreply` commit identity; other non-GitHub providers use Roomote as the Git
+author for public work.
+
+Existing account links pick up verified profile attribution after their OAuth
+token refreshes or after the account is linked again.
+
 Changing a repository from private to public does not rewrite existing Git
 history. Roomote sanitizes a legacy named attribution line the next time it
 updates an open public pull request.

apps/web/src/components/settings/LinkedAccounts.tsx

@@ -815,6 +815,7 @@ export function LinkedAccounts() {
     githubInstallations.isPending ||
     gitlabAccount.isPending ||
     giteaAccount.isPending ||
+    bitbucketAccount.isPending ||
     adoAccount.isPending ||
     slackInstallation.isPending ||
     linearInstallation.isPending ||