@lansenger-pm/openclaw-lansenger-channel 3.0.0 → 3.0.2

package/README.fr.md

@@ -372,7 +372,10 @@ Les mises à jour de statut d'approbation utilisent le format DynamicMsg appCard
 
 ## Journal des modifications
 
-- **v2.9.11** — Adaptateur de statut (probeAccount / buildChannelSummary / buildAccountSnapshot) ; `channels status --probe` affiche « configured » et « works » ; repli sur variables d'environnement pour les identifiants (LANSENGER_APP_ID / LANSENGER_APP_SECRET / LANSENGER_API_GATEWAY_URL)
+- **v3.0.0** — Ajout de `lansenger_send_format_text` (Markdown + @mention) ; réécriture SKILL.md (format arbre de décision, correction headStatusInfo description+colour — description supporte div-style pour couleur, couleur est la couleur du point) ; suppression du code de debug ; mise à jour manifest contracts
+- **v2.10.0** — Conversion automatique px→pt pour appCard ; classification erreurs sendImageUrl ; journalisation info pour inscription outils
+- **v2.9.12** — Suppression `defaultAccount` ; uiHints (labels chinois) ; nettoyage README (5 langues)
+- **v2.9.11** — Adaptateur de statut ; repli sur variables d'environnement ; `channels status --probe` affiche « configured » et « works »
 - **v2.8.1** — Correction README : flux d'installation 4 étapes ; SKILL.md frontmatter (spec AgentSkills) ; identifiant de canal en minuscules `lansenger`
 - **v2.8.0** — Routage multi-agent OpenClaw `bindings[]` ; groupPolicy/groupAllowFrom/groups contrôle d'accès groupe
 - **v2.7.0** — Enregistrement outils comme objets simples ; état runtime pour client/target

package/README.md

