MessageAttachment
userMessage image attachment metadata: metadata only —
the durable bytes live in the log and are reachable on the raw altitude.
Fields and variants
Section titled “Fields and variants”attachmentIdheightmediaTypetypewidth
Source
schema/msp/experimental/msp.schema.json#/types/MessageAttachment
{ "description": "`userMessage` image attachment metadata: metadata only —\nthe durable bytes live in the log and are reachable on the raw altitude.", "properties": { "attachmentId": { "description": "This attachment's name, `<itemId>/<n>` — the item's id plus this\nentry's 1-based position in its `attachments` array. Name only: no link form and no byte read\nby id.\n\nSet by the server on every attachment entry it emits, and identical\non live, paging, snapshot and rebuild paths. Optional\nin the schema so older servers stay valid; clients compare and store\nthe whole string and MUST NOT parse it (ADR 42850).", "type": "string" }, "height": { "description": "Pixel height, when known.", "type": "integer" }, "mediaType": { "description": "The image media type (e.g. `\"image/png\"`).", "type": "string" }, "type": { "description": "Attachment type, `\"image\"` in v1 (free string: attachment vocabulary\ngrows additively with the runtime's intake surface).", "type": "string" }, "width": { "description": "Pixel width, when known.", "type": "integer" } }, "required": [ "mediaType", "type" ], "type": "object"}