dsh-aimail 0.1.14 → 0.1.15

package/lib/mail-service.js

@@ -1,5 +1,5 @@
 import { resolveByRecipient, resolveByEmail, resolveBySessionId, } from '@aimail/mail';
-import { autoBind, emailForAgent, ensureSystem, hasAnySystem, listSystemDirs, readSystemConfig, releaseAllSystems, } from '@aimail/mail-core';
+import { autoBind, emailForAgent, ensureSystem, detectSystemForHome, hasAnySystem, listSystemDirs, readSystemConfig, releaseAllSystems, } from '@aimail/mail-core';
 import * as os from 'node:os';
 import * as path from 'node:path';
 import { fileURLToPath } from 'node:url';
@@ -68,7 +68,7 @@ export function apply(ctx, config = {}) {
         // non-fatal: resources are a seed; explicit release can re-run later
     }
     // install readiness: a dsh-only machine ensures its system through the CLI
-    // reverse-call ABI (`aimail ensure-system`, L1 only — never platform wiring,
+    // reverse-call ABI (`aimail install --system-only`, L1 only — never platform wiring,
     // which is how the install↔plugin call loop stays acyclic). UNCONDITIONAL
     // reverse-call (ownership short-circuit lives inside ensureSystem): a
     // multi-platform machine with only ANOTHER platform's systems must still
@@ -79,20 +79,33 @@ export function apply(ctx, config = {}) {
         const platformHome = process.env.AIMAIL_SYSTEM_HOME?.trim() ||
             process.env.DSH_HOME?.trim() ||
             path.join(os.homedir(), '.dsh');
-        void ensureSystem({ systemHome: platformHome })
+        // Bound-machine guard (2026-09-22): if this home already OWNS a system
+        // (platform pointer first, then the system_home scan — the same judgement
+        // the CLI makes), do not reverse-call at all. A stale activation code left
+        // in the environment then can no longer surface as a bogus startup error on
+        // a machine that is already bound ("no aimail system yet — Invalid
+        // activation code", the 2026-09-21 dsh report).
+        // Home-keyed, not "any system exists": another platform's systems do not
+        // claim this home, so a multi-platform machine still reaches the CLI
+        // (AUDIT-1 P1-7 must stay fixed).
+        void detectSystemForHome(platformHome)
+            .then((bound) => (bound ? null : ensureSystem({ systemHome: platformHome })))
             .then((r) => {
+            if (!r)
+                return;
             if (r.ok) {
                 if (r.activated) {
                     console.log(`[dsh-aimail] system activated: ${r.systemId}`);
                 }
+                return;
             }
-            else {
-                const hint = r.hint ? ` (${r.hint})` : '';
-                console.warn(`[dsh-aimail] no aimail system yet — ${r.error ?? 'unknown'}` + hint);
-            }
+            // Readable + actionable: say what is missing, then how to fix it.
+            const hint = r.hint ? `\n  hint: ${r.hint}` : '';
+            console.warn(`[dsh-aimail] no AIMail system is bound to this dsh home yet: ${r.error ?? 'unknown'}${hint}` +
+                `\n  to activate: aimail install --home ${platformHome} -c <activation-code> -m <manager@address>`);
         })
             .catch((e) => {
-            console.warn(`[dsh-aimail] system ensure failed: ${e instanceof Error ? e.message : String(e)}`);
+            console.warn(`[dsh-aimail] AIMail system check failed: ${e instanceof Error ? e.message : String(e)}`);
         });
     }
     catch {

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.14",
+  "version": "0.1.15",
   "publishConfig": {
     "access": "public",
     "provenance": true
@@ -51,8 +51,8 @@
     "@deepseek-ai/dsh-tools": "^0.0.1-rc.1"
   },
   "dependencies": {
-    "@aimail/mail-core": "^0.1.14",
-    "@aimail/mail": "^0.1.14"
+    "@aimail/mail-core": "^0.1.15",
+    "@aimail/mail": "^0.1.15"
   },
   "devDependencies": {
     "@deepseek-ai/cordis": "^4.0.1",

package/resources/skills/SKILL.md

@@ -35,6 +35,21 @@ Each inbound email arrives as a JSON message. Key fields:
 | `thread_summary` | Snapshot of active topics, decisions, and pending actions from previous exchanges. Pre-loaded from the last `set_email_summary` call. |
 | `attachments` | Local file paths. DOCX/XLSX/HTML/PDF have extracted `.md` versions alongside. Use `read_file` to inspect. |
 
+### System Mail (welcome & command confirmations)
+
+Two system emails (`noreply@<your-domain>`) carry operational meaning beyond the conversation:
+
+- **Welcome** — subject `Welcome to AIMail World, <you>, since <date>!`, sent when your address becomes active. **Reply-all** with exactly these three labelled lines so your manager can review and apply your outbound identity:
+
+  ```
+  persona: <one to three sentences introducing who you are and what you do>
+  signature: <your outbound email signature>
+  current_time: <the current time when you reply, human-readable, e.g. 2026-09-23 10:30 UTC>
+  ```
+
+  Once your manager applies it, the result is your `my_profile` (your manager is the only party who can change it).
+- **Command confirmations** — subject `[AIMail] Command applied: …` or `[AIMail] Command failed: …`. These acknowledge a command email a manager sent about you (approve persona / add contact / remove contact). No reply, no action.
+
 ---
 
 ## Processing Flow