@@ -364,7 +364,10 @@ Approval status updates use the DynamicMsg appCard format. The `updateCardStatus
 
 ## Changelog
 
-- **v2.9.11** — Add status adapter (probeAccount / buildChannelSummary / buildAccountSnapshot); `channels status --probe` shows "configured" and "works"; env var fallback for credentials (LANSENGER_APP_ID / LANSENGER_APP_SECRET / LANSENGER_API_GATEWAY_URL)
+- **v3.0.0** — Add `lansenger_send_format_text` tool (Markdown + @mention); rewrite SKILL.md (decision tree format, fix headStatusInfo description+colour semantics — description supports div-style for color, colour is dot color); remove debug code; update manifest contracts
+- **v2.10.0** — font-size px→pt auto-conversion in appCard; sendImageUrl error classification; tool registration info-level logging
+- **v2.9.12** — Removed `defaultAccount`; uiHints (Chinese labels); README cleanup (5 locales)
+- **v2.9.11** — Add status adapter; env var fallback for credentials; `channels status --probe` shows "configured" and "works"
 - **v2.8.1** — Fix README: proper 4-step install flow; SKILL.md frontmatter (AgentSkills spec); channel identifier to lowercase `lansenger`
 - **v2.8.0** — OpenClaw `bindings[]` multi-agent routing; groupPolicy/groupAllowFrom/groups access control
 - **v2.7.0** — Plain-object tool registration; runtime state for client/target

package/README.zhHans.md

@@ -372,7 +372,10 @@ Agent 路由由 OpenClaw 的 `bindings[]` 配置管理——见[多 Agent 路由
 
 ## 更新日志
 
-- **v2.9.11** — 新增状态适配器（probeAccount / buildChannelSummary / buildAccountSnapshot）；`channels status --probe` 显示"configured"和"works"；环境变量回退支持凭证（LANSENGER_APP_ID / LANSENGER_APP_SECRET / LANSENGER_API_GATEWAY_URL）
+- **v3.0.0** — 新增 `lansenger_send_format_text` 工具（Markdown + @提及）；重写 SKILL.md（决策树格式，修正 headStatusInfo description+colour 语义——description 支持 div-style 标颜色，colour 是圆点颜色）；移除调试代码；更新 manifest contracts
+- **v2.10.0** — appCard font-size px→pt 自动转换；sendImageUrl 错误分类；工具注册 info 级别日志
+- **v2.9.12** — 移除 `defaultAccount`；uiHints（中文标签）；README 精简（5 语言）
+- **v2.9.11** — 新增状态适配器；环境变量回退支持凭证；`channels status --probe` 显示"configured"和"works"
 - **v2.8.1** — 修复 README：4 步安装流程；SKILL.md frontmatter（AgentSkills 规范）；频道标识符改为小写 `lansenger`
 - **v2.8.0** — OpenClaw `bindings[]` 多 Agent 路由；groupPolicy/groupAllowFrom/groups 群聊准入控制
 - **v2.7.0** — 纯对象工具注册；运行时状态获取 client/target

package/README.zhHant.md

@@ -372,7 +372,10 @@ Agent 路由由 OpenClaw 的 `bindings[]` 設定管理——見[多 Agent 路由
 
 ## 更新日誌
 
-- **v2.9.11** — 新增狀態適配器（probeAccount / buildChannelSummary / buildAccountSnapshot）；`channels status --probe` 顯示「configured」和「works」；環境變數回退支援憑證（LANSENGER_APP_ID / LANSENGER_APP_SECRET / LANSENGER_API_GATEWAY_URL）
+- **v3.0.0** — 新增 `lansenger_send_format_text` 工具（Markdown + @提及）；重寫 SKILL.md（決策樹格式，修正 headStatusInfo description+colour 語義——description 支援 div-style 標顏色，colour 是圓點顏色）；移除除錯代碼；更新 manifest contracts
+- **v2.10.0** — appCard font-size px→pt 自動轉換；sendImageUrl 錯誤分類；工具註冊 info 級別日誌
+- **v2.9.12** — 移除 `defaultAccount`；uiHints（中文標籤）；README 精簡（5 語言）
+- **v2.9.11** — 新增狀態適配器；環境變數回退支援憑證；`channels status --probe` 顯示「configured」和「works」
 - **v2.8.1** — 修復 README：4 步安裝流程；SKILL.md frontmatter（AgentSkills 規範）；頻道識別符改為小寫 `lansenger`
 - **v2.8.0** — OpenClaw `bindings[]` 多 Agent 路由；groupPolicy/groupAllowFrom/groups 羣聊准入控制
 - **v2.7.0** — 純物件工具註冊；運行時狀態取得 client/target

package/README.zhHantHK.md

@@ -374,7 +374,10 @@ Agent 路由由 OpenClaw 的 `bindings[]` 設定管理——見[多 Agent 路由
 
 ## 更新日誌
 
-- **v2.9.11** — 新增狀態適配器（probeAccount / buildChannelSummary / buildAccountSnapshot）；`channels status --probe` 顯示「configured」和「works」；環境變數回退支援憑證（LANSENGER_APP_ID / LANSENGER_APP_SECRET / LANSENGER_API_GATEWAY_URL）
+- **v3.0.0** — 新增 `lansenger_send_format_text` 工具（Markdown + @提及）；重寫 SKILL.md（決策樹格式，修正 headStatusInfo description+colour 語義——description 支援 div-style 標顏色，colour 是圓點顏色）；移除除錯代碼；更新 manifest contracts
+- **v2.10.0** — appCard font-size px→pt 自動轉換；sendImageUrl 錯誤分類；工具註冊 info 級別日誌
+- **v2.9.12** — 移除 `defaultAccount`；uiHints（中文標籤）；README 精簡（5 語言）
+- **v2.9.11** — 新增狀態適配器；環境變數回退支援憑證；`channels status --probe` 顯示「configured」和「works」
 - **v2.8.1** — 修復 README：4 步安裝流程；SKILL.md frontmatter（AgentSkills 規範）；頻道識別符改為小寫 `lansenger`
 - **v2.8.0** — OpenClaw `bindings[]` 多 Agent 路由；groupPolicy/groupAllowFrom/groups 羣聊准入控制
 - **v2.7.0** — 純物件工具註冊；運行時狀態取得 client/target

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lansenger-pm/openclaw-lansenger-channel",
-  "version": "3.0.0",
+  "version": "3.0.2",
   "type": "module",
   "main": "dist/index.js",
   "files": [

package/skills/lansenger-messaging/SKILL.md

@@ -1,227 +1,190 @@
 ---
 name: lansenger-messaging
-description: How to communicate on Lansenger (蓝信) — choose the right tool, when, send rich content, and pitfalls
+description: How to communicate on Lansenger (蓝信) — choose the right tool, when, and send rich content, and approvals, and pitfalls
 metadata: {"openclaw":{"requires":{"config":["channels.lansenger"]},"primaryEnv":"LANSENGER_APP_ID"}}
 ---
 
+```
+
 # Lansenger (蓝信) Messaging — Agent Quick Reference
 
