typeclaw 0.31.1 → 0.32.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "typeclaw",
-  "version": "0.31.1",
+  "version": "0.32.0",
   "homepage": "https://github.com/typeclaw/typeclaw#readme",
   "bugs": {
     "url": "https://github.com/typeclaw/typeclaw/issues"

package/src/agent/session-origin.ts

@@ -129,14 +129,34 @@ type PlatformInfo = {
   // the call would no-op. Keep in sync with the adapters that call
   // `router.registerReaction` (github, slack-bot, discord-bot today).
   supportsReactions: boolean
+  // Whether this adapter's OutboundCallback accepts file attachments. Gates the
+  // "ship a researcher report as a PDF by default" prompt guidance: a report is
+  // only worth converting to a downloadable file on channels that can actually
+  // receive one. GitHub's outbound callback hard-rejects attachments
+  // (`github-bot-does-not-support-attachments` in adapters/github/outbound.ts),
+  // so a PDF nudge there would train the model toward a call that always fails;
+  // the other four upload files (Slack `uploadFile`, Discord `uploadFile`,
+  // Telegram `sendDocument`, KakaoTalk `sendAttachment`). Keep in sync with the
+  // adapters' outbound callbacks.
+  supportsAttachments: boolean
 }
 
 const PLATFORM_INFO: Record<AdapterId, PlatformInfo> = {
-  'slack-bot': { displayName: 'Slack', mentionMode: 'angle-id', supportsReactions: true },
-  'discord-bot': { displayName: 'Discord', mentionMode: 'angle-id', supportsReactions: true },
-  github: { displayName: 'GitHub', mentionMode: 'at-username', supportsReactions: true },
-  'telegram-bot': { displayName: 'Telegram', mentionMode: 'at-username', supportsReactions: false },
-  kakaotalk: { displayName: 'KakaoTalk', mentionMode: 'alias', supportsReactions: false },
+  'slack-bot': { displayName: 'Slack', mentionMode: 'angle-id', supportsReactions: true, supportsAttachments: true },
+  'discord-bot': {
+    displayName: 'Discord',
+    mentionMode: 'angle-id',
+    supportsReactions: true,
+    supportsAttachments: true,
+  },
+  github: { displayName: 'GitHub', mentionMode: 'at-username', supportsReactions: true, supportsAttachments: false },
+  'telegram-bot': {
+    displayName: 'Telegram',
+    mentionMode: 'at-username',
+    supportsReactions: false,
+    supportsAttachments: true,
+  },
+  kakaotalk: { displayName: 'KakaoTalk', mentionMode: 'alias', supportsReactions: false, supportsAttachments: true },
 }
 
 function getPlatformInfo(adapter: AdapterId): PlatformInfo {
@@ -461,6 +481,7 @@ function renderChannelOrigin(
     "matching the channel's `allow` rules are accepted (the tool returns",
     '`{ ok: false }` otherwise).',
     '',
+    ...renderResearchReportDeliveryGuidance(platformInfo),
     ...renderMentionGuidance(platformInfo, origin.participants ?? [], now, origin.self),
   )
 
@@ -496,6 +517,30 @@ function renderMembershipSummary(
   return `This channel has approximately ${total} members (about ${membership.humans} humans, ${membership.bots} bots — the bot count is approximate, the full member list was not enumerated because it exceeds the 50-member cap). The 10 most recent speakers are listed below.`
 }
 
+// The `researcher` subagent always hands back a markdown report file
+// (`research-<slug>.md`) and is itself read-only — it cannot produce the PDF.
+// Whoever delivers that report to a channel is the one who decides the format,
+// and on a channel that accepts file uploads the right default for a multi-page
+// research report is a downloadable PDF, not a wall of raw markdown dumped into
+// chat. This block makes that the default ONLY where it is actionable: gated on
+// `supportsAttachments` so GitHub (whose outbound callback rejects attachments)
+// never gets a nudge toward a `channel_send` call that would fail.
+function renderResearchReportDeliveryGuidance(platformInfo: PlatformInfo): string[] {
+  if (!platformInfo.supportsAttachments) return []
+  return [
+    `**Ship \`researcher\` reports as a PDF by default.** ${platformInfo.displayName} accepts file`,
+    'attachments. When you receive a `researcher` subagent result — a',
+    '`research-<slug>.md` report file path in its `<report>` block — convert that',
+    'markdown to a PDF with the `typeclaw-markdown-pdf` skill and deliver it with',
+    '`channel_send({ ..., attachments: [{ path, filename }] })`, with a one- or',
+    'two-line summary as the message text. A downloadable file is what a human',
+    'wants for a multi-page report; do not paste the full markdown into chat. Send',
+    'the report inline as plain text only if the caller explicitly asked for it in',
+    'the message, or the report is short enough that a file would be overkill.',
+    '',
+  ]
+}
+
 function renderMentionGuidance(
   platformInfo: PlatformInfo,
   participants: readonly ChannelParticipant[],

package/src/skills/typeclaw-markdown-pdf/SKILL.md

@@ -108,7 +108,7 @@ fonts/margins only if the user asks.
     #counter(page).display("1 / 1", both: true)
   ]),
 )
