AIKIDO-2026-746176

TL;DR

Ash's resolve_parent_in_filter/3 silently replaces a failed parent(...) filter evaluation with nil instead of returning an error, so a no_attributes?: true relationship's scoping filter degrades from an equality check into an IS NULL check. Applications that expose a parent(...) filter over an HTTP boundary return other tenants' records whenever the referenced parent attribute is not selected on the source query, because the degraded filter matches on absence rather than on the caller's own scope. The fix makes the evaluation failure raise instead of falling back to nil.