-You are on Lansenger. This skill tells you **what tool to use, when, and how**.
+You`
 
-> ⚠️ This is reference documentation, NOT a CLI command. `openclaw skill lansenger-messaging` does not exist. Use the agent tools listed below directly.
+在 a Lansenger session, **just write your reply normally** — Markdown renders automatically as formatText. No tool needed for formatted text unless you also need @mentions.
 
----
+However, Markdown and file attachments are **mutually exclusive**. If you need both formatting AND a file, send the Markdown reply first, then call `lansenger_send_file` separately.
+Never put raw Markdown in lansenger_send_text — itansenger_send_format_text — it displays shows as ugly source code.
 
-## Quick Decision: What Tool Do I Use?
-```
-Need to send something? Follow this decision tree:
+> ⚠️ This is reference documentation, NOT a CLI command. `openclaw skill lansenger-messaging` does not exist. Use the agent tools directly.
 
-1. Normal reply with formatting (bold, lists, code, tables) → JUST WRITE IT. Markdown renders automatically. No tool needed.
-2. Need Markdown + @mention someone → lansenger_send_format_text (with reminder)
-3. Need plain text + @mention + file → lansenger_send_text (with reminder + filePath)
-4. Need just a FILE (any local file) → lansenger_send_file
-5. Need image from URL → lansenger_send_image_url
-6. Need a link card → lansenger_send_link_card
-7. Need multi-article card (图文) → lansenger_send_app_articles
-8. Need a rich formatted card → lansenger_send_app_card
-9. Need approval workflow → lansenger_send_app_card (isDynamic=true) → update via lansenger_update_dynamic_card
-10. Need to revoke a message → lansenger_revoke_message
-11. Need group IDs → lansenger_query_groups
-```
-> ⚠️ Group chat: appCard/linkCard/appArticles/formatText may be rejected by API. Fall back to lansenger_send_text.
-```
----
-
-## #1 Rule: Markdown Is Automatic
-In a Lansenger session, **just write your reply normally** — Markdown is automatically rendered as formatText. You never need to call a tool for formatted text unless you also need @mentions.
-
-However: Markdown and file attachments are **mutually exclusive**. If you need both formatting AND a file, send the Markdown reply first, then call `lansenger_send_file separately.
-Never put raw Markdown in lansenger_send_text — it displays as ugly source code.
+## Quick Decision: What Tool Do I Use?
 
----
+Need to send something? Follow this decision tree:
+1. Normal reply with formatting → JUST WRITE IT. No tool needed.
+2. Markdown + @mention → lansenger_send_format_text (with reminder)
+3. Plain text + @mention + file → lansenger_send_text (with reminder + filePath)
+4. Send a FILE → lansenger_send_file
+5. Send image from URL → lansenger_send_image_url
+6. Link card → lansenger_send_link_card
+7. Multi-article card (图文) → lansenger_send_app_articles
+8. Rich formatted card → lansenger_send_app_card
+9. Approval workflow → lansenger_send_app_card (isDynamic=true), → update via lansenger_update_dynamic_card
+10. Revoke a message → lansenger_revoke_message
+11. Find group IDs → lansenger_query_groups
+
+> ⚠️ **Group chat**: appCard/linkCard/appArticles/formatText may be rejected by API. Fall back to lansenger_send_text.
 
 ## Message Type Capability Matrix
-```
-┌──────────────┬──────────────┬──────────────┬──────────────┐
-│  Type        │  Markdown    │  @mention    │  Attachments │
-├──────────────┼──────────────┼──────────────┼──────────────┤
-│  formatText  │  ✓ (auto)    │  ✓ (reminder)│  ✗           │
-│  text        │  ✗           │  ✓           │  ✓           │
-└──────────────┴──────────────┴──────────────┴──────────────┘
-```
-- formatText: default outbound type. Markdown renders automatically. Also supports @mentions via `reminder` param (auto-fallback if API rejects). No file attachments.
-- text: plain text only. Supports @mentions + file attachments. No Markdown rendering.
+| Type       | Markdown | @mention | Attachments |
+|----------|----------|----------|------------|
+| formatText | ✓ (auto)  | ✓ (reminder) | ✗          |
+| text      | ✗          | ✓          | ✓          |
 
+- formatText: Markdown renders, supports @mention via reminder param (auto-fallback if API rejects). No file attachments.
+- text: Plain text only. Supports @mention + file attachment. No Markdown rendering.
 - These two types are **mutually exclusive** — pick one based on what you need.
-```
----
 
 ## Tool Reference
