@dai_ming/plugin-deliverables 1.1.0 → 1.1.2

package/INSTALL.md

@@ -1,11 +1,11 @@
 # plugin-deliverables 安装文档
 
-本文档描述 `@dai_ming/plugin-deliverables@1.1.0` 的安装、升级与验证方式。
+本文档描述 `@dai_ming/plugin-deliverables@1.1.2` 的安装、升级与验证方式。
 
 ## 安装
 
 ```bash
-openclaw plugins install @dai_ming/plugin-deliverables@1.1.0 --pin
+openclaw plugins install @dai_ming/plugin-deliverables@1.1.2 --pin
 openclaw plugins enable plugin-deliverables
 ```
 
@@ -13,7 +13,7 @@ gateway 部署配置：
 
 ```yaml
 installPlugins:
-  - "@dai_ming/plugin-deliverables@1.1.0"
+  - "@dai_ming/plugin-deliverables@1.1.2"
 ```
 
 ## 验证

package/README.md

@@ -15,7 +15,7 @@ OpenClaw Native 插件：注册 `deliverables__upload_deliverable` 原生 agent
 ## 安装
 
 ```bash
-openclaw plugins install @dai_ming/plugin-deliverables@1.1.0 --pin
+openclaw plugins install @dai_ming/plugin-deliverables@1.1.2 --pin
 openclaw plugins enable plugin-deliverables
 ```
 
@@ -23,7 +23,7 @@ openclaw plugins enable plugin-deliverables
 
 ```yaml
 installPlugins:
-  - "@dai_ming/plugin-deliverables@1.1.0"
+  - "@dai_ming/plugin-deliverables@1.1.2"
 ```
 
 ## 运行方式

package/agents-rules/deliverables.md

@@ -13,20 +13,21 @@ Tool name note:
 ### Required output behavior
 
 0. Your final assistant message MUST start with 1-2 short sentences in your own words, briefly describing what you produced for the user.
-1. The intro must be based on the actual content/request, not a fixed boilerplate like `交付物已上传成功，可直接在线预览或下载。`
-2. If tool result contains `reply_markdown`, append that field verbatim after your intro on the following lines. Do not rewrite the links inside it.
-3. If tool result has `preview_url`, include one line:
+1. For content deliverables such as articles, documents, reports, and PDFs, add 3-5 concise bullets after the intro summarizing the actual sections, highlights, or conclusions. Do not reply with only a one-sentence upload notice.
+2. The intro and bullets must be based on the actual content/request, not a fixed boilerplate like `交付物已上传成功，可直接在线预览或下载。`
+3. If tool result contains `reply_markdown`, append that field verbatim after your intro and content bullets on the following lines. Do not rewrite the links inside it.
+4. If tool result has `preview_url`, include one line:
    `预览链接：[点击预览](<full_url>)`
-4. If tool result has `download_url`, include one line:
+5. If tool result has `download_url`, include one line:
    `下载链接：[点击下载](<full_url>)`
-5. For multi-file/game deliverables, if tool result already formats the second line as
+6. For multi-file/game deliverables, if tool result already formats the second line as
    `文件列表：[查看目录](<full_url>)`
    then keep that exact label and URL. Do not rewrite it back to a raw long link.
-6. Keep URL target value exactly from tool result (no shortening, no masking, no redirect rewrite).
-7. Use short link labels (`点击预览` / `点击下载` / `查看目录`) to avoid exposing long raw URLs.
-8. Do not say "已上传/已完成" without links.
-9. Do not output naked long URLs outside Markdown link syntax.
-10. Keep the intro concise; do not paste the full file content, saved-path text, or a long summary after the Markdown links.
+7. Keep URL target value exactly from tool result (no shortening, no masking, no redirect rewrite).
+8. Use short link labels (`点击预览` / `点击下载` / `查看目录`) to avoid exposing long raw URLs.
+9. Do not say "已上传/已完成" without links.
+10. Do not output naked long URLs outside Markdown link syntax.
+11. Keep the intro and bullets concise; do not paste the full file content, saved-path text, or a long summary after the Markdown links.
 
 ### Forbidden output behavior
 
