dsh-aimail 0.1.12-rc.2 → 0.1.12

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/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 aimail_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.2",
+  "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.2",
-    "@aimail/mail": "^0.1.12-rc.2"
+    "@aimail/mail-core": "^0.1.12",
+    "@aimail/mail": "^0.1.12"
   },
   "devDependencies": {
     "@deepseek-ai/cordis": "^4.0.1",

package/resources/skills/SKILL.md

@@ -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", ...)`.