-All tools accept optional `to` (chatId). Leave empty to auto-detect current conversation. Only fill for different chat. chatId is case-sensitive.
-```
-How to get chatId: Inbound message senderId/conversationId. Never truncate or modify a chatId.
-
-```
----
-
+All tools accept optional `to` (chatId). Leave empty to auto-detect current conversation. Only fill for different chat. chatId is case-sensitive — never truncate or modify.
 ### lansenger_send_file
-| Param | Required | Description |
-|-------|----------|-------------|
-| filePath | ✅ | Absolute local path (workspace, /tmp, Desktop, etc.) |
-| caption | ❌ | Plain-text caption (no Markdown) |
-| to | ❌ | Target chatId (auto if omitted) |
-> Use this instead of MEDIA: tags for non-workspace files. MEDIA: silently fails outside workspace.
+| Param    | Type     | Required | Description |
+|---------|----------|----------|-------------|
+| filePath | string   ✅      | Absolute local path (workspace, /tmp, Desktop, etc.) |
+| caption | string   ❌      | Plain-text caption (no Markdown) |
+| to      | string   ❌      | Target chatId (auto if omitted) |
+
+> ⚠️ **MEDIA: tags currently broken** — they silently fail for ALL files, not just workspace ones Use lansenger_send_file for every file attachment.
 
 ### lansenger_send_text
-| Param | Required | Description |
-|-------|----------|-------------|
-| content | ✅ | Plain text only (NO Markdown) |
-| filePath | ❌ | Optional file to attach (content becomes caption) |
-| to | ❌ | Target chatId |
-| reminderAll | ❌ | @mention all members (group only) |
-| reminderUserIds | ❌ | @mention specific users (group only) |
+| Param    | Type     | Required | Description |
+|---------|----------|----------|-------------|
+| content | string   ✅      | Plain text only (NO Markdown) |
+| filePath | string   ❌      | Optional file to attach (content becomes caption) |
+| to      | string   ❌      | Target chatId |
+| reminderAll | boolean   ❌      | @mention all members (group only) |
+| reminderUserIds | string[] | ❌      | @mention specific users (group only) |
 
 ### lansenger_send_format_text
