Module processor 

ContentProcessor: maps Messages to processContent requests, resolves the acting user id, and evaluates the resulting verdicts.

A scoped-down port of Python’s ScopedContentProcessor — see crate::client’s module docs for exactly what’s cut (the protection- scopes precheck, caching, and background content-activity logging) and why. What is ported faithfully: per-message request construction (the internal build_request) and the GUID-based user-id resolution algorithm (mirrors ScopedContentProcessor._map_messages’s additional_properties["user_id"] / author_name scan, minus the bearer-token-JWT fallback — see the crate docs).

Structs

ContentProcessor

Orchestrates processContent evaluation over a batch of messages. See the module docs for how this differs in scope from Python’s ScopedContentProcessor.

Functions

resolve_user_id

Resolve the acting user id for a batch of messages, mirroring ScopedContentProcessor._map_messages’s resolution order (minus the bearer-token-JWT fallback this port doesn’t perform — see the crate docs):