[ConsoleTVs]

Summary

fresh render read
  select instance-owned request by key
  reuse across Suspense retries and fresh siblings
  retain after commit
  release after last consumer unmounts

• Honors hook and instance freshness; ordinary cache/expiration policy and explicit fresh actions remain intact.
• Documents first-reader options, remounts, invalidation, abandoned/rejected reads and notification-only configuration.
• Adds public Query.resource / QueryResource. createQuery callers need no migration; hand-written Query implementations must add the resource retain/release protocol. The implementation commit has a BREAKING CHANGE footer.
• Non-destructively merged current main through ad27cc6 (v2.0.0), preserving Fix request ownership across overlapping fetches #12 request ownership, Preserve rendered data on background refetch errors #14 background-error handling, Preserve mutation ordering against older fetches #15 mutation queues/superseded-fetch tracking, and Make React cross-tab query broadcasts explicitly opt-in #13 opt-in caller-owned broadcast channels. Successful queued mutations and hydration synchronize resource promises through cacheItem; both README migration sections remain intact.

Evidence

• Before: React DOM regression made two requests before the first delayed fetch resolved, with no user input (npx vitest run src/react/hooks/useQueryFresh.test.tsx -t 'shares per-hook').
  After: 113 tests pass across 15 files, including 24 tests added relative to current main's 89 tests. Regression coverage includes retries, siblings, rerenders, StrictMode, key/instance changes, remounts, errors, and explicit refreshes.
• Targeted integration: 52 tests pass across resource, mutation-ordering, request-ownership, fresh React, background-error, and broadcast-provider suites. Added cases cover ordered mutations surviving obsolete completion; hydration/resource synchronization with abort/replacement ownership; and fresh provider context retaining caller channel ownership through cleanup.
• npm test, npm run lint, npm run format:check, git diff --check, and sensitive-path checks pass. The final follow-up commit changes documentation only and passes lint/format checks.
• npm run build exits 0 and emits bundles, but reports the existing Solid QueryProvider.tsx:80 TS2786 diagnostic. Reproduced on unchanged current-main baseline ad27cc6; baseline passes 89 tests and prints the same negative-timeout warning category.
• Root npx tsc --build --pretty false remains blocked by baseline React/Solid JSX pollution: 75 diagnostics on current main, 76 here (the additional use-site is the new test rendering the existing QueryProvider). Isolated React/core typechecking has zero diagnostics across 36 root files, including all new tests.
• Initial npm ci reported 16 dependency vulnerabilities. This PR does not change dependencies relative to main.

Merge Danger

Door: two-way

Fresh React reads now share a request lifetime instead of restarting on every render. Uncommitted/rejected selections remain until invalidation or instance collection. Committed consumers retain their successful value through failed refreshes; initial render errors and explicit action rejections retain their existing behavior.

Hand-written Query adapters require migration to implement resource; createQuery callers need no API migration. The breaking-change footer can trigger another major release after main's v2.0.0. Main integration conflicts are resolved; await review/CI before merging.

Hydration updates cache/resource state immediately. The existing async refetch transition can defer the visible update while a request remains pending; this was independently reproduced on unchanged main and is not changed by this fix. Integration tests assert immediate cache/resource synchronization and final rendered state after observers settle.

Blast Radius: consumers

The per-instance resource API synchronizes successful writes only after ownership/supersession checks. Existing imperative query(..., { fresh: true }) still aborts/replaces pending requests. Providers neither create nor close channels. No force push, rebase, reset, or PR merge was performed.