dsh-aimail 0.1.12-rc.1 → 0.1.12

package/README.md

@@ -3,7 +3,7 @@
 AIMail plugin for dsh (deepseek-harness). It gives a dsh agent a mailbox on
 AIMail: inbound email is delivered into the agent's session, and the agent
 can send mail, manage contacts, keep thread notes, and work on A2A boards
-through 13 plain tools.
+through 15 plain tools.
 
 ## Install
 
@@ -24,11 +24,11 @@ dsh plugin --profile web remove dsh-aimail
 
 ## What it does
 
-**Tools** — the same 13 bare-name tools as every other adapter:
+**Tools** — the same 15 bare-name tools as every other adapter:
 `send_mail`, `manage_contacts`, `contact_profile`, `set_contact_profile`,
 `email_summary`, `set_email_summary`, `search_mail`,
 `board_status`, `board_task_list`, `board_task_show`, `board_heartbeat`,
-`board_members`, `set_public_whoami`.
+`board_members`, `board_roles`, `set_public_whoami`, `activate_address_code`.
 Identity comes from the session id resolved through `@aimail/mail`
 (`agentmail.json` is the sole identity source); unbound sessions fail loud.
 
@@ -47,7 +47,7 @@ workflow (reply-all semantics, tool selection, thread continuity).
 
 The same tool surface and inbound contract, bound to other agent platforms:
 
