Interface ExecuteGQLOptions

The entities a mutation is known to write. After a mutation the provider drops its RunView dedup-linger entries; with this set, only the entries touching these entities are dropped instead of every entry. The entity Save()/Delete() paths pass their own entity — the same scope the local BaseEntity save/delete event already invalidates. Leave it unset for any mutation whose writes are not known up front (Remote Operations, Actions, agent runs): those drop everything, because a stale replay is worse than a re-query. Ignored for queries.

Rows a server-side save hook writes to OTHER entities are outside the scope, exactly as they were before mutations invalidated at all; code that reads such rows right after the save can call InvalidateRunViewDedupCache() itself.