Prototype to contract

Replace prototype data and action seams with fragments, route queries, and backend contract SDL.

Read

• Read the current schema, schemaExtensions, GraphQL Client config, route entry, prototype data, and local action hooks.
• Follow the app's existing graphql loading and generated-artifact conventions.
• Use graphql-schema-design skill for schema names, nullability, connections, mutation payloads, and typed errors.

Components

• Preserve prototype boundaries unless the component reads fields from more than one entity.
• Give each data-bound component one primary entity and one colocated fragment for the subset it reads.
  • use the graphql clients equivalent of useFragment and use data masking!
• Pass related entities to child components as fragment data; do not read their fields in the parent.
• Split shells from data-bound content when the shell would otherwise own multiple entity fragments.
• Keep local UI state, formatting, icons, labels, and styling out of GraphQL.