-| Param | Required | Description |
-|-------|----------|-------------|
-| content | ✅ | Markdown text |
-| to | ❌ | Target chatId |
-| reminderAll | ❌ | @mention all (group only) |
-| reminderUserIds | ❌ | @mention specific users (group only) |
+| Param    | Type     | Required | Description |
+|---------|----------|----------|-------------|
+| content | string   ✅      | Markdown text |
+| to      | string   ❌      | Target chatId |
+| reminderAll | boolean   ❌      | @mention all (group only) |
+| reminderUserIds | string[] | ❌      | @mention specific users (group only) |
 
 > Use when you need Markdown + @mention. No file attachments. Plugin auto-fallback if API rejects reminder.
 
-Always include "@姓名" in text when mentioning someone.
-
+> Always include "@姓名" in text when mentioning someone.
 ### lansenger_send_image_url
-| Param | Required | Description |
-|-------|----------|-------------|
-| imageUrl | ✅ | Directly reachable image URL |
-| caption | ❌ | Plain-text caption (no Markdown) |
-| to | ❌ | Target chatId |
-
-> URL must be reachable from gateway host. For local files use lansenger_send_file.
+| Param    | Type     | Required | Description |
+|---------|----------|----------|-------------|
+| imageUrl | string   ✅      | Directly reachable image URL |
+| caption | string   ❌      | Plain-text caption (no Markdown) |
+| to      | string   ❌      | Target chatId |
 
+> URL must be reachable from the gateway host. For local files, use lansenger_send_file.
 ### lansenger_send_link_card
-| Param | Required | Description |
-|-------|----------|-------------|
-| title | ✅ | Card title |
-| link | ✅ | Click-through URL |
-| description | ❌ | Card description (API-required, defaults empty) |
-| iconLink | ❌ | Icon URL (defaults empty) |
-| fromName | ❌ | Source name (defaults empty) |
-| fromIconLink | ❌ | Source icon URL (defaults empty) |
-| to | ❌ | Target chatId |
-
+| Param    | Type     | Required | Description |
+|---------|----------|----------|-------------|
+| title   | string   ✅      | Card title |
+| link    | string   ✅      | Click-through URL |
+| description | string   ❌      | Card description (API-required, defaults empty) |
+| iconLink  | string   ❌      | Icon URL (defaults empty) |
+| pcLink  | string   ❌      | PC client link |
+| fromName  | string   ❌      | Source name (defaults empty) |
+| fromIconLink | string   ❌      | Source icon URL (defaults empty) |
+| to      | string   ❌      | Target chatId |
 ### lansenger_send_app_articles
-| Param | Required | Description |
-|-------|----------|-------------|
-| articles | ✅ | Each: { imgUrl, title, url, summary? } |
-| to | ❌ | Target chatId |
+| Param    | Type     | Required | Description |
+|---------|----------|----------|-------------|
+| articles | object[] | ✅      | Each: { imgUrl, title, url, summary?, pcUrl? } |
+| to      | string   ❌      | Target chatId |
 
 > ⚠️ Article summary field is `summary`, NOT `description`. `description` is silently ignored.
-
 ### lansenger_send_app_card