@@ -36,12 +37,13 @@ Tool name note:
 - Outputting only naked long URL without Markdown link label
 - Replacing `文件列表：[查看目录](...)` with a naked URL or a zip description
 - Using a generic boilerplate intro that does not mention the actual deliverable content
+- For document/PDF deliverables, replying with only one sentence before the links
 <!-- DELIVERABLE_LINK_RULES_END -->
 
 <!-- DELIVERABLE_AUTO_UPLOAD_RULES_START -->
 ## Deliverables -- Auto Upload for Document Requests (HARD CONSTRAINT)
 
-When user asks to write/generate/create a file, document, article, report, HTML, PPT, plan, guide, markdown, introduction, biography, strategy, summary, or similar artifact, you MUST upload it as a deliverable by default.
+When user asks to write/generate/create a file, document, article, report, PDF, HTML, PPT, plan, guide, markdown, introduction, biography, strategy, summary, or similar artifact, you MUST upload it as a deliverable by default.
 
 Tool name note:
 
@@ -54,26 +56,30 @@ Tool name note:
 1. Create content under current agent workspace `output/` directory first (for example `output/report.md`), then call the deliverables upload tool exposed in this session.
 2. If you need to use the `write` tool, the target path MUST be inside `output/`. Never write deliverable files to the workspace root.
 3. If you already wrote the file to the wrong place, move/copy it into `output/` before finalizing the task and before describing the saved path to the user.
-4. For binary deliverables such as PDF, PPT, images, video, or zip files, pass `file_path` pointing at the file under `output/`; do not paste shell output or partial base64 into `content_base64`.
-5. If the upload tool returns an error, retry with a valid `file_path` or report the upload failure. Never invent OSS, preview, or download URLs.
-6. If format is HTML, prefer `type=article` and file name ends with `.html`.
-7. Every single-file deliverable MUST use a file name with an explicit extension.
-8. If format is markdown/text, use `type=article` and `.md`/`.txt`.
-9. If the user did not specify a document/text format, default to Markdown and use a `.md` file name.
-10. For multi-file deliverables (game/site), you MUST prefer `type=game` with `files[]`, keep files as a folder structure, and do NOT zip before upload unless the user explicitly asks for a zip package.
-11. Static multi-file game/site deliverables SHOULD include a root `index.html` so the preview link can open the homepage directly.
-12. If a generated project requires starting a separate backend service, custom port, database, or long-running process to work, do NOT pretend the deliverables preview can run it. Tell the user that deliverables preview only supports static output, and that runtime projects need deployment/ingress instead.
-13. After successful upload, the final assistant message MUST start with 1-2 short sentences in your own words, briefly describing what you generated for the user.
-14. The intro must be based on the actual deliverable content/request, not a fixed sentence like `交付物已上传成功，可直接在线预览或下载。`
-15. If tool result contains `reply_markdown`, append that field verbatim after your intro on the following lines.
-16. Otherwise final reply MUST include Markdown links (short label + full URL target):
+4. For simple text PDFs, call `deliverables__upload_deliverable` directly with `type=pdf`, a `.pdf` `file_name`, and `content_text`; the tool renders a basic PDF without installing dependencies.
+5. For existing binary deliverables such as rich PDFs, PPT, images, video, or zip files, pass `file_path` pointing at the file under `output/`; do not paste shell output or partial base64 into `content_base64`.
+6. Never run `pip install`, `npm install`, `apt-get`, or similar dependency installation just to create a PDF. Use built-in tools or the PDF `content_text` fallback; if rich PDF generation is unavailable, say so clearly.
+7. If the user asks for PDF, upload a `.pdf` deliverable with `type=pdf`; do not substitute HTML or Markdown unless PDF generation truly failed and you clearly say so.
+8. If the upload tool returns an error, retry with valid parameters or report the upload failure. Never invent OSS, preview, or download URLs.
+9. If format is HTML, prefer `type=article` and file name ends with `.html`.
+10. Every single-file deliverable MUST use a file name with an explicit extension.
+11. If format is markdown/text, use `type=article` and `.md`/`.txt`.
+12. If the user did not specify a document/text format, default to Markdown and use a `.md` file name.
+13. For multi-file deliverables (game/site), you MUST prefer `type=game` with `files[]`, keep files as a folder structure, and do NOT zip before upload unless the user explicitly asks for a zip package.
+14. Static multi-file game/site deliverables SHOULD include a root `index.html` so the preview link can open the homepage directly.
+15. If a generated project requires starting a separate backend service, custom port, database, or long-running process to work, do NOT pretend the deliverables preview can run it. Tell the user that deliverables preview only supports static output, and that runtime projects need deployment/ingress instead.
+16. After successful upload, the final assistant message MUST start with 1-2 short sentences in your own words, briefly describing what you generated for the user.
+17. For content deliverables such as articles, documents, reports, and PDFs, add 3-5 concise bullets after the intro summarizing the actual sections, highlights, or conclusions. Do not reply with only a one-sentence upload notice.
+18. The intro and bullets must be based on the actual deliverable content/request, not a fixed sentence like `交付物已上传成功，可直接在线预览或下载。`
+19. If tool result contains `reply_markdown`, append that field verbatim after your intro and content bullets on the following lines.
+20. Otherwise final reply MUST include Markdown links (short label + full URL target):
    `预览链接：[点击预览](<full_url>)`
    `下载链接：[点击下载](<full_url>)`
