feat(graphql): GraphQL operations as data sources (7.1, C4)

[officialCodeWork]

Phase 7.1 — GraphQL adapter (failure mode C4) · first Phase 7 step

Recognizes the GraphQL a component runs and treats each operation as a data source, reusing the existing data-source node + fetches-from wiring. No schema change — graphql was already a DataSourceKind.

Changes

• graphql.ts
  • parseGraphqlOperation — reads operation type/name (and root selection fields as an anonymous-op fallback) from a gql document; ignores # comments; handles shorthand { … }; returns null for fragment-only docs.
  • graphqlOperationFromArg — resolves a hook's first argument to an operation: an inline gql/graphql tagged template, or an identifier followed via getDefinitionNodes() so an imported/co-located gql const resolves cross-file.
• detectDataSource gains a GraphQL branch before the react-query branch. Apollo/urql reuse useQuery/useMutation, so it only claims the call when the argument is an actual gql document — otherwise it falls through and react-query handles it. Emits sourceKind: "graphql", method = query/mutation/subscription, endpoint = operation name (the value federation/attribution will join on).

Fixture & tests

• c4-graphql: imported-const useQuery (GetUsers) + useMutation (CreateUser) + inline useSubscription (OnTick) → one graphql source each with the right method and a fetches-from edge.
• 9 unit tests including the react-query disambiguation (the c5 fixture's URL-queryFn useQuery/useMutation still classify as react-query, zero graphql sources).

Verification

• pnpm eval → 326 pass · determinism 1.000 · all metrics 1.000
• parser-react 160 tests; full suite, typecheck, lint green.

Codegen response types (feeding 5.5) deferred — needs a .graphql/codegen fixture; the operation→data-source spine here is what unblocks federation (7.6). 7.2–7.6 remain sketch-level pending 0.5.0 tester feedback. Tracker updated.

🤖 Generated with Claude Code