Fix isLoading stuck true with coalesced requests in reactive frameworks

When multiple reactive getters (e.g., in Alpine.js) call .it() for the same
item during a single reactive cycle, the requests are correctly coalesced but
isLoading can remain true even after data is fetched.

Root cause: finalizeItemMeta only set isLoading=false when query IDs matched
or activeQueryId was null. With coalesced requests, especially silent fetches,
the activeQueryId matching logic could fail.

Solution: Explicitly check if ref.data exists. If data is present, the item
is definitively not loading, regardless of query ID matching. This handles
the coalescing edge case while preserving all existing behavior.

This fix ensures proper loading states for:
- Alpine.js reactive computed properties
- React hooks with multiple consumers
- Vue computed properties
- Svelte reactive declarations

Fixes: https://github.com/YidiDev/verity/issues (see BUG.md)
Version: 1.0.7 → 1.0.8

Author: YidiDev

package.json

@@ -1,6 +1,6 @@
 {
   "name": "verity-dl",
-  "version": "1.0.7",
+  "version": "1.0.8",
   "description": "A framework agnostic data layer built to handle the communication layer between the server and the client seamlessly and keep the ui state always up to date with the source of truth",
   "main": "verity/shared/static/lib/core.js",
   "module": "verity/shared/static/lib/core.js",

verity/shared/static/lib/core.js

@@ -1053,7 +1053,11 @@ function finalizeItemMeta(ref, canonicalLevel, qid, overrides = {}, { force = fa
     };
 
     if (!Object.prototype.hasOwnProperty.call(overrides, "isLoading")) {
-        if (matchedActiveQuery || next.activeQueryId == null) {
+        // If we have data, we're definitely not loading
+        // This handles cases where coalesced requests may have mismatched query IDs
+        if (ref.data != null) {
+            next.isLoading = false;
+        } else if (matchedActiveQuery || next.activeQueryId == null) {
             next.isLoading = false;
         }
     }