The single, centralized vehicle for publishing on PUSH_STATUS_UPDATES_TOPIC. Every
publisher — resolver or service — routes through here (resolvers via the
ResolverBase.PublishStatusUpdate wrapper; non-resolvers by calling this directly), so the
payload shape and the required-identity guarantee live in exactly one place. Adding a field to
the push is a one-line change here; a new publisher physically cannot omit ownerUserId.
The single, centralized vehicle for publishing on PUSH_STATUS_UPDATES_TOPIC. Every publisher — resolver or service — routes through here (resolvers via the
ResolverBase.PublishStatusUpdatewrapper; non-resolvers by calling this directly), so the payload shape and the required-identity guarantee live in exactly one place. Adding a field to the push is a one-line change here; a new publisher physically cannot omitownerUserId.