-17. For multi-file/game deliverables, if the tool gives directory-style output, the second line may be:
+21. For multi-file/game deliverables, if the tool gives directory-style output, the second line may be:
    `文件列表：[查看目录](<full_url>)`
    Keep that format instead of forcing a zip link.
-18. Do NOT only say "已保存到工作空间".
-19. Do NOT append workspace path or a raw URL block after the Markdown links.
+22. Do NOT only say "已保存到工作空间".
+23. Do NOT append workspace path or a raw URL block after the Markdown links.
 
 ### Exception
 

package/index.js

@@ -53,6 +53,7 @@ const TEXT_EXTENSIONS = new Set([
 const IMAGE_EXTENSIONS = new Set([".apng", ".avif", ".bmp", ".gif", ".ico", ".jpeg", ".jpg", ".png", ".svg", ".webp"]);
 const VIDEO_EXTENSIONS = new Set([".avi", ".m4v", ".mkv", ".mov", ".mp4", ".mpeg", ".mpg", ".webm"]);
 const PPT_EXTENSIONS = new Set([".ppt", ".pptx"]);
+const PDF_EXTENSIONS = new Set([".pdf"]);
 const ARCHIVE_EXTENSIONS = new Set([".7z", ".gz", ".rar", ".tar", ".tgz", ".zip"]);
 const IGNORED_PATH_PARTS = new Set([
   ".git",
@@ -76,13 +77,16 @@ const RUNTIME_DELIVERABLES_GUIDANCE = [
   "## Deliverables Runtime Guard (HARD CONSTRAINT)",
   "",
   "- These rules apply to the main agent and all subagents.",
-  "- When the user asks for a document, article, report, HTML page, Markdown file, PPT, image, archive, game, or any other file deliverable, you MUST create it under the current workspace `output/` directory and upload it with `deliverables__upload_deliverable`.",
-  "- For binary deliverables such as PDF, PPT, images, video, or zip files, pass `file_path` to `deliverables__upload_deliverable` after writing the file under `output/`; do not paste command output or partial base64 into `content_base64`.",
+  "- When the user asks for a document, article, report, PDF, HTML page, Markdown file, PPT, image, archive, game, or any other file deliverable, you MUST create it under the current workspace `output/` directory and upload it with `deliverables__upload_deliverable`.",
+  "- For simple text PDF deliverables, call `deliverables__upload_deliverable` with `type: \"pdf\"`, a `.pdf` `file_name`, and `content_text`; the tool will render a basic PDF without installing dependencies.",
+  "- For existing binary deliverables such as rich PDFs, PPT, images, video, or zip files, pass `file_path` to `deliverables__upload_deliverable` after writing the file under `output/`; do not paste command output or partial base64 into `content_base64`.",
+  "- Never install PDF libraries or other packages at runtime just to create a deliverable. Use built-in tools or the PDF `content_text` fallback; if a rich PDF renderer is unavailable, say so clearly.",
+  "- If the user asks for PDF, upload the generated `.pdf` as `type: \"pdf\"`; do not substitute HTML or Markdown unless PDF generation truly failed and you clearly say so.",
   "- Every single-file deliverable must use a file name with an explicit extension. If the user did not specify a document/text format, default to Markdown and use a `.md` file name.",
   "- Do not use direct message attachments to deliver generated files. This includes the message tool attachment fields such as `media`, `path`, `filePath`, `buffer`, `attachment`, or similar file-carrying fields.",
   "- Do not emit `MEDIA:` file references for user-facing deliverables. Deliverable links must come from the deliverables upload tool instead.",
   "- If the deliverables upload tool returns an error, retry with a valid `file_path` or explain the upload failure; never invent or rewrite OSS/download URLs.",
-  "- After a successful upload, reply with a substantive content summary before the links. For documents/articles/reports, prefer 1 short intro plus 3-6 concise bullets covering key sections, highlights, or findings, then preserve the Markdown links returned by the deliverables tool.",
+  "- After a successful upload, reply with a substantive content summary before the links. For documents/articles/reports/PDFs, include 1 short intro plus 3-5 concise bullets covering the actual sections, highlights, or findings; never respond with only a generic one-sentence upload notice.",
 ].join("\n");
 
 const UPLOAD_DELIVERABLE_TOOL = {
@@ -109,7 +113,7 @@ const UPLOAD_DELIVERABLE_TOOL = {
       },
       type: {
         type: "string",
-        enum: ["article", "game", "zip", "image", "video", "ppt", "link"],
+        enum: ["article", "game", "zip", "image", "video", "ppt", "pdf", "link"],
         description: "交付物类型。若使用 file_path 且未准确判断，可由插件按文件扩展名兜底。",
       },
       file_name: {
@@ -122,7 +126,7 @@ const UPLOAD_DELIVERABLE_TOOL = {
       },
       content_text: {
         type: "string",
-        description: "文本内容（Markdown、HTML 等）。",
+        description: "文本内容（Markdown、HTML 等）。type=pdf 时可传纯文本/Markdown，插件会生成基础 PDF。",
       },
       content_base64: {
         type: "string",
@@ -215,6 +219,9 @@ function deliverableTypeForPath(filePath, isDirectory) {
   if (PPT_EXTENSIONS.has(ext)) {
     return "ppt";
   }
+  if (PDF_EXTENSIONS.has(ext)) {
+    return "pdf";
+  }
   if (ARCHIVE_EXTENSIONS.has(ext)) {
     return "zip";
   }
@@ -655,6 +662,8 @@ function defaultExtensionForDeliverable(args) {
       return ".zip";
     case "ppt":
       return ".pptx";
+    case "pdf":
+      return ".pdf";
     case "image":
       return ".png";
     case "video":
@@ -664,6 +673,155 @@ function defaultExtensionForDeliverable(args) {
   }
 }
 
+function normalizePDFSourceText(contentText, fallbackTitle) {
+  const text = trimString(contentText) || trimString(fallbackTitle) || "PDF deliverable";
+  return text
+    .replace(/\r\n/g, "\n")
+    .replace(/\r/g, "\n")
+    .split("\n")
+    .map((line) =>
+      line
+        .replace(/^#{1,6}\s+/, "")
+        .replace(/\*\*([^*]+)\*\*/g, "$1")
+        .replace(/`([^`]+)`/g, "$1")
+        .replace(/^\s*[-*]\s+/, "- ")
+        .trimEnd(),
+    )
+    .join("\n")
+    .slice(0, 20000);
+}
+
+function visualWidth(text) {
+  let width = 0;
+  for (const ch of String(text || "")) {
+    width += ch.charCodeAt(0) > 0xff ? 2 : 1;
+  }
+  return width;
+}
+
+function wrapPDFTextLine(line, maxWidth) {
+  const input = String(line || "");
+  if (input.length === 0) {
+    return [""];
+  }
+  const out = [];
+  let current = "";
+  for (const ch of input) {
+    if (current && visualWidth(current + ch) > maxWidth) {
+      out.push(current);
+      current = ch;
+    } else {
+      current += ch;
+    }
+  }
+  if (current) {
+    out.push(current);
+  }
+  return out;
+}
+
+function utf16BEHex(text) {
+  const input = String(text || "");
+  const bytes = [0xfe, 0xff];
+  for (let i = 0; i < input.length; i += 1) {
+    const code = input.charCodeAt(i);
+    bytes.push((code >> 8) & 0xff, code & 0xff);
+  }
+  return Buffer.from(bytes).toString("hex").toUpperCase();
+}
+
+function buildPDFObjects(objects) {
+  const chunks = ["%PDF-1.4\n%\xE2\xE3\xCF\xD3\n"];
+  const offsets = [0];
+  let length = Buffer.byteLength(chunks[0], "utf8");
+  for (const obj of objects) {
+    const body = `${obj.id} 0 obj\n${obj.body}\nendobj\n`;
+    offsets[obj.id] = length;
+    chunks.push(body);
+    length += Buffer.byteLength(body, "utf8");
+  }
+  const xrefOffset = length;
+  const maxID = objects.reduce((max, obj) => Math.max(max, obj.id), 0);
+  const xref = ["xref\n", `0 ${maxID + 1}\n`, "0000000000 65535 f \n"];
+  for (let id = 1; id <= maxID; id += 1) {
+    xref.push(`${String(offsets[id] || 0).padStart(10, "0")} 00000 n \n`);
+  }
+  xref.push(
+    "trailer\n",
+    `<< /Size ${maxID + 1} /Root 1 0 R >>\n`,
+    "startxref\n",
+    `${xrefOffset}\n`,
+    "%%EOF\n",
+  );
+  return Buffer.from(chunks.join("") + xref.join(""), "utf8");
+}
+
+function createBasicTextPDF(contentText, fileName) {
+  const normalized = normalizePDFSourceText(contentText, fileName);
+  const wrappedLines = [];
+  for (const line of normalized.split("\n")) {
+    wrappedLines.push(...wrapPDFTextLine(line, 72));
+  }
+  const linesPerPage = 44;
+  const pages = [];
+  for (let i = 0; i < wrappedLines.length; i += linesPerPage) {
+    pages.push(wrappedLines.slice(i, i + linesPerPage));
+  }
+  if (pages.length === 0) {
+    pages.push(["PDF deliverable"]);
+  }
+
+  const pageIDs = pages.map((_, idx) => 3 + idx);
+  const fontID = 3 + pages.length;
+  const cidFontID = fontID + 1;
+  const contentStartID = cidFontID + 1;
+  const objects = [
+    { id: 1, body: "<< /Type /Catalog /Pages 2 0 R >>" },
+    {
+      id: 2,
+      body: `<< /Type /Pages /Kids [${pageIDs.map((id) => `${id} 0 R`).join(" ")}] /Count ${pages.length} >>`,
+    },
+  ];
+
+  pages.forEach((pageLines, idx) => {
+    const contentID = contentStartID + idx;
+    objects.push({
+      id: pageIDs[idx],
+      body: `<< /Type /Page /Parent 2 0 R /MediaBox [0 0 595 842] /Resources << /ProcSet [/PDF /Text] /Font << /F1 ${fontID} 0 R >> >> /Contents ${contentID} 0 R >>`,
+    });
+  });
+
+  objects.push(
+    {
+      id: fontID,
+      body: `<< /Type /Font /Subtype /Type0 /BaseFont /STSong-Light /Encoding /UniGB-UCS2-H /DescendantFonts [${cidFontID} 0 R] >>`,
+    },
+    {
+      id: cidFontID,
+      body:
+        "<< /Type /Font /Subtype /CIDFontType0 /BaseFont /STSong-Light /CIDSystemInfo << /Registry (Adobe) /Ordering (GB1) /Supplement 2 >> /DW 1000 >>",
+    },
+  );
+
+  pages.forEach((pageLines, idx) => {
+    const streamLines = ["BT", "/F1 12 Tf", "50 790 Td", "16 TL"];
+    pageLines.forEach((line) => {
+      if (line) {
+        streamLines.push(`<${utf16BEHex(line)}> Tj`);
+      }
+      streamLines.push("T*");
+    });
+    streamLines.push("ET");
+    const stream = `${streamLines.join("\n")}\n`;
+    objects.push({
+      id: contentStartID + idx,
+      body: `<< /Length ${Buffer.byteLength(stream, "utf8")} >>\nstream\n${stream}endstream`,
+    });
+  });
+
+  return buildPDFObjects(objects);
+}
+
 function normalizeDeliverableFileName(args, fallbackName) {
   let fileName = trimString(args && args.file_name) || trimString(fallbackName) || "file";
   if (trimString(args && args.type) === "link") {
@@ -758,8 +916,14 @@ function buildNativeUploadRequestBody(args) {
     body.files = files;
     return { body, isDirectory: true };
   }
-  body.contentText = (args && (args.content_text || args.contentText)) || "";
-  body.contentBase64 = (args && (args.content_base64 || args.contentBase64)) || "";
+  const contentText = (args && (args.content_text || args.contentText)) || "";
+  const contentBase64 = (args && (args.content_base64 || args.contentBase64)) || "";
+  if (body.type === "pdf" && trimString(contentText) && !trimString(contentBase64)) {
+    body.contentBase64 = createBasicTextPDF(contentText, body.fileName).toString("base64");
+  } else {
+    body.contentText = contentText;
+    body.contentBase64 = contentBase64;
+  }
   return { body, isDirectory: false };
 }
 
@@ -1787,6 +1951,8 @@ const plugin = {
 };
 
 plugin.__test = {
+  buildNativeUploadRequestBody,
+  createBasicTextPDF,
   deliverableTypeForPath,
   extractFileReferencesFromText,
   extractDeliverableURL,

package/openclaw-plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "plugin-deliverables",
-  "version": "1.1.0",
+  "version": "1.1.2",
   "npm_package": "@dai_ming/plugin-deliverables",
   "description": "Deliverables plugin: native upload tool + skill + AGENTS rules for AI-generated file uploads",
   "skills": {

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "plugin-deliverables",
   "name": "Deliverables",
   "description": "Deliverables runtime guard for upload-first file delivery with Palz split-send diagnostics.",
-  "version": "1.1.0",
+  "version": "1.1.2",
   "skills": ["./skills"],
   "configSchema": {
     "type": "object",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dai_ming/plugin-deliverables",
-  "version": "1.1.0",
+  "version": "1.1.2",
   "description": "OpenClaw deliverables native plugin — upload AI-generated files to OSS and return shareable preview/download links",
   "keywords": [
     "openclaw",

package/skills/deliverables/SKILL.md

@@ -5,7 +5,7 @@ description: 上传AI生成的文件到交付物系统，返回可分享的预
 
 # 文件交付规则（强制）
 
-当你生成了文件内容（文章、文档、介绍、攻略、HTML页面、Markdown、游戏、图片等），**必须**调用交付物上传工具，不得把文件内容直接粘贴在消息里。
+当你生成了文件内容（文章、文档、介绍、攻略、PDF、HTML页面、Markdown、游戏、图片等），**必须**调用交付物上传工具，不得把文件内容直接粘贴在消息里。
 
 ## 工具名说明（强制）
 
@@ -31,17 +31,20 @@ description: 上传AI生成的文件到交付物系统，返回可分享的预
 | `resource_id` | 消息元数据中的 `resource_id` 字段 | `user_xxx_lobster_yyy` |
 | `group_id` | 消息元数据中的 `group_id` 或 `conversation_id` | `group_abc123` |
 | `user_id` | 消息元数据中的 `sender_id` 或 `owner_id` | `cbb0fab9...` |
-| `type` | 根据内容选择：`article`/`game`/`image`/`video`/`ppt`/`zip`/`link` | `article` |
+| `type` | 根据内容选择：`article`/`game`/`image`/`video`/`ppt`/`pdf`/`zip`/`link` | `article` |
 | `file_name` | 有意义的文件名，单文件必须含扩展名；若用户未指定文档格式，默认用 `.md` | `report-2026.html` |
-| `content_text` | 文件的完整文本内容（HTML/Markdown等） | `<html>...</html>` |
+| `content_text` | 文件的完整文本内容（HTML/Markdown等）；简单 PDF 可传文本/Markdown，由工具生成基础 PDF | `<html>...</html>` |
 | `file_path` | PDF/PPT/图片/zip 等二进制文件的本地路径，推荐使用，避免手工复制 base64 | `output/sample.pdf` |
 
 > **直接对话（direct chat）时**：`group_id` 填 `conversation_id`，`user_id` 填 `owner_id`。
 
 ## 二进制文件上传（强制）
 
-- PDF、PPT、图片、视频、zip 等二进制文件必须优先传 `file_path`，不要把 `base64` 命令输出复制到 `content_base64`。
+- 简单文本 PDF 可以直接调用 `deliverables__upload_deliverable`：`type=pdf`、`.pdf` 文件名、`content_text` 填完整内容；工具会生成基础 PDF，不需要额外依赖。
+- 已经生成好的 PDF、PPT、图片、视频、zip 等二进制文件必须优先传 `file_path`，不要把 `base64` 命令输出复制到 `content_base64`。
 - `file_path` 指向你已经写入 `output/` 的文件，例如 `output/sample.pdf`；上传工具会读取文件并自动编码。
+- 不要为了生成 PDF 临时执行 `pip install`、`npm install`、`apt-get` 等依赖安装。使用已有工具或上面的 PDF `content_text` 兜底；如果复杂 PDF 渲染器不可用，要明确说明限制。
+- 用户要求 PDF 时，必须上传 `.pdf` 交付物，`type` 使用 `pdf`；不要只返回 HTML/Markdown 作为替代格式。
 - 如果上传工具返回错误，必须修正参数后重试，或明确告诉用户上传失败；禁止编造 OSS、下载或预览链接。
 
 ## 多文件（游戏）
@@ -64,9 +67,10 @@ files: [
 ## 上传成功后
 
 优先规则：
-- 最终消息必须先用你自己的话写 1-2 句简短介绍，粗略说明你生成了什么内容、包含哪些重点。
-- 这句介绍必须基于实际产物内容，不要使用固定模板，例如：`交付物已上传成功，可直接在线预览或下载。`
-- 如果工具结果里有 `reply_markdown`，把它原样放在这句介绍后面，不要改写其中的链接。
+- 最终消息必须先用你自己的话写 1-2 句简短介绍，说明你生成了什么内容。
+- 对文章、文档、报告、PDF 等内容型交付物，介绍后必须补充 3-5 条内容要点，概括实际章节、重点信息或结论；不要只写一句“已上传/已生成”。
+- 介绍和要点必须基于实际产物内容，不要使用固定模板，例如：`交付物已上传成功，可直接在线预览或下载。`
+- 如果工具结果里有 `reply_markdown`，把它原样放在内容要点后面，不要改写其中的链接。
 
 否则只发给用户：
 - 预览链接（`preview_url`，必须用 Markdown 链接格式）