Linked Insight Ids

Insight ids linked to the requested entity / event scope.

The browser already holds the whole store from /all-insights, so scoping a browse only needs graph adjacency: it intersects these ids with the corpus it has instead of refetching a listing. Adjacency is not user-specific — provider access is already applied to the store the ids are intersected with.

Scopes AND together, the same way the paginated listing stacks its entity and event pre-filters. Adjacency does not vary with subject/topic/dataset filters, so those are not accepted here — the caller narrows the intersection it already holds.

candidate_id asks the picker's second question against the same intersection: which of the entities on screen would empty it. That belongs here rather than on the entity listing, which is response-cached across all of its filters — folding a per-selection answer into that key would give every distinct selection its own copy of every page, for one bit per row.