Bulk-resolve actor user_ids to %{email, site_id} in ONE query — so the table's actor column doesn't Ash.get per row (an N+1 that also dragged in the user's permissions/site loads). id = ANY($1::text[]::uuid[]) keeps the param text (Postgrex-friendly) while comparing against the un-cast uuid pkey.

Scoped to the viewer: a site user loads only its own site's users, so another site's or a master's email never reaches the request. A master (a user whose site_id is nil) loads any actor. No viewer, or anything that is not a user, loads nothing. MishkaCmsCore.Activity.Helpers.actor_labels/2 names the rest.

@spec counts(map()) :: %{
  total: non_neg_integer(),
  info: non_neg_integer(),
  warn: non_neg_integer(),
  error: non_neg_integer()
}

How many entries page/1 has to show, as %{total: n, info: n, warn: n, error: n} — the log's KPI row and its "showing 1–20 of N" label.

Takes the same opts as page/1 minus :severity, :limit and :offset: each figure is a COUNT over the very same UNION, so a count always agrees with the list beside it. Like page/1, every branch is capped at @max_cap, so a log past that reports the cap rather than scanning forever.

@spec day_counts(map()) :: %{required(Date.t()) => non_neg_integer()}

How many entries fall on each day, as %{~D[2026-07-16] => 15} — the "15 events" beside a day's heading in the timeline.

Takes the same opts as counts/1. One GROUP BY over the same UNION, so the figure is the day's REAL total rather than however much of that day happens to be loaded — the log pages with load_more, and a heading that counted only the loaded rows would keep changing as you scroll.

@spec max_cap() :: pos_integer()

The most rows any one branch is scanned for — a count that reaches it means "or more".

Runs the unified activity query for one page and returns the entry maps (the MishkaCmsCore.Activity.ActivityEntry shape), already ordered newest-first.

Opts:

• :site_id — the one site to read; nil reads every site, which only a master's reach asks for (MishkaCmsCore.Activity.Helpers.reach/1)

• :kind — "content" | "job" | nil

• :severity — "info" | "warn" | "error" | nil

• :resources — :all (the default) or the "Elixir.Module" strings whose entries are shown, as MishkaCmsCore.Activity.Helpers.resources_for/1 answers for a viewer
• :limit — page size (Ash sets this to page_size + 1 so more? works)
• :offset — page offset

Humanise a "Elixir.A.B.Thing" resource string to "Thing" (spaced).

Grouped options for the resource/source :select filter — one {extension_label, [{resource_label, module_string}]} group per extension (so same-named resources in different extensions, e.g. Blog vs Document "Tag", stay distinct). Covers version parent modules + distinct event-log resource values; the value is the module string the SQL filters on.

Whether a resource shares its global (site_id nil) rows with tenants — true iff it exposes the :for_tenant_with_globals read, the same rule its own admin page uses (Component, Layout, JsHook, Stylesheet). Tenants see global activity only for these; everything else (Page, ErrorPage, Media, blog, document, …) stays own-site-only for tenants.

Bulk-resolve site ids to their name in ONE query (archived included).

@spec total(map()) :: non_neg_integer()

How many entries match opts in total — what page/1 is showing a window of.

Same opts as page/1 minus :limit/:offset. The read hands this to Ash as full_count so the table can say how far into the log a page reaches; Ash.DataLayer.Simple cannot count a manual read by itself. Capped like page/1, so a log past @max_cap reports the cap.