Record one audit event.
The actor arrives as an external id and is resolved here, so callers never
hold the internal FK. Domain services do not call this: activity writes
belong to the dashboard, which is the only layer that knows who is acting
(see lib/userActivities.ts). A domain service taking an actor parameter
is the shape this replaces.
Optionalinput: {OptionalobjectIds?: string[]object_id values to filter by (e.g. tok_… / bow_…).
Optionalpage?: numberOptionalpageSize?: numberOptionaltypes?: (OptionaluserIds?: string[]External ids (adusr_…) of actors to filter by.
Optionalvisibility?: "ALL" | "INTERNAL"
Read and write path for
admin.dashboard_user_activity— the audit feed behind the/tokensand/walletsdetail-panel History sections.Not cached: audit reads are cold and the underlying data changes on every config write, so any cache would be busy churning for no hit-rate gain.