@dbx-tools/appkit-email-shared 0.1.67 → 0.1.69

package/package.json

@@ -1,12 +1,11 @@
 {
   "name": "@dbx-tools/appkit-email-shared",
-  "version": "0.1.67",
+  "version": "0.1.69",
   "dependencies": {
     "zod": "^4.3.6"
   },
   "exports": {
     ".": {
-      "source": "./src/index.ts",
       "types": "./dist/index.d.ts",
       "default": "./dist/index.js"
     }
@@ -15,8 +14,7 @@
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "files": [
-    "dist",
-    "src"
+    "dist"
   ],
   "license": "Apache-2.0"
 }

package/src/index.ts

@@ -1,8 +0,0 @@
-/**
- * Wire-format contract for `@dbx-tools/appkit-email`: the email a model
- * drafts and the result of dispatching it (zod schemas + inferred
- * types). Pure and browser-safe - no `node:*` imports - so the
- * server-side sender, the Mastra tool, and the React approval UI all
- * validate and type against one definition.
- */
-export * from "./protocol.js";

package/src/protocol.ts

@@ -1,53 +0,0 @@
-// Wire-format contract for `@dbx-tools/appkit-email`: the email a model
-// drafts and the result of dispatching it. Pure (zod + inferred types,
-// no Node-only imports) so the server-side sender, the Mastra tool, and
-// the React approval UI all validate / type against one definition.
-//
-// Array fields intentionally avoid `.min()` / `.nonempty()`: those emit
-// `minItems` in the JSON schema, which some Model Serving endpoints
-// reject ("array types do not support minItems") when the schema is
-// forwarded as a tool definition.
-
-import { z } from "zod";
-
-/** Schema for the email a model asks to send (the tool input). */
-export const emailMessageSchema = z.object({
-  to: z
-    .string()
-    .describe(
-      'Single recipient email address (e.g. "alice@example.com"). Comma-separate multiple recipients yourself.',
-    ),
-  subject: z.string().describe("Subject line. Keep it short and specific."),
-  body: z
-    .string()
-    .describe(
-      [
-        "Email body in GitHub-Flavored Markdown; it is rendered to HTML before sending.",
-        "Use real Markdown structure: '#'/'##' headings, '-' or '1.' lists, **bold**/_italic_, '>' blockquotes, and fenced ``` code blocks.",
-        "For tabular data, emit a real Markdown table: a header row, then a '| --- | --- |' separator row, then one '| ... |' row per record.",
-        "Do NOT format with ASCII art: no '=====' or '-----' divider lines, and never hand-draw tables or bar charts with spaces, pipes, or '#'. Use the Markdown constructs above instead.",
-        "Be self-contained: the recipient has none of the chat context.",
-      ].join(" "),
-    ),
-  cc: z.array(z.string()).optional().describe("Optional CC recipient addresses."),
-  bcc: z.array(z.string()).optional().describe("Optional BCC recipient addresses."),
-});
-
-/** A validated outbound email message. */
-export type EmailMessage = z.infer<typeof emailMessageSchema>;
-
-/** Schema for the dispatch result returned to the model after a send. */
-export const emailResultSchema = z.object({
-  sent: z.boolean().describe("True once the message was handed to the SMTP server."),
-  recipient: z.string().describe("Echo of the `to` field for confirmation."),
-  from: z
-    .string()
-    .describe("The resolved sender address the message was actually sent from."),
-  messageId: z
-    .string()
-    .optional()
-    .describe("SMTP message id assigned by the server, when one was returned."),
-});
-
-/** The outcome of dispatching an {@link EmailMessage}. */
-export type EmailResult = z.infer<typeof emailResultSchema>;