Add X social search adapter

docs/EVAL_INTEGRATION_CATALOG.md

@@ -75,6 +75,12 @@ These integrations should anchor the large eval effort because they cover the ma
 | GitHub | `@relayfile/adapter-github` | `packages/github` | P0 | Pull requests, issues, reviews, commits, checks. |
 | GitLab | `@relayfile/adapter-gitlab` | `packages/gitlab` | P1 | Merge requests, issues, pipelines, jobs, commits. |
 
+### Social & Search
+
+| Integration | Package | Directory | Eval priority | Coordination surface |
+|---|---|---|---|---|
+| X | `@relayfile/adapter-x` | `packages/x` | P1 | Budgeted recent/archive social search, posts, optional user hydration. |
+
 ### CRM & Sales
 
 | Integration | Package | Directory | Eval priority | Coordination surface |
@@ -213,6 +219,7 @@ These are not implemented packages in this repo today, but they should be part o
 | Real-time storage bridge | Google Drive, SharePoint, OneDrive, GCS, S3, Dropbox |
 | Data and runtime state | Postgres, Redis, Airtable, Segment, Mixpanel |
 | Commerce and payments | Shopify, Stripe |
+| Social and search | X |
 | Long-tail provider breadth | Mailgun, SendGrid, Calendly, Box, Azure Blob |
 | Gap validation | Confluence, Google Docs, Freshdesk, ServiceNow, PagerDuty, Monday.com, Discord, Outlook, Figma |
 
@@ -233,6 +240,7 @@ The current publish resolver uses these group aliases. Keep this list aligned wi
 | `email` | `mailgun`, `sendgrid` |
 | `commerce` | `shopify`, `stripe` |
 | `db` | `postgres`, `redis` |
+| `social` | `x` |
 
 ## Sources
 

docs/integration-scopes.yaml

@@ -1,6 +1,6 @@
 version: 1
 title: Relayfile integration scope catalog
-updated: "2026-05-10"
+updated: "2026-05-17"
 purpose: >
   Machine-readable scope inventory for Relayfile adapter evals and app
   registration. Entries start as pending unless scopes were already provided or
@@ -978,6 +978,26 @@ integrations:
       - https://learn.microsoft.com/en-us/graph/api/subscription-post-subscriptions?view=graph-rest-1.0
     notes: "Microsoft Teams uses Microsoft Graph permissions. Nango's `microsoft-teams` provider aliases the shared Microsoft OAuth provider, whose registry default is `offline_access` plus `.default`; Nango's Teams setup guide tells operators to add required delegated Microsoft Graph permissions in Entra, and its maintained messages sync declares `ChannelMessage.Read.All` and `Chat.Read.All`. Relayfile reads team/channel metadata, members, tabs, channel messages/replies, chat metadata/messages, and reactions, and writes channel messages, channel replies, and chat messages. The read surface maps to `Team.ReadBasic.All`, `Channel.ReadBasic.All`, `TeamMember.Read.All`, `TeamsTab.Read.All`, `ChannelMessage.Read.All`, and `Chat.Read.All`. Message create writeback uses delegated `ChannelMessage.Send`; Microsoft documents application message send only through migration-only `Teamwork.Migrate.All`, so that is not included for normal app behavior. Message deletion is delegated-only in Graph's `chatMessage: softDelete` API and requires `ChannelMessage.ReadWrite` for channel messages/replies and `Chat.ReadWrite` for chat messages; the current adapter's delete resolver should use Graph softDelete semantics for real deletion. Graph subscriptions require read permission for the subscribed resource: tenant-wide `/teams/getAllMessages`, `/chats/getAllMessages`, `/teams/getAllChannels`, and `/teams` presets are application-only, while team/channel/chat scoped presets can use delegated or application permissions depending on the resource. This means the full eval surface is a mixed model: delegated OAuth with `offline_access` for user-scoped read/write, plus admin-consented Graph application permissions when tenant-wide subscription presets are enabled."
 
+  - slug: x
+    display_name: X
+    category: social
+    status: implemented
+    package: "@relayfile/adapter-x"
+    nango_slug: x
+    auth_model: bearer_or_oauth2
+    scope_status: needs_review
+    required_scopes:
+      - tweet.read
+      - users.read
+    candidate_scopes:
+      - offline.access
+    sources:
+      - https://docs.x.com/x-api/posts/search/introduction
+      - https://docs.x.com/x-api/posts/search/quickstart/recent-search
+      - https://docs.x.com/x-api/posts/search/integrate/overview
+      - https://docs.x.com/x-api/fundamentals/post-cap
+    notes: "The X adapter is read-only and search-first. It uses recent search by default and full-archive search only when explicitly configured, then materializes saved search runs, matched posts, and capped optional user hydration. X's search quickstart documents Bearer Token authentication for recent search; OAuth 2.0 App-Only is documented for public Post data, while user-context OAuth apps normally request tweet.read and users.read. Cost controls are part of the adapter contract because X bills successful returned resources under pay-per-use."
+
   - slug: zendesk
     display_name: Zendesk
     category: support

docs/writeback-spec-coverage.md

@@ -34,6 +34,7 @@ Contract-backed means the endpoint uses `contractEndpoint(...)`, loads its reque
 | sharepoint | None | 0 | 2 | Inline JS schemas. |
 | slack | None | 0 | 4 | Inline JS schemas. |
 | teams | None | 0 | 3 | Inline JS schemas. |
+| x | None | 0 | 0 | Read-only social search adapter; no writeback endpoints. |
 | zendesk | None | 0 | 3 | Inline JS schemas. |
 
 ## Updating This File