-#set text(font: ("Libertinus Serif", "New Computer Modern"), size: 11pt, lang: "en")
+#set text(font: ("Libertinus Serif", "New Computer Modern", "Noto Serif CJK KR"), size: 11pt, lang: "en")
 #set par(justify: true, leading: 0.68em, spacing: 1.1em)
 
 #show heading: set text(weight: "semibold")
@@ -136,9 +136,15 @@ Notes:
 - `read("report.md")` is **relative to the workspace** (the compiler's `workspace`
   is set to `workspace/` — see Step 3). Keep the `.typ` and `.md` in `workspace/`.
 - Fonts `Libertinus Serif` / `New Computer Modern` are bundled with Typst (no font
-  install). For Korean/CJK body text, add `"Noto Serif CJK KR"` to the `font:` list
-  and pass that font dir to `fontPaths` in Step 3 (the container's `cjkFonts` toggle
-  installs `fonts-noto-cjk` under `/usr/share/fonts`).
+  install) and carry the Latin text. `"Noto Serif CJK KR"` is appended as the
+  fallback so Korean/CJK glyphs resolve per-glyph — Typst falls through to it
+  wherever the Latin fonts have no glyph, leaving Latin runs untouched. It comes
+  from `fonts-noto-cjk`, which Step 3's renderer loads from `/usr/share/fonts` via
+  `fontPaths`. **The package is only present when the container's `cjkFonts` toggle
+  resolves to `true`.** Its default is `"auto"`, which installs the fonts only when
+  the host locale is CJK (`ja`/`ko`/`zh`) — so on a non-CJK host, CJK PDFs still
+  render as tofu until you set `docker.file.cjkFonts: true` in `typeclaw.json` and
+  rebuild. If your CJK font lives elsewhere, add its dir to the `fontPaths` list.
 
 ## Step 3 — render
 
@@ -149,15 +155,23 @@ writes the PDF. Pass the wrapper and output paths as arguments.
 ```ts
 // workspace/.tools/render.ts
 import { NodeCompiler } from '@myriaddreamin/typst-ts-node-compiler'
-import { writeFileSync } from 'node:fs'
+import { existsSync, writeFileSync } from 'node:fs'
 
 const [, , mainFile, outFile] = process.argv
 if (!mainFile || !outFile) throw new Error('usage: render.ts <main.typ> <out.pdf>')
 
+// Load system fonts so CJK glyphs resolve. The compiler does NOT auto-discover
+// system font dirs the way the Typst CLI does — without explicit fontPaths,
+// "Noto Serif CJK KR" (from fonts-noto-cjk under /usr/share/fonts) is invisible
+// and Korean/Japanese/Chinese text renders as .notdef tofu boxes. Filtered with
+// existsSync so a missing dir (e.g. on a dev/host run) is skipped, not fatal.
+const fontPaths = ['/usr/share/fonts', '/usr/local/share/fonts', '/Library/Fonts', '/System/Library/Fonts'].filter(
+  existsSync,
+)
+
 const compiler = NodeCompiler.create({
   workspace: '.', // run from workspace/, so read("report.md") resolves
-  // Add CJK / extra font dirs here if needed:
-  // fontArgs: [{ fontPaths: ["/usr/share/fonts"] }],
+  ...(fontPaths.length > 0 ? { fontArgs: [{ fontPaths }] } : {}),
 })
 const pdf = compiler.pdf({ mainFilePath: mainFile })
 writeFileSync(outFile, Buffer.from(pdf))