-| Param | Required | Description |
-|-------|----------|-------------|
-| bodyTitle | ✅ | Card title (supports div-style) |
-| headTitle | ❌ | Header title |
-| bodyContent | ❌ | Content (supports div-style) |
-| isDynamic | ❌ | Enable approval workflow (default: false) |
-| headStatusInfo | ❌ | { description, colour } — description is status TEXT (supports div-style for color, e.g. `<div style="color:#FFB116">待审批</div>`, max 30 bytes), colour is the DOT/圆点 color (hex, e.g. #FFB116). These are TWO different things: text color vs dot color. |
-| fields | ❌ | Key-value pairs (max 10) |
-| links | ❌ | Links (max 3) |
-| to | ❌ | Target chatId |
+| Param    | Type     | Required | Description |
+|---------|----------|----------|-------------|
+| bodyTitle | string   ✅      | Card title (supports div-style) |
+| headTitle | string   ❌      | Header title |
+| bodySubTitle | string   ❌      | Subtitle (supports div-style) |
+| bodyContent | string   ❌      | Main content (supports div-style) |
+| signature | string   ❌      | Footer signature |
+| isDynamic | boolean   ❌      | Enable approval workflow (default: false) |
+| headStatusInfo | object   ❌      | { description, colour } — description: status TEXT (supports div-style for color, e.g. `<div style="color:#FFB116">待审批</div>`, max 30 bytes), colour: DOT/圆点 color (hex e.g. #FFB116). They are TWO different things: text color vs dot color. |
+| fields  | object[] | ❌      | Key-value pairs (max 10) |
+| links  | object[] | ❌      | Links (max 3): { title, url } |
+| cardLink | string   ❌      | Card click-through link |
+| staffId  | string   ❌      | Staff openId for sender avatar |
+| headIconUrl | string   ❌      | Header icon URL |
+| to      | string   ❌      | Target chatId |
 
 > ⚠️ **Group chat does NOT support appCard** — falls back to plain text. Approval workflows won't work in group chat.
 
-```
----
-
-div-style formatting rules:
+**div-style rules:**
 - `color`: hex (e.g. #333, #007BFF)
 - `font-size`: **MUST use pt** (12pt–36pt). px causes "invalid bodyContent" error.
 - `text-align`: left, center, right
 - `text-indent`: **MUST use 0em** — bare 0 causes silent failure
-```
 
 Example: `<div style="color:#333;font-size:14pt;text-indent:0em;text-align:left">Content here</div>`
-```
----
-
 ### lansenger_update_dynamic_card
-| Param | Required | Description |
-|-------|----------|-------------|
-| msgId | ✅ | Message ID from original send_app_card response |
-| headStatusInfo | ❌ | { description, colour } — description is text (supports div-style for color; `<div style="color:#198754">已批准</div>`), max 30 bytes. colour is the DOT/圆点 color (hex like #198754). These are TWO different things: text color vs dot color. |
-| isLastUpdate | ❌ | True = final state (default: false) |
-
-> headStatusInfo.description supports div-style for coloring the text. headStatusInfo.colour controls the status dot color. They are independent.
-
+| Param    | Type     | Required | Description |
+|---------|----------|----------|-------------|
+| msgId   | string   ✅      | Message ID from original send_app_card response |
+| headStatusInfo | object   ❌      | { description, colour } — description: status TEXT (supports div-style for color), colour: DOT/圆点 color (hex). Independent. |
+| links  | object[] | ❌      | Updated links (max 3) |
+| isLastUpdate | boolean   ❌      | True = final state, card becomes static (default: false) |
+
+> Set isLastUpdate=true on final approval decision. Intermediate updates steps: keep isLastUpdate=false.
 ### lansenger_revoke_message
-| Param | Required | Description |
-|-------|----------|-------------|
-| messageIds | ✅ | List of message IDs |
-| chatType | ❌ | bot (default) or group |
-| senderId | ❌ | Required if chatType=group |
-
+| Param    | Type     | Required | Description |
+|---------|----------|----------|-------------|
+| messageIds | string[] | ✅      | List of message IDs |
+| chatType | string   ❌      | bot (default) or group |
+| senderId | string   ❌      | Required if chatType=group |
 ### lansenger_query_groups
-| Param | Required | Description |
-|-------|----------|-------------|
-| pageOffset | ❌ | Page number (default: 1) |
-| pageSize | ❌ | Groups per page (default: 100) |
+| Param    | Type     | Required | Description |
+|---------|----------|----------|-------------|
+| pageOffset | integer  ❌      | Page number (default: 1) |
+| pageSize  | integer  ❌      | Groups per page (default: 100) |
 
 > ⚠️ May return errCode=10005 "API服务无权限" on enterprise deployments. Ask user for group IDs manually.
 
----
-
 ## Approval Workflow Pattern
-```
-1. Send: lansenger_send_app_card(bodyTitle="...", isDynamic=true, headStatusInfo={description: '<div style="color:#FFB116">待审批</div>', colour: "#FFB116"})
+1. Send: `lansenger_send_app_card(bodyTitle="...", isDynamic=true, headStatusInfo={description: '<div style="color:#FFB116">待审批</div>', colour: "#FFB116"})`
 2. User approves/denies → OpenClaw processes approval
-3. Update: lansenger_update_dynamic_card(msgId="<from step 1>", headStatusInfo={description: '<div style="color:#198754">已批准</div>', colour: "#198754"}, isLastUpdate=true)
-```
-Status colors: #FFB116 (pending), #198754 (approved) #dc3545 (denied)
+3. Update: `lansenger_update_dynamic_card(msgId="<from step 1>", headStatusInfo={description: '<div style="color:#198754">已批准</div>', colour: "#198754"}, isLastUpdate=true)`
 
-⚠️ **Approval only works in DM (1:1 chat)** — group chat de appCard falls back to plain text.
-
-```
----
+Status colors: #FFB116 (pending), #198754 (approved), #dc3545 (denied)
+> ⚠️ **Approval only works in DM (1:1 chat)** — group chat appCard falls back to plain text.
+> Set `isLastUpdate=true` on final decision. Keep `isLastUpdate=false` for intermediate updates step.
 
 ## @Mention Rules
-Both formatText and text support @mentions:
-- formatText: `reminderAll` + `reminderUserIds` params
-- text: `reminderAll` + `reminderUserIds` params
-
+Both formatText and text support @mentions via `reminderAll` + `reminderUserIds` params.
 Two rules:
-1. Always include "@姓名" in message text — reminder sends the push, "@姓名" makes it visible
-2. reminder is optional — use it in group chat when replying to someone so they notice your message
-
----
-
+1. Always include "@姓名" in message text — reminder sends the push notification, "@姓名" makes it visible in message
+2. reminder is optional — recommended in group chat when replying to someone
 ## Inbound Messages
-| Type | What you see |
+| Type    | What you see |
 |------|-------------|
 | text | Plain text |
 | formatText | Markdown text |
 | image | [Image] + local file paths |
-| video | [Video] + local file paths |
-| file | [File] + local file paths |
+| video | [Video] + local file path |
+| file | [File] + local file path |
 | voice | [Voice] + local file path |
 | position | [Location] name address lat,long |
 | card | [Contact Card] staffId |
-
----
-
+| sticker | [Sticker] stickerId |
 ## Common Pitfalls
 | Pitfall | Fix |
 |---------|-----|
 | Raw Markdown in text tool | Never do this — shows as ugly source code. Write normally for Markdown. |
-| MEDIA: tag for non-workspace file | Use lansenger_send_file. MEDIA: silently fails outside workspace. |
+| MEDIA: tag for file delivery | ⚠️ Currently broken for ALL files. Use lansenger_send_file for every file attachment. |
 | AppArticles `description` field | Use `summary`, not `description`. `description` is ignored. |
-| AppCard `font-size: 14px` | Use `font-size: 14pt`. px causes "invalid bodyContent". Range: 12pt–36pt. |
-| AppCard `text-indent: 0` | Use `text-indent: 0em`. Bare 0 causes silent failure. |
-| Dynamic card headStatusInfo div wrapping   │ description SUPPORTS div-style for color. colour is for the dot/圆点 only. They are separate. |
+| AppCard `font-size: px` | Use `pt` units (12pt–36pt). px causes API error. |
+| AppCard `text-indent: 0` | Use `0em` with unit. Bare 0 causes silent failure. |
+| headStatusInfo div wrapping | description supports div-style for color. colour is the DOT/圆点 color only. They are separate. |
 | Group chat appCard | Falls back to plain text. Approval workflows won't work. Use text + /approve. |
-| Message too long | ~4000 character limit. Split long content into multiple messages. |
+| Message too long | ~4000 character limit. Split into multiple messages. |
 | `openclaw skill` command | Does NOT exist. Use agent tools directly. |