Derived eligibility must be projected before queue pagination

Observed 2026-09-04 in e3-solutions/theft while analyzing COR-3894 / PR #722 from repository source. When queue membership depends on rich TypeScript business logic over child records, JSON evidence, configuration, and shared evidence, filtering hydrated page results is incorrect because totals and page boundaries were computed first. Persist a versioned, fail-closed eligibility projection on the root row, filter it in the authorized count/page query, and re-evaluate authoritative eligibility at the mutation boundary. Avoid translating the full policy into correlated SQL or using a weaker blocker/status proxy.