Read query and mutation state as properties, not accessors

[pathscale]

Corrects the API shape of the primitives added in #284, before any application is written against them.

Why this is needed

I designed createQuery around accessors — query.data() — without first measuring how the code that will consume it is written. solid-query returns a store, so every existing consumer reads properties:

read	occurrences (5 sites sampled)
.data	2097
.isLoading	612
.isSuccess	134
.isError	123
.isPending	182

Roughly 3300 reads. Keeping accessors would have meant editing every file that reads a query, not just the ~300 that define one — and for no benefit, since a getter over a signal subscribes identically.

So this is a straight shape change: getters over the same signals.

What changed

• QueryResult and MutationResult expose data, error, isLoading, isError, isSuccess, isReady (and isPending) as properties.
• refetch, mutate, mutateAsync, reset stay methods, matching what call sites already write.

isPending is carried over deliberately with different meaning, and this is the one thing to look at closely. In solid-query it meant "has no data", which stayed true forever for a query held back by enabled: false — so if (isPending) return <Spinner/> spun for the life of the page. That is the defect that took honey.id's authenticated routes down. Here it means "a fetch is in flight", so a disabled query reads as not pending and its consumer renders instead of hanging. Call sites migrate without edits, but they behave better rather than identically.

Verification

• bun test --conditions=browser src/hooks/data — 8 pass.
• The new one is the load-bearing claim: a createRenderEffect reading q.data re-runs when the fetch resolves. It asserts the subscription, not just the value, because "getters still track" is the whole basis for this change.
• bunx tsc --noEmit clean, biome lint clean on the changed files.

Compatibility

Breaking against 2.12.0. Nothing consumes it yet — 2.12.0 published about a minute before this branch — so the blast radius is zero if it lands before the site migrations start.