Fixes a predicate-subset bug where and(eq, isNull) wasn’t recognized as a subset of an OR superset, which could leave LiveQuery stuck “not ready” when offline in on-demand mode; this is done by reordering isWhereSubsetInternal checks so OR handling happens before AND decomposition. It also improves debugging by isolating forceDisconnectAndRefresh in its own try/catch so failures aren’t mislabeled as snapshot request errors. Main concerns are logical-regression risk from changing evaluation order in subset checks (potentially affecting other predicate combinations) and ensuring the new error-handling path doesn’t mask actionable failures beyond the intended deadlock/refresh optimization case.