translate-spec-to-craft-ts

Decompose the spec into remote reads, remote writes, local UI state, URL state, events, and forms, then match each part: server reads to query, writes to mutation, UI-only state to state, and URL-backed state to queryParams. The lexical map in references/lexical-map.md gives the exact wording-to-API correspondences.

Use one query for the list, one mutation per delete intent (single and bulk), a selection state for selected ids, and insertReactOnMutation on the query with optimisticUpdate using removeOne or removeMany. Enable reload.onMutationError by default for optimistic deletes.

A primitive accepts only one insertion, so compose several with the universal craftPipe: primitive(config, (context) => craftPipe(context, insertion1, insertion2)). The variadic form no longer exists, except for the form-tree helpers which stay variadic.

Use craftInputs when a value comes from a parent component, route, or context and does not belong in the URL. Use queryParams only for shareable, URL-backed state such as page, sort, search, and filters.

Yes. It defaults to optimisticPatch for shallow field edits and optimisticUpdate for structural changes, with reload.onMutationError enabled. For pagination it recommends identifier on the query plus insertPaginationPlaceholderData to avoid flicker.

Treat toSource, computedSource, signalSource, linkedSource, resourceById, and toInject as infrastructure-level choices. Only select them when the request is explicitly about source pipelines or custom resource plumbing, not ordinary product wording.