@intx/tools-mail 0.2.2 → 0.3.0

package/README.md

@@ -14,7 +14,11 @@ its definitions alongside other bundles.
 import { createMailTools } from "@intx/tools-mail";
 import { defineMailTools } from "@intx/harness";
 
-const mailFactory = defineMailTools(() => createMailTools({ capabilities }));
+const mailTools = createMailTools({ capabilities });
+const mailFactory = defineMailTools(
+  () => mailTools,
+  mailTools.definitions.map((def) => ({ name: def.name })),
+);
 const def = defineAgent({ ..., tools: [mailFactory, posixFactory] });
 ```
 

package/dist/sidecar-bundle.d.ts

@@ -1,13 +1,12 @@
 import { type BaseEnv } from "@intx/agent";
-import type { MessageTransport } from "@intx/types/runtime";
+import type { RuntimeCapabilities } from "@intx/types/runtime-capabilities";
 /**
  * Env contract for the mail tool bundle. Extends `BaseEnv` with the
- * harness-level fields the mail tools depend on at handler-init time.
- * Compatible by structure with `@intx/harness`'s `MailEnv` so a host
- * that already provides that env can pass it straight through.
+ * host-assembled `capabilities` -- from which the mail tools resolve
+ * `mail.transport` -- and the agent `address`.
  */
 export interface MailToolEnv extends BaseEnv {
-    transport: MessageTransport;
+    capabilities: RuntimeCapabilities;
     address: string;
 }
 /**

package/dist/sidecar-bundle.js

@@ -1,13 +1,15 @@
 // Sidecar-bundle entry for `@intx/tools-mail` — the convention-compliant
 // factory the tool-package loader invokes.
 //
-// The factory declares the env keys it touches (`transport`, `address`)
-// via `defineTool`'s `requires`. The host populates those slots in the
-// per-instance env; the factory wraps the existing `createMailTools`
-// implementation.
+// The bundle consumes the host-assembled runtime capabilities rather than
+// building its own. The host (the sidecar's step-env builder) owns the
+// `RuntimeCapabilities` and puts it on `env.capabilities`; this factory
+// resolves `mail.transport` from it through `createMailTools` instead of
+// re-wrapping a raw transport it was handed separately. The env keys it
+// touches (`capabilities`, `address`) are declared in `requires`.
 import { defineTool } from "@intx/agent";
-import { createRuntimeCapabilities } from "@intx/types/runtime-capabilities";
 import { createMailTools } from "./index.js";
+import { TOOL_DEFINITIONS } from "./definitions.js";
 /**
  * Named export the loader picks up. The id is package-namespaced per
  * the convention; the model-facing tool names are synthesized by the
@@ -15,12 +17,10 @@ import { createMailTools } from "./index.js";
  */
 export const mail = defineTool({
     id: "@intx/tools-mail/sidecar-bundle",
-    requires: ["transport", "address"],
+    requires: ["capabilities", "address"],
+    definitions: TOOL_DEFINITIONS.map((def) => ({ name: def.name })),
     factory: (env) => {
-        const capabilities = createRuntimeCapabilities({
-            "mail.transport": env.transport,
-        });
-        const tools = createMailTools({ capabilities });
+        const tools = createMailTools({ capabilities: env.capabilities });
         return {
             definitions: tools.definitions,
             run: (call, signal) => tools.run(call, signal),

package/package.json

@@ -1,6 +1,7 @@
 {
   "name": "@intx/tools-mail",
-  "version": "0.2.2",
+  "description": "Mail tool runner giving agents mail_send, mail_reply, mail_search, mail_read, and mail_wait",
+  "version": "0.3.0",
   "license": "LGPL-2.1-only",
   "type": "module",
   "interchange": {
@@ -19,10 +20,13 @@
     }
   },
   "dependencies": {
-    "@intx/agent": "0.2.2",
-    "@intx/types": "0.2.2",
+    "@intx/agent": "0.3.0",
+    "@intx/types": "0.3.0",
     "arktype": "^2.1.29"
   },
+  "devDependencies": {
+    "@intx/storage-isogit": "0.3.0"
+  },
   "files": [
     "dist",
     "README.md",