Remove debug logging - bug is fixed (v1.0.18)

The debug logging in v1.0.17 confirmed the fix works. Removing the
console.error statements as they're no longer needed.

The actual fix was the combination of all previous changes:
- v1.0.11: Explicit isLoading: false in applyFetchedLevel overrides
- v1.0.14: Silent fetch activeQueryId fix
- v1.0.15: Coalescing invariant fix
- v1.0.16: Removed race condition sync

Version: 1.0.17 → 1.0.18

Author: YidiDev

package.json

@@ -1,6 +1,6 @@
 {
   "name": "verity-dl",
-  "version": "1.0.17",
+  "version": "1.0.18",
   "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

@@ -1296,21 +1296,6 @@ function applyFetchedLevel(T, typeName, id, ref, sourceLevelKey, data, timestamp
         isLoading: false,  // Fetch completed successfully, clear loading state
     };
     const nextMeta = finalizeItemMeta(ref, sourceLevelKey, qid, overrides, options);
-    
-    // Debug logging
-    if (nextMeta.isLoading === true) {
-        console.error('[VERITY BUG] finalizeItemMeta returned isLoading=true after fetch completed!', {
-            typeName,
-            id,
-            sourceLevelKey,
-            qid,
-            'ref.meta.activeQueryId': ref.meta.activeQueryId,
-            'ref.meta.isLoading': ref.meta.isLoading,
-            'nextMeta.isLoading': nextMeta.isLoading,
-            'nextMeta.activeQueryId': nextMeta.activeQueryId,
-            overrides
-        });
-    }
 
     assignRef(ref, { data: nextData, meta: nextMeta });
 }