messages_around

messages_around is implemented by handleMessagesAround in src/api/handlers/message/messages_around.osl.

Handles the messages around protocol operation through the resource-specific helper and storage layers.

Access

Gate	Requirement
Authentication	Required by the central API gate.
Central permission	None. Resource, channel, ownership, or hierarchy checks may still apply in the handler/helpers.
Broadcast	Not marked global directly by this adapter. A helper may emit focused or server-wide updates.

Request

Every request includes cmd: "messages_around" and may include an opaque listener correlation value.

Field	Validation / meaning
`channel`	`schema.string().defaultValue("")`
`thread_id`	`schema.string().defaultValue("")`
`around`	`schema.string().trim().minLen(1)`
`bounds`	`schema.object({`

Validator source

The handler and shared validation path use these OSL schema definitions before normalization:

*schema.Schema schemaMessagesAround = schema.object({
  channel: schema.string().defaultValue(""),
  thread_id: schema.string().defaultValue(""),
  around: schema.string().trim().minLen(1),
  bounds: schema.object({
    above: schema.integer().defaultValue(50),
    below: schema.integer().defaultValue(50)
  }).defaultValue({})
})

Processing path

handleCmd enforces authentication.
dispatchCmd routes messages_around to handleMessagesAround.
The adapter validates and normalizes input, then calls its domain collaborators.
Durable mutations complete before the response or event is returned.
onMessage adds the request listener to direct responses and performs any marked broadcast.

Direct collaborators visible in the handler: userFromId, channelGet, messageContext, storedMessageAround, true, dbMessageToPublic, typeof, total

Responses and events

Response/event command names visible in this adapter: messages_around.

Validation and domain failures use:

{
  "cmd": "error",
  "val": "<message>",
  "src": "messages_around",
  "listener": "<copied from request>"
}