tben
f2802c1bf3
A coordinator asked to set an uploaded logo as a workspace picture could not: the picture tools take a media id, and nothing ever gave the bot one. Attachments reached the model as "[Attached image \"logo.png\"]", every file tool answers with a [file:ID] ref, and an SVG is deliberately stored as a document rather than an image. - copyMediaAsPicture copies an approved image into a new picture row (bot-image/workspace-image). The source keeps its row and bytes, so a message that attached it still loads and changing a picture can never take a file away from a conversation. - grabPictureSource resolves a picture by [file:ID] (the same scope gate every file tool uses) or by the user's own upload; parseFileRef reads the [file:12] form. - The new set_picture tool ships on every run: a bot sets its own face, the coordinator can also dress a worker. update_workspace gained picture_file_id, and setBotPicture/setProfileImage share the copy and the delete. - removeReplacedPicture deletes a replaced picture only when it really is one, never a chat upload. - uploadAndRecordMedia writes images in their own format: PNG stays PNG with its transparency, WebP stays WebP, GIF becomes PNG, everything else JPEG, and the row records the real mime type (it used to say jpeg for every image). - Pictures change live: BotUpdatedData carries image_media_id and a new server:workspace-updated pushes workspace pictures, relayed between processes. - Attachments are labelled with their media id, and BotFilesNote tells a bot that a [file:ID] can become a picture. - grabRunScopes is now the single source of a run's reachable folders, shared by the file tools, imports and the picture tools.
23 lines
610 B
TypeScript
23 lines
610 B
TypeScript
type Params = {
|
|
/**
|
|
* The name the file was uploaded with.
|
|
*/
|
|
name: string;
|
|
/**
|
|
* Its `media` id.
|
|
*/
|
|
id: number | string;
|
|
};
|
|
|
|
/**
|
|
* How an upload is described to the model: its name and its media id, e.g.
|
|
* `"summit-logo.png", media id 42`.
|
|
*
|
|
* The id matters: the picture tools (`set_picture`, `update_workspace`)
|
|
* take an upload by media id, so a bot that can read the id can act on the
|
|
* image the user sent instead of asking them to upload it again.
|
|
*/
|
|
export default function describeAttachment({ name, id }: Params) {
|
|
return `"${name}", media id ${id}`;
|
|
}
|