Project derived edges for request. Every data read must go through RunView or RunQuery
with ctx.User so entity permissions and row-level security apply.
ProtectedLogLog that a per-step read hit its row cap, so a truncated neighborhood is visible rather than silently partial.
Projects derived many-to-many edges through a join entity (e.g.,
Person$\to$Organization"Member Of"viaMemberships). Batches one bounded, orderedRunViewper expansion step underctx.User.Every column named in the configuration must be a field of the join entity: it is resolved through entity metadata and the metadata's own field name goes into the filter, so configuration text never reaches SQL as an identifier. An unknown field disables the provider (logged) rather than guessing.