export declare const TURN_INTO_APP_ATTACHMENTS_REFERENCE_MD = "# Dispatch Handoff Attachments\n\nWhen calling `start-workspace-app-creation`, pass source files in the `attachments` argument rather than embedding their bytes in `prompt`.\n\n## Uploaded files\n\nImages and PDFs use an upload attachment with a matching base64 data URL:\n\n```ts\n{\n  type: \"upload\",\n  contentType: \"image/webp\" | \"image/png\" | \"image/jpeg\" | \"image/gif\" | \"application/pdf\",\n  name: string,\n  dataUrl: \"data:<contentType>;base64,<BASE64_CONTENT>\",\n  id: string\n}\n```\n\nText and JSON files provide decoded contents instead of a data URL:\n\n```ts\n{\n  type: \"upload\",\n  contentType: \"text/plain\" | \"application/json\",\n  name: string,\n  dataUrl: \"\",\n  text: string,\n  id: string\n}\n```\n\nSend any other text-based file (Markdown, CSV, source code, plain text) as `text/plain` with its real file name, for example `notes.md`. Use a stable or unique `id` for each attachment. A malformed attachment is rejected with `invalid_attachment` and a message naming the problem; fix that attachment and retry, because an unchanged retry fails the same way.\n\n## Public URLs\n\nFor an existing public file that Builder can fetch, use:\n\n```ts\n{\n  type: \"url\",\n  value: \"https://...\"\n}\n```\n\nDo not pass private, localhost, or internal-network URLs.\n\n## Handoff behavior\n\nKeep the original task in `prompt` and tell the Builder agent how each attachment should be used. Put multiple attachments in the same `attachments` array. Attachments are model context only and are not copied into the generated app's workspace.\n";