<!--
AUTO-GENERATED — DO NOT EDIT THIS FILE.
Generated by `mlcl sync-docs` from the package's src/index.ts JSDoc + mlcl/registry.json.
Edits here are overwritten on the next commit (molecule's pre-commit hook regenerates).
To change this document, edit the module-level JSDoc in src/index.ts.
Generated: 2026-11-14T12:29:21.947Z
-->

# @molecule/app-query-react

React hooks for `@molecule/app-query`.

**Load page data with {@link useQuery}, not `fetch` inside a `useEffect`.** A hand-written load
effect that cancels its request on cleanup (a `cancelled` flag, or an `AbortController`) re-runs
its cleanup on EVERY re-render whenever one of its dependencies is a function created inline each
render — `const [messages, setError] = useApiErrors()` returning arrow functions is the usual
source. The effect's own guard (`if (loaded.current === slug) return`) then returns without
refetching, so the response is discarded whenever it arrives after a re-render: always on a
remote server, never on localhost, which is why the page passes locally and fails on the live URL.
`useQuery` subscribes once per key, keeps its request stable across re-renders, and aborts it
only when the key changes or the page unmounts.

{@link useQuery} observes one document from the app's shared cache and
returns cached data on the first render; {@link usePrefetch} and
{@link intentPrefetchProps} warm a document when a person is about to
open it. Together they make a detail page open with no loading state.

This package needs a bonded client: install `@molecule/app-query` with a bond
(`@molecule/app-query-memory`, or `@molecule/app-query-tanstack`) and call the bond's
`setProvider(provider)` once at startup (the scaffold's `app/src/bonds/` does this).

**Keep displayed records on the query cache.** Render `query.data` directly. A custom
mutation handler publishes its saved response with `query.setData(saved)`; every observer
and the next visit receive it, and subsequent refreshes still update the view. A local
`useState` copy hydrated only once per record hides later query answers. Editable form
drafts remain local until saved. Prefer {@link createQueryResource} for a complete resource;
its writes already publish the response and refresh its tracked collections.

> **Auto-generated, AI-first package reference** for the [molecule.dev](https://molecule.dev) ecosystem.
> It is written to be read by coding agents as much as by people, and is generated from this
> package's source — edit `src/index.ts` JSDoc, not this file.

## Quick Start

```tsx
import { Link } from 'react-router'
import { getClient, isHttpError } from '@molecule/app-http'
import { t } from '@molecule/app-i18n'
import { intentPrefetchProps, useQuery } from '@molecule/app-query-react'

interface PackageDocument {
  name: string
  description: string
}

const packageQuery = (name: string) => ({
  key: ['package', name],
  fetch: async (signal: AbortSignal): Promise<PackageDocument | null> => {
    try {
      const response = await getClient().get<PackageDocument | null>(
        `/data/packages/${encodeURIComponent(name)}.json`,
        { signal },
      )
      return response.data
    } catch (error) {
      if (isHttpError(error) && error.status === 404) return null
      throw error
    }
  },
})

function PackageLink({ name }: { name: string }) {
  return (
    <Link to={`/packages/${name}`} {...intentPrefetchProps(packageQuery(name))}>
      {name}
    </Link>
  )
}

function PackagePage({ name }: { name: string }) {
  const { data, status } = useQuery(packageQuery(name))
  if (status === 'error') {
    return (
      <p role="alert">
        {t('packages.loadFailed', undefined, { defaultValue: 'Unable to load package.' })}
      </p>
    )
  }
  if (status === 'idle' || status === 'loading') {
    return <p role="status">{t('common.loading', undefined, { defaultValue: 'Loading…' })}</p>
  }
  if (data == null) {
    return <p>{t('packages.notFound', undefined, { defaultValue: 'Package not found.' })}</p>
  }
  return (
    <article>
      <h1>{data.name}</h1>
      <p>{data.description}</p>
    </article>
  )
}
```

A list whose page and filter live in the URL: derive the key from the route and pass
`keepPreviousData` with a `principal`, so a page/filter change keeps the rows already on screen
until the next page answers. The app's HTTP client sends the session, so the viewer is part of
what the answer depends on: key on it and pass the same value as `principal` — an account
switch then drops the previous account's rows at once. Pass `null` while the session is still
being restored (`status === 'loading'`; the HTTP client holds the request until then anyway),
so restoring a session never swaps a key that already rendered rows.

```tsx
import { Link } from 'react-router'
import { unwrapList } from '@molecule/app-http'
import { useQuery } from '@molecule/app-query-react'
import { useAuth, useHttpClient, useTranslation } from '@molecule/app-react'
import { useListRoute } from '@molecule/app-routing-react-router'

interface Invoice {
  id: string
  number: string
}

function InvoiceList() {
  const http = useHttpClient()
  const { t } = useTranslation()
  const { status, user } = useAuth<{ id: string }>()
  const list = useListRoute({ pageSize: 20, filters: { status: {} } })
  const viewer = user ? String(user.id) : 'anonymous'
  const query = useQuery(
    status === 'loading' || !list.canLoad
      ? null
      : {
          key: ['invoices', viewer, list.filters, list.page],
          principal: viewer,
          keepPreviousData: true,
          fetch: async (signal: AbortSignal) =>
            unwrapList<Invoice>(
              await http.get('/api/invoices', {
                signal,
                params: { ...list.filters, limit: list.pageSize, offset: list.offset },
              }),
            ),
        },
  )

  // Status renders outside the item list (it is not an item), and the empty state
  // describes only the key on screen, never a retained previous page.
  return (
    <section>
      {status === 'loading' || query.isFetching ? (
        <p role="status">{t('common.loading', undefined, { defaultValue: 'Loading…' })}</p>
      ) : null}
      {query.status === 'error' ? (
        <p role="alert">
          {t('invoices.loadFailed', undefined, { defaultValue: 'Unable to load invoices.' })}
        </p>
      ) : null}
      <ul>
        {query.data?.map((invoice) => (
          <li key={invoice.id}>
            <Link to={`/invoices/${invoice.id}`}>{invoice.number}</Link>
          </li>
        ))}
      </ul>
      {!query.isPreviousData && query.data?.length === 0 ? (
        <p>{t('invoices.empty', undefined, { defaultValue: 'No invoices yet.' })}</p>
      ) : null}
      <Link to={list.href({ page: list.page + 1 })}>
        {t('common.next', undefined, { defaultValue: 'Next page' })}
      </Link>
    </section>
  )
}
```

A mutation or a failed load has to change a page that is ALREADY mounted, and
the cache never starts that request by itself: `set()` paints a mutation's own
response, `invalidate()` marks what it affects for the next mount, and an
explicit `fetch()` retries into the mounted page.

```tsx
import { getClient } from '@molecule/app-http'
import { t } from '@molecule/app-i18n'
import { getQueryClient } from '@molecule/app-query'

// The key names what the document actually depends on — here the signed-in
// principal, the filter and the page. Another principal's feed is a
// different document, so an invalidation scoped to this one leaves it alone.
const feedKey = (principal: string, filter: string, page: number) =>
  ['feed', principal, filter, page] as const

const feedOptions = (principal: string, filter: string, page: number) => ({
  key: feedKey(principal, filter, page),
  fetch: async (signal: AbortSignal) =>
    (await getClient().get(`/api/feeds/${filter}`, { signal, params: { page } })).data,
})

async function setFollowing(principal: string, authorId: string, follow: boolean) {
  const client = getQueryClient()
  const http = getClient()
  const { data: body } = follow
    ? await http.post<{ feed: unknown }>(`/api/follows/${authorId}`)
    : await http.delete<{ feed: unknown }>(`/api/follows/${authorId}`)
  // The response IS the document: paint it now, with no second round trip.
  // (If it were only a count or a flag, skip set() and invalidate() instead.)
  client.set(feedKey(principal, 'following', 1), body.feed)
  // Future reads of every feed this principal owns are stale.
  client.invalidate(['feed', principal])
}

function Retry({ principal }: { principal: string }) {
  return (
    <button
      onClick={() => {
        // invalidate() alone would leave the mounted page on its error;
        // an explicit fetch retries into it. useQuery shows the outcome.
        void getQueryClient()
          .fetch(feedOptions(principal, 'following', 1))
          // The mounted useQuery observer presents this failure via status/error.
          .catch((_error) => {})
      }}
    >
      {t('common.retry', undefined, { defaultValue: 'Retry' })}
    </button>
  )
}
```

One API resource described once, for every page that reads or changes it.
`createQueryResource` returns the list and detail reads as `useQuery` options and the writes
as functions that put the server's record into the cache and fetch the lists on screen again,
so a page never mirrors a response into `useState`. A flag the API models as a sub-path
(`POST /invoices/:id/flag`, `DELETE` to clear it) is `toggle`, which resolves with the saved
record and is the `commit` of `useOptimisticValue`.

```tsx
import { getClient, unwrapList, unwrapSingle } from '@molecule/app-http'
import { createQueryResource, QueryContent, useQuery } from '@molecule/app-query-react'
import { useAuth, useOptimisticValue, useTranslation } from '@molecule/app-react'

interface Invoice {
  id: string
  number: string
  flagged: boolean
}

export const invoices = createQueryResource<Invoice>({
  name: 'invoices',
  path: '/invoices',
  http: getClient,
  readList: (response) => unwrapList<Invoice>(response),
  readOne: (response) => unwrapSingle<Invoice>(response),
})

function InvoicePage({ id }: { id: string }) {
  const { user } = useAuth<{ id: string }>()
  const { t } = useTranslation()
  const viewer = user ? String(user.id) : 'anonymous'
  const query = useQuery(invoices.detail(viewer, id))
  return (
    <QueryContent
      query={query}
      pending={<p role="status">{t('common.loading', undefined, { defaultValue: 'Loading…' })}</p>}
      missing={
        <p role="alert">
          {t('invoice.missing', undefined, { defaultValue: 'Invoice not found.' })}
        </p>
      }
      error={() => (
        <p role="alert">
          {t('invoice.failed', undefined, { defaultValue: 'Unable to load invoice.' })}
        </p>
      )}
    >
      {(invoice) => <FlagButton key={invoice.id} invoice={invoice} viewer={viewer} />}
    </QueryContent>
  )
}

function FlagButton({ invoice, viewer }: { invoice: Invoice; viewer: string }) {
  const { t } = useTranslation()
  const flag = useOptimisticValue({
    value: invoice.flagged,
    commit: async (on) => (await invoices.toggle(viewer, invoice.id, 'flag', on)).flagged,
  })
  return (
    <button type="button" aria-pressed={flag.value} onClick={() => flag.update((on) => !on)}>
      {flag.value
        ? t('invoice.unflag', undefined, { defaultValue: 'Unflag' })
        : t('invoice.flag', undefined, { defaultValue: 'Flag' })}{' '}
      {invoice.number}
    </button>
  )
}
```

A pager needs the whole response, including its total. Keep that read on the same resource
as its mutations, including alternate list paths; a separate hand-written `QueryOptions`
is outside the resource's refresh tracking.

```typescript
import { getClient } from '@molecule/app-http'
import { createQueryResource } from '@molecule/app-query-react'

interface TicketPage {
  tickets: { id: string; subject: string }[]
  total: number
}
const tickets = createQueryResource<TicketPage['tickets'][number]>({
  name: 'tickets',
  path: '/tickets',
  http: getClient,
  readOne: (response) => response.data as TicketPage['tickets'][number],
})
const page = tickets.listPage(
  'agent-1',
  { limit: 10, offset: 20 },
  (response) => response.data as TicketPage,
)
// useQuery(page) observes both rows and total. tickets.create/update/remove/toggle
// and tickets.refresh('agent-1') refresh this page too.
// A second list can use tickets.listPage(viewer, params, readPage, '/tickets/open').
// Use one canonical page reader per path; list() still returns only its own rows.
// For immediate deletion from an opaque page, add a fifth argument:
// (page, id) => {
//   const rows = page.tickets.filter((row) => String(row.id) !== id)
//   return { ...page, tickets: rows, total: page.total - (page.tickets.length - rows.length) }
// }
```

A resource mutation also waits out a pre-mutation list request before fetching again;
joining that older in-flight read alone would leave the new record absent.
Successful deletion removes a row immediately, including one just created through the
resource. Stale reads cannot restore acknowledged deletions for that viewer; an explicit
successful create can recreate the identity. Opaque listPage envelopes need their own
removeFromPage adapter; no row or total property is guessed.

## Type

`feature`

## Installation

```bash
npm install @molecule/app-query-react @molecule/app-query react
npm install -D @types/react
```

## API

### Interfaces

#### `ResourceResponse`

The part of an HTTP response a resource reads.

```typescript
interface ResourceResponse {
  /** The parsed response body. */
  data: unknown
}
```

#### `ResourceHttp`

The HTTP client a resource calls: the app's own bonded client (`getClient()` from
`@molecule/app-http`) has this shape. Only what a resource uses is named here.

```typescript
interface ResourceHttp {
  /** Reads `path`; `signal` cancels it and `params` become the query string. */
  get(
    path: string,
    options?: { signal?: AbortSignal; params?: Record<string, unknown> },
  ): Promise<ResourceResponse>
  /** Creates at `path`. */
  post(path: string, body?: unknown): Promise<ResourceResponse>
  /** Replaces at `path`. */
  put(path: string, body?: unknown): Promise<ResourceResponse>
  /** Changes part of the record at `path`. */
  patch(path: string, body?: unknown): Promise<ResourceResponse>
  /** Removes at `path`. */
  delete(path: string): Promise<ResourceResponse>
}
```

#### `QueryResourceConfig`

What {@link createQueryResource} needs to know about one resource.

```typescript
interface QueryResourceConfig<T> {
  /** The first element of every cache key of this resource, e.g. `'invoices'`. */
  name: string
  /** The collection's path under the API base, e.g. `'/invoices'`. */
  path: string
  /** The app's HTTP client, read on every call so a client bonded later is the one used. */
  http: () => ResourceHttp
  /** The field a record is addressed by in a URL. Defaults to `'id'`. */
  id?: keyof T & string
  /** The HTTP method the API updates a record with. Defaults to `'put'`. */
  updateMethod?: 'put' | 'patch'
  /** Reads the records out of a list response. Defaults to the body itself. */
  readList?: (response: ResourceResponse) => T[]
  /** Reads the record out of a detail or write response. Defaults to the body itself. */
  readOne?: (response: ResourceResponse) => T | null
}
```

#### `QueryResource`

The reads and writes {@link createQueryResource} returns.

```typescript
interface QueryResource<T, Create = Partial<T>, Update = Partial<T>> {
  /**
   * `useQuery` options for the collection. `viewer` is who the answer is for (the signed-in id,
   * or `'anonymous'`); a page or filter change keeps the rows on screen until the next answer.
   */
  list(viewer: string, params?: Record<string, unknown>): QueryOptions<T[]>
  /**
   * Options for a collection's whole page (rows plus totals), or a filtered collection path.
   * Reads share this resource's mutation refresh and viewer isolation. `readPage` reads the
   * canonical page response for `path`; row-only `list` reads keep a separate cache entry.
   * Supply `removeFromPage` for opaque page envelopes to remove acknowledged deletions
   * immediately and keep stale list responses from restoring them.
   */
  listPage<Page>(
    viewer: string,
    params: Record<string, unknown>,
    readPage: (response: ResourceResponse) => Page,
    path?: string,
    removeFromPage?: (page: Page, id: string) => Page,
  ): QueryOptions<Page>
  /**
   * `useQuery` options for one record, or null while `id` is not known yet (`useQuery(null)`
   * observes nothing). A missing record resolves to null, not to an error.
   */
  detail(viewer: string, id: string | null | undefined): QueryOptions<T | null> | null
  /** Creates a record, shows it in the cache and refreshes the lists on screen. */
  create(viewer: string, input: Create): Promise<T>
  /** Updates a record, shows the saved record in the cache and refreshes the lists on screen. */
  update(viewer: string, id: string, input: Update): Promise<T>
  /** Removes a record from detail and tracked row lists, then refreshes those lists. */
  remove(viewer: string, id: string): Promise<void>
  /**
   * Switches a flag the API models as a sub-path: `POST path/id/action` turns it on and
   * `DELETE path/id/action` turns it off. Resolves with the saved record, so it is the `commit`
   * of `useOptimisticValue`.
   * The saved detail is published before tracked lists finish refreshing; this promise waits
   * for those refreshes. Render the shared controller's value and let it queue inverse clicks
   * during that interval. A page-local busy guard can drop a click on the newly changed label.
   */
  toggle(viewer: string, id: string, action: string, on: boolean): Promise<T>
  /** Fetches the lists on screen again, after a change this resource did not make itself. */
  refresh(viewer: string): Promise<void>
}
```

#### `UseQueryResult`

A mounted query's state and its explicit cache and refresh actions.

```typescript
interface UseQueryResult<T> extends QueryState<T> {
  /**
   * Publish a saved document to this key and all its observers. Render `data` directly
   * instead of copying it to local state: later cache updates then remain visible.
   * A function receives this key's current cached document, never retained previous-page
   * data. Returning `undefined` leaves the cache unchanged. A disabled (`null`) query
   * does nothing, including not calling an updater. Like React state setters, wrap a
   * function-valued document in an updater. A saved callback stays bound to its original key.
   * The write supersedes older in-flight reads, using the bonded client's `set` contract.
   */
  setData: (value: T | ((previous: T | undefined) => T | undefined)) => void
  /**
   * Fetch this key again, even when its cached document is fresh. Observers receive the
   * updated state. Resolves with that state, including an error when the request fails;
   * a disabled (`null`) query resolves idle without a request.
   */
  refetch: () => Promise<QueryState<T>>
}
```

#### `QueryContentProps`

A loaded document owns its controls; absent documents expose only status content.

```typescript
interface QueryContentProps<T> {
  /** State from useQuery, or any compatible query observer. */
  query: Pick<QueryState<T>, 'data' | 'status' | 'error'>
  /** Mounted only with a real document, including false, zero and an empty list. */
  children: (data: NonNullable<T>) => ReactNode
  /** Initial idle/loading content. Render a status node, never a fake item or action. */
  pending?: ReactNode
  /** Content for a loaded null record. Null is distinct from an unfinished request. */
  missing?: ReactNode
  /** A failed initial read. Cached data stays visible if its refresh fails. */
  error?: (error: unknown) => ReactNode
}
```

#### `IntentPrefetchProps`

The handlers {@link intentPrefetchProps} returns.

```typescript
interface IntentPrefetchProps {
  onPointerEnter: () => void
  onFocus: () => void
  onTouchStart: () => void
}
```

### Functions

#### `prefetchQuery(options)`

Warms the cache for a document, when the connection can afford it (see
`shouldPrefetch()` in the core). Safe to call repeatedly: a fresh or
in-flight document is skipped, and failures are swallowed.

```typescript
function prefetchQuery<T>(options: QueryOptions<T>): void
```

- `options` — Key, fetch, freshness.

#### `createQueryResource(config)`

Describe one API resource once and get its reads and writes on the shared cache.

A page that loads with `fetch` inside an effect and mirrors the answer into `useState` has to
re-solve the same problems on every screen: a late answer for the previous page lands
over the current one, and a list still shows what it showed before a comment was added.
Here the reads are `useQuery` options (one key per
viewer, page and filter; the previous rows stay until the next answer) and every write puts
the server's own record into the cache and fetches the lists on screen again.

The factory supplies data operations. Mount a keyed
control inside `QueryContent` (your framework's query package: `@molecule/app-query-react`,
`-vue`, …) so it receives a loaded record and stays mounted during refresh.
For a server-backed toggle, use `useOptimisticValue` from your framework binding
(`@molecule/app-react`, `@molecule/app-vue`, …), or `OptimisticToggleButton` from its UI
package (`@molecule/app-ui-react`, …) for a boolean. Pass `toggle` as its
commit adapter, return the saved flag/count, and render the controller's value for the action
label too. Do not block clicks while that commit is pending. The resource example in
`@molecule/app-query-react` composes these APIs; a custom handler must provide the same
readiness and ordering itself.

Markup, labels and routes stay in the app. The factory has no vendor in it: the HTTP client
and the query provider are whatever the app bonded.

```typescript
function createQueryResource<T, Create = Partial<T>, Update = Partial<T>>(
  config: QueryResourceConfig<T>,
): QueryResource<T, Create, Update>
```

- `config` — The resource's name, path, HTTP client and response readers.

**Returns:** List and detail query options, and create, update, remove, toggle and refresh.

#### `QueryContent(props)`

The loaded-data branch receives a non-null document. Pending, failed initial reads and
missing records never mount that branch, so its actions cannot swallow an early click.
Cached data remains mounted during refresh, including a failed refresh. Status fallbacks
belong outside the list or record container rendered by `children`, and so does a refresh
line; the default fallbacks render nothing.

```typescript
function QueryContent<T>({
  query,
  children,
  pending = null,
  missing = null,
  error,
}: QueryContentProps<T>): ReactNode
```

- `props` — Query state, loaded content and optional status fallbacks.

**Returns:** Loaded content or the appropriate fallback.

#### `usePrefetch()`

A stable `prefetch(options)` function for event handlers.

```typescript
function usePrefetch(): <T>(options: QueryOptions<T>) => void
```

**Returns:** The prefetch function.

#### `intentPrefetchProps(options)`

Event handlers that warm a document at the first sign of intent: the
pointer arriving, keyboard focus, or a touch starting. Spread them onto a
link: `<Link {...intentPrefetchProps(packageQuery(name))} />`.

```typescript
function intentPrefetchProps<T>(options: QueryOptions<T>): IntentPrefetchProps
```

- `options` — Key, fetch, freshness.

**Returns:** The handlers.

#### `useQuery(options)`

The document for `options.key`, kept current: cached data is returned on
the very first render (so a warmed page never flashes a loading state),
a stale or missing document is fetched, and every change re-renders.
Pass `null` to observe nothing. A key change resets to that key's state;
the hook never hands a caller another key's document — unless the caller
opts into {@link QueryOptions.keepPreviousData}, and then only within one
{@link QueryOptions.principal}.

The request is stable across re-renders — a parent state change neither
restarts it nor cancels it, so a response that arrives after one still
lands. It is aborted only when the key changes or the component unmounts
(the `signal` given to `options.fetch`). Use this instead of a hand-written
`useEffect` + `fetch`: an effect whose cleanup sets a `cancelled` flag, and
whose deps include a function rebuilt each render, cancels its own request
on every re-render and then skips the refetch.
An explicit `refetch()` is an awaited cache fetch; it can finish after the observer unmounts,
like an explicit `client.fetch(options)` caller.

For a LIST, put the route's page, filter and selected view in the key and
pass `keepPreviousData` with a `principal`: a Next/Previous or filter change
then keeps the rows already on screen until the new page answers, instead of
rendering a loading state over an empty list. The key names everything the
answer depends on, and the app's HTTP client sends the session, so a list the
server can filter or personalize per viewer puts the viewer in its key and
passes the same value as `principal` (`'anonymous'` when signed out): an
account switch then drops the previous account's document immediately. Only
an endpoint that answers every viewer the same takes a viewer-free key with
`principal: 'public'`.

For custom mutation handlers, `setData(saved)` publishes the server's response to this
key and every observer. Use `setData(current => next)` for a local cache update. Render
`data` directly; a component-local copy stops observing later server responses. Prefer
`createQueryResource` when the API's reads and writes can share one resource definition.
Mount record-dependent actions inside `QueryContent` (or an explicit non-null data branch),
so a visible action cannot return early because its initial record is still missing.
Keep loaded actions mounted during refreshes. Server-backed toggles use `useOptimisticValue`
from `@molecule/app-react` or `OptimisticToggleButton` from `@molecule/app-ui-react` to keep
their displayed label and queued clicks on the same state while a save finishes.

```typescript
function useQuery<T>(options: QueryOptions<T> | null): UseQueryResult<T>
```

- `options` — Key, fetch, freshness, and optionally `principal` with `keepPreviousData`; or `null`.

**Returns:** The document's state, `setData()` and `refetch()`. `isPreviousData` is `true` while `data` is the previous key's document for the same principal.

## Injection Notes

### Requirements

Peer dependencies:

- `@molecule/app-query` ^1.2.0
- `react` ^18.0.0 || ^19.0.0

### Runtime Dependencies

- `@molecule/app-query`
- `react`

- **`useQuery` reads the cache synchronously on the first render.** A
  document prefetched from a hovered link, or seeded with `client.set()`
  from a server-rendered JSON island, renders at once — no spinner, no
  layout shift. Render loading from `status === 'idle' || status === 'loading'`;
  `undefined` data can also accompany a completed error. A completed `null`
  response is missing, not pending. The detail example treats only HTTP 404
  or a successful null response as missing; other errors stay load failures.
  The app's bonded HTTP client rejects non-2xx responses. Native `fetch`
  resolves them, so a custom fetcher must check `response.ok` before JSON.
- **Mount a detail region and its actions only after its initial document arrives.**
  A visible container is not a loaded document: a caller may wait for that container and
  read its text once, or click its button, while `data` is still undefined. Put the loading
  message outside the detail region, as in `PackagePage` above. Keep record-dependent
  controls absent or natively disabled until the record exists; returning early inside
  an enabled click handler loses that click. `client.set()` protects a cache mutation
  from an older read, but cannot recover a click whose handler never sent the mutation.
- **The key is the identity.** Building `options` inline is fine; the
  hook resubscribes only when the key's value changes, not when the
  `fetch` closure does.
- **A key change normally resets to the new key's state.** For a list's own
  page/filter/view change, opt into `keepPreviousData` with a `principal`;
  `isPreviousData` tells you the rows on screen belong to the key you just
  left. A completed response (including an empty list) replaces them, and a
  changed principal drops them, so an account switch never shows the previous
  account's rows. Do not emulate this with a local `useState` mirror of the
  query data — that mirror is what serves stale rows under a new page, or
  blanks the list on a re-render.
- **The key names the viewer whenever the answer can depend on it.** The
  app's HTTP client sends the session, so the server may filter or
  personalize even a list that guests can see (a `favorited` or `following`
  flag), and the cache serves a key's document to whoever observes it,
  across sign-in and sign-out. Key such a list on the viewer
  (`user ? String(user.id) : 'anonymous'`), pass the same value as
  `principal`, and pass `null` while the session is still being restored
  (`status === 'loading'`; the HTTP client holds the request until then
  anyway), so restoring a session never swaps a key that already rendered
  rows. A viewer-free key with `principal: 'public'` is only for an endpoint
  that answers every viewer the same. A protected `useListRoute` view also
  passes `null` while `canLoad` is false.
- **Render loading, empty and error status outside the item list**, and never
  give a placeholder the item's own class or element shape: a list read by
  the item class (or by `:first-child`) must contain only real items. An
  empty array is a loaded empty state, not a missing response; render it
  only when `isPreviousData` is not set, because a retained document belongs
  to the key you just left.
- `intentPrefetchProps` spreads three handlers onto a link. It is a plain
  function (not a hook), so it works inside `.map()` too.
- Prefetching respects the browser's data-saver setting and skips 2G
  connections (`shouldPrefetch()` in the core) — do not bypass that for
  "important" links; the person can still click.
- **Refresh a mounted document with `query.refetch()`.** It fetches even a fresh cache
  entry and updates every observer of that key. After a mutation whose response is not the
  whole document, `await query.refetch()` reloads the displayed list. It resolves with the
  resulting state (including `status: 'error'` on failure); a disabled query stays idle.
  Prefer `client.set(key, response)` when the mutation already returned the whole document.
- Errors are not thrown from the hook; read `status === 'error'` and
  `error`. `client.invalidate()` does NOT refetch a mounted page — it only
  marks documents stale, so the page keeps its error (or its old document)
  until the app retries with `client.fetch(options)` or the page subscribes
  again (a key change or a re-mount).
- After a mutation, `client.set(key, response)` paints the server's own
  answer at once and supersedes an older fetch already in flight for that
  key, so its response cannot undo the mutation. An existing `fetch()` caller
  still settles independently of the cache write; read `client.get(key)` for the newest document.
  `client.invalidate(prefix)` marks the affected reads stale for their next
  mount. Which key and which scope is the app's decision: the cache does not
  infer it from auth or form state.

Render resource-dependent lists and controls through {@link QueryContent}. Its child function
receives only loaded, non-null data; loading and error content never mount item actions.
It renders cached content during refresh and treats an empty list, false and zero as data.
Put the list, or the record's own container (its card, header or profile block), inside the
child and every status line (loading, error, `isFetching` refresh) beside it, never inside it:
a reader that finds the container and reads its paragraph must read the record, not "Loading…".

```tsx
<QueryContent
  query={query}
  pending={<p role="status">{loadingLabel}</p>}
  missing={<p>{missingLabel}</p>}
  error={() => <p role="alert">{errorLabel}</p>}
>
  {(record) => <RecordActions record={record} />}
</QueryContent>
```

Keep every resource identity in the query key. A boundary cannot correct a query that supplies
another record's cached data. For a list, map real rows inside the child; never style a status
placeholder as a row. QueryContent is headless and owns no translations or styling.