-- [openclaw-aimail](https://www.npmjs.com/package/openclaw-aimail) — AIMail plugin for OpenClaw — definePluginEntry: 13 tools, in-gateway HTTP route, register/status commands.
+- [openclaw-aimail](https://www.npmjs.com/package/openclaw-aimail) — AIMail plugin for OpenClaw — definePluginEntry: 15 tools, in-gateway HTTP route, register/status commands.
 - [pi-aimail](https://www.npmjs.com/package/pi-aimail) — AIMail extension for pi (earendil-works/pi) — registerTool tools + local inbound listener bridged via sendUserMessage.
 
 ## Related repositories

package/cordis.patch.yml

@@ -33,6 +33,6 @@
       config:
         port: 9099
 
-    # AIMail tools (12 bare names, semantics from @aimail/mail-core)
+    # AIMail tools (15 bare names, semantics from @aimail/mail-core)
     - id: tool-mail
       name: 'dsh-aimail/tools'

package/lib/inbound.js

@@ -85,7 +85,7 @@ export function apply(ctx, config = {}) {
             }
             // Inbound routing (Q3 — mirror Python bridge routing): the per-delivery
             // target is authoritative. The bridge injects X-AIMail-Email (legacy
-            // X-Amail-Email fallback) on each single-delivery POST; payload.to is
+            // on each single-delivery POST; payload.to is
             // the FILTERED full list (external recipients first), so to[0] is often
             // an external address. Use the header when present; only iterate toRaw
             // when the header is absent (batch deliveries carry no such header).

package/lib/index.d.ts

@@ -3,7 +3,7 @@
  *
  * The bundle patch (cordis.patch.yml) self-mounts three subpath entries:
  *   dsh-aimail/mail-service  → ctx.mail (config resolution binding)
- *   dsh-aimail/tools         → 13 AIMail bare tools
+ *   dsh-aimail/tools         → 15 AIMail bare tools
  *   dsh-aimail/inbound       → node:http inbound endpoint + delivery
  *
  * Installed via: dsh plugin --profile web add dsh-aimail

package/lib/index.js

@@ -3,7 +3,7 @@
  *
  * The bundle patch (cordis.patch.yml) self-mounts three subpath entries:
  *   dsh-aimail/mail-service  → ctx.mail (config resolution binding)
- *   dsh-aimail/tools         → 13 AIMail bare tools
+ *   dsh-aimail/tools         → 15 AIMail bare tools
  *   dsh-aimail/inbound       → node:http inbound endpoint + delivery
  *
  * Installed via: dsh plugin --profile web add dsh-aimail

package/lib/register-cli.js

@@ -13,7 +13,7 @@
  *      local extra update) — mirrors bind_agent's every-run semantics.
  *
  * ABI: stdout = one JSON line {ok,email,system_id,exists?,registered?,
- * config_path?,api_key?,error?,hint?}; logs → stderr; exit 0 = ok.
+ * config_path?,error?,hint?}; logs → stderr; exit 0 = ok.
  *
  * Usage (from the CLI platform registry):
  *   node <dsh-aimail>/dist/register-cli.js [--system-id S] [--email E]

package/lib/tools.d.ts

@@ -1,9 +1,11 @@
 /**
- * dsh-aimail tools — registers the 13 AIMail bare tools for this profile.
+ * dsh-aimail tools — registers the 15 AIMail bare tools for this profile.
  *
  * Semantic text (names, descriptions, parameter descriptions) comes from
  * the shared MAIL_TOOLS registry in @aimail/mail-core (single source of
- * truth, parity-tested against amail_mcp_server.py). This adapter only:
+ * truth, parity-tested against the shared tool spec in
+ * pysdk/aimail_mcp_server.py). No MCP service is used by this TS adapter.
+ * This adapter only:
  *   - iterates MAIL_TOOLS, translating each entry to a dsh defineTool
  *   - binds execution: exec.agent.id (dsh session uuid) → ctx.mail.resolveCtx
  */

package/lib/tools.js

@@ -30,6 +30,9 @@ function toDshParam(p) {
     }
     if (p.description !== undefined)
         base.description = p.description;
+    // 审计 2026-09-21: default 也要透传到宿主 schema(与 mail-core 的 TypeBox 转换同口径)
+    if (p.default !== undefined)
+        base.default = p.default;
     if (p.required === true)
         base.required = true;
     return base;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dsh-aimail",
   "description": "AIMail plugin for dsh — install via: dsh plugin --profile web add dsh-aimail",
-  "version": "0.1.12-rc.1",
+  "version": "0.1.12",
   "publishConfig": {
     "access": "public",
     "provenance": true
@@ -51,8 +51,8 @@
     "@deepseek-ai/dsh-tools": "^0.0.1-rc.1"
   },
   "dependencies": {
-    "@aimail/mail-core": "^0.1.12-rc.1",
-    "@aimail/mail": "^0.1.12-rc.1"
+    "@aimail/mail-core": "^0.1.12",
+    "@aimail/mail": "^0.1.12"
   },
   "devDependencies": {
     "@deepseek-ai/cordis": "^4.0.1",

package/resources/board/role_prompt_en/common.md

@@ -18,7 +18,6 @@ Your AIMail address is **{{AGENTMAIL_ADDRESS}}**.
 - `board_roles(board_id, role?)` — view role permissions
 - `board_status(board_id)` — pipeline overview with dependencies
 - `board_heartbeat(task_id, note?)` — long-task heartbeat (first call Ready→Running, assignee only)
-- `board_continue_request(task_id, progress, note?)` — cross-session task continuation
 
 ## Key Instructions
 

package/resources/board/role_prompt_en/orchestrator.md

@@ -11,11 +11,9 @@ Your email: {{AGENTMAIL_ADDRESS}}
 - `[A2A] block <task-id>` / `[A2A] unblock <task-id>` — block/unblock task
 - `[A2A] cancel <task-id>` — cancel Blocked-only task (block first, then cancel)
 - `[A2A] reassign <task-id>` / `[A2A] edit <task-id>` / `[A2A] deadline <task-id>` — manage tasks
-- `[A2A] notify_all` — broadcast notification (phase report, urgent)
 - `[A2A] comment <task-id>` — add note
 - `[A2A] arbitrate` — request admin arbitration
 - `[A2A] list` / `[A2A] show` / `[A2A] members` / `[A2A] roles` / `[A2A] status` — queries
-- `[A2A] continue` — resume cross-session task (worker-initiated)
 
 ### Session Flow (to members, CC Board)
 

package/resources/board/role_prompt_en/worker.md

@@ -6,11 +6,10 @@ Your email: {{AGENTMAIL_ADDRESS}}
 ### Instruction Flow Commands (to Board)
 
 - `[A2A] complete <task-id>` — complete task with summary, Ready→Running on first call
-- `[A2A] continue <task-id>` — request continuation for cross-session long task
 - `[A2A] block <task-id>` — proactively block when stuck (your task, your right to report)
 - `[A2A] comment <task-id>` — add note
 - `[A2A] list` / `[A2A] show` / `[A2A] members` / `[A2A] roles` / `[A2A] status` — queries
-- Use `board_heartbeat(task_id)` for long-running tasks (first call transitions Ready→Running). Use `board_continue_request(task_id, progress, note)` to chain sessions.
+- Use `board_heartbeat(task_id)` for long-running tasks (first call transitions Ready→Running).
 
 ### Cannot Initiate
 

package/resources/board/role_prompt_zh/common.md

@@ -18,7 +18,6 @@
 - `board_roles(board_id, role?)` — 查看角色权限
 - `board_status(board_id)` — 管线总览（含依赖关系和负责人）
 - `board_heartbeat(task_id, note?)` — 长任务心跳（首次调用 Ready→Running，仅 assignee）
-- `board_continue_request(task_id, progress, note?)` — 跨 session 任务延续
 
 ## 关键指令
 

package/resources/board/role_prompt_zh/orchestrator.md

@@ -11,11 +11,9 @@
 - `[A2A] block <task-id>` / `[A2A] unblock <task-id>` — 阻塞/解除
 - `[A2A] cancel <task-id>` — 取消 task（仅 Blocked 状态可 cancel，先 block 再 cancel）
 - `[A2A] reassign <task-id>` / `[A2A] edit <task-id>` / `[A2A] deadline <task-id>` — 管理 task
-- `[A2A] notify_all` — 全员通知（阶段汇报、紧急通知）
 - `[A2A] comment <task-id>` — 添加备注
 - `[A2A] arbitrate` — 提请管理员仲裁
 - `[A2A] list` / `[A2A] show` / `[A2A] members` / `[A2A] roles` / `[A2A] status` — 查询
-- `[A2A] continue` — 长任务延续（Worker 发起）
 
 ### 可发起会话流（→ 成员，CC Board）
 

package/resources/board/role_prompt_zh/worker.md

@@ -6,11 +6,10 @@
 ### 可发起指令流指令（→ Board）
 
 - `[A2A] complete <task-id>` — 完成任务，带 summary，首次 heartbeat Ready→Running
-- `[A2A] continue <task-id>` — 长任务跨 session 延续
 - `[A2A] block <task-id>` — 遇到困难主动 block（你的任务，你有权报告阻塞）
 - `[A2A] comment <task-id>` — 添加备注
 - `[A2A] list` / `[A2A] show` / `[A2A] members` / `[A2A] roles` / `[A2A] status` — 查询
-- 长任务定期用 `board_heartbeat(task_id)` 发心跳（首次调用 Ready→Running）。跨 session 用 `board_continue_request(task_id, progress, note)` 串联。
+- 长任务定期用 `board_heartbeat(task_id)` 发心跳（首次调用 Ready→Running）。
 
 ### 不可发起
 

package/resources/skills/SKILL.md

@@ -29,7 +29,7 @@ Each inbound email arrives as a JSON message. Key fields:
 | `recipients` | `{to: [...], cc: [...]}` — everyone on the thread. Each is `Name <email>`. |
 | `recipients_profile` | Profiles for all recipients except you. |
 | `my_profile` | Your approved persona — who you are (single source of truth, set by your manager via `approve persona`). |
-| `my_amail_addr` | Your identity with persona in this conversation. |
+| `my_aimail_addr` | Your identity with persona in this conversation. |
 | `direct_message` | `true` = you're the only recipient. `false` = group conversation. |
 | `mentioned` | Someone wrote `@your-name` in the body (only meaningful when `direct_message: false`). |
 | `thread_summary` | Snapshot of active topics, decisions, and pending actions from previous exchanges. Pre-loaded from the last `set_email_summary` call. |
@@ -206,7 +206,7 @@ set_contact_profile(address="alice@example.com",
 
 ## Tools
 
-The 6 aimail tools are registered with full schemas — parameter names, types, and descriptions are visible to you automatically. This table is a quick reference:
+The aimail tools are registered with full schemas — parameter names, types, and descriptions are visible to you automatically. This table is a quick reference:
 
 | Tool | Use |
 |------|-----|
@@ -214,11 +214,15 @@ The 6 aimail tools are registered with full schemas — parameter names, types,
 | `contact_profile` | Look up a contact before deciding how to engage. |
 | `set_contact_profile` | Persist new observations about a contact. Only changed fields. |
 | `manage_contacts` | Check/add/remove/update contacts with direction control. `check` covers both "to" and "all" directions. `add` sends approval request to manager. `remove` needs no direction (one address = one record). `update` changes direction. |
+| `search_mail` | Search your own LOCAL mail history (offline). `query` keywords match subject/body/attachment text; `scope`=inbound/outbound/all; `since`/`until` (YYYY-MM-DD) and `from` narrow the window. Use to recall past conversations, find when something happened, or recover attachment content. Results newest-first with hit snippets. |
 | `email_summary` | Retrieve the stored thread summary (pre-loaded as `thread_summary`; call directly only if you need to re-read it mid-processing). |
 | `set_email_summary` | Save updated thread state after sending and replying. |
 
 ---
 
+### Recalling History
+When you need to remember what was said, when an event happened, or what an attachment contained, search your own mail archive first — `search_mail` is offline and instant. Empty `query` with `scope`+`since`/`until` browses a period. Your archive starts from when snapshots are enabled (default: on); mail you sent or received before that is not indexed.
+
 ## Rules
 
 1. **Contact gate**: all `to`/`cc` addresses must be in your contacts. Verify with `manage_contacts(action="check", ...)`.