@plitzi/sdk-server 0.35.3 → 0.35.4

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # @plitzi/sdk-server
 
+## 0.35.4
+
+### Patch Changes
+
+- v0.35.4
+- Updated dependencies
+  - @plitzi/plitzi-sdk@0.35.4
+  - @plitzi/sdk-shared@0.35.4
+
 ## 0.35.3
 
 ### Patch Changes

package/dist/actions.d.ts

@@ -55,7 +55,8 @@ export { createKvStore } from './modules/actions/runtime/kvStore';
  * and still wants refusals on the log stream wires one of each; that is the normal shape, not a workaround.
  */
 export { createRunLogger, createRejectLogger } from './modules/actions/runtime/runLogger';
-export type { ActionCredential, ActionDbDriver, ActionKvAdapter, ActionKvStore, ActionLookups, ActionRejectRecord, ActionRunRecord, ActionRunRequest, ActionRunResult, ActionsConfig, ActionTask, ActionTaskContext, ActionTaskRegistry, RegisteredTask, ResolvedConnector } from './modules/actions/types';
+export type { TaskRegistryOptions } from './modules/actions/tasks/registry';
+export type { ActionCredential, ActionDbDriver, ActionEmailAdapter, ActionEmailMessage, ActionKvAdapter, ActionKvStore, ActionLookups, ActionRejectRecord, ActionRunRecord, ActionRunRequest, ActionRunResult, ActionsConfig, ActionTask, ActionTaskContext, ActionTaskRegistry, RegisteredTask, ResolvedConnector } from './modules/actions/types';
 export type { ActionsModule } from './modules/actions';
 export type { ActiveRun, RunGuards } from './modules/actions/runtime/guards';
 export type { ScheduleResult, ScheduleRunner, ScheduleTick } from './modules/actions/runtime/schedule';

package/dist/modules/actions/index.d.ts

@@ -37,4 +37,5 @@ export { handleActionCancel } from './transport/cancelHandler';
 export type { ActiveRun, RunGuards } from './runtime/guards';
 export type { ScheduleResult, ScheduleRunner, ScheduleTick } from './runtime/schedule';
 export type { ActionTaskDescriptor } from './taskCatalog';
-export type { ActionCredential, ActionDbDriver, ActionKvStore, ActionLookups, ActionRejectRecord, ActionRunRecord, ActionRunRequest, ActionRunResult, ActionsConfig, ActionTask, ActionTaskContext, ActionTaskRegistry, RegisteredTask, ResolvedConnector } from './types';
+export type { TaskRegistryOptions } from './tasks/registry';
+export type { ActionCredential, ActionDbDriver, ActionEmailAdapter, ActionEmailMessage, ActionKvStore, ActionLookups, ActionRejectRecord, ActionRunRecord, ActionRunRequest, ActionRunResult, ActionsConfig, ActionTask, ActionTaskContext, ActionTaskRegistry, RegisteredTask, ResolvedConnector } from './types';

package/dist/modules/actions/index.js

@@ -25,7 +25,10 @@ import { handleActionCancel } from "./transport/cancelHandler.js";
 * the same as having no single-flight at all. Nothing outside this folder needs to know how a run is assembled.
 */
 var createActionsModule = (config) => {
-	const registry = createTaskRegistry(config.tasks, (config.dbDrivers?.length ?? 0) > 0);
+	const registry = createTaskRegistry(config.tasks, {
+		db: (config.dbDrivers?.length ?? 0) > 0,
+		email: config.email !== void 0
+	});
 	const { runAction } = createActionRunner(config, registry, config.fetchImpl);
 	/**
 	* Single-flight over the store the deployment already gave the `kv` tasks — its own Redis, table or whatever it

package/dist/modules/actions/moduleFor.js

@@ -26,6 +26,7 @@ var actionsModuleFor = (config) => {
 		rateLimit: config.action?.rateLimit,
 		idempotency: config.action?.idempotency,
 		dbDrivers: config.action?.dbDrivers,
+		email: config.action?.email,
 		onRun: config.action?.onRun
 	});
 	modules.set(config, module);

package/dist/modules/actions/runtime/runAction.js

@@ -260,6 +260,7 @@ var createActionRunner = (config, registry, baseFetch = fetch) => {
 			fetch: runFetch,
 			kv: scopedKv,
 			dbDrivers: config.dbDrivers ?? [],
+			email: config.email,
 			emit: (chunk) => request.emit?.(redact(chunk))
 		});
 		const trace = [];
@@ -280,7 +281,13 @@ var createActionRunner = (config, registry, baseFetch = fetch) => {
 			spaceId: request.spaceId,
 			environment: request.environment,
 			trigger: request.trigger,
-			runId
+			runId,
+			/**
+			* The moment the run started, as an ISO string — and the same moment for every step. A check that asks the
+			* time and the write it guards cannot straddle midnight, and a template reads it in the zone it cares about
+			* with `{{ now|date('Y-m-d', 'Europe/Madrid') }}`.
+			*/
+			now: new Date(startedAt).toISOString()
 		};
 		let status = "completed";
 		let returned;

package/dist/modules/actions/tasks/builtins.d.ts

@@ -2,7 +2,8 @@ import { ActionTask } from '../types';
 /**
  * The tasks `sdk-server` itself ships: the ones that are mechanism rather than policy.
  *
- * Anything needing an account somewhere — email, AI, object storage — is the DEPLOYMENT's, registered through
- * `actions.tasks`. A server with no mail transport must not offer a step whose only possible outcome is failure.
+ * Anything needing an account somewhere — AI, object storage — is the DEPLOYMENT's, registered through
+ * `actions.tasks`. `db.query` and `email.send` sit in between: the task is shipped because its rules are the same
+ * everywhere, the driver or transport is the deployment's, and the registry offers the task only when one was given.
  */
 export declare const builtinTasks: ActionTask<Record<string, unknown>>[];

package/dist/modules/actions/tasks/builtins.js

@@ -8,8 +8,9 @@ import { transformTasks } from "./transform.js";
 /**
 * The tasks `sdk-server` itself ships: the ones that are mechanism rather than policy.
 *
-* Anything needing an account somewhere — email, AI, object storage — is the DEPLOYMENT's, registered through
-* `actions.tasks`. A server with no mail transport must not offer a step whose only possible outcome is failure.
+* Anything needing an account somewhere — AI, object storage — is the DEPLOYMENT's, registered through
+* `actions.tasks`. `db.query` and `email.send` sit in between: the task is shipped because its rules are the same
+* everywhere, the driver or transport is the deployment's, and the registry offers the task only when one was given.
 */
 var builtinTasks = [
 	...flowTasks,

package/dist/modules/actions/tasks/email.d.ts

@@ -0,0 +1,2 @@
+import { ActionTask } from '../types';
+export declare const emailTasks: ActionTask<Record<string, unknown>>[];

package/dist/modules/actions/tasks/email.js

@@ -0,0 +1,62 @@
+//#region src/modules/actions/tasks/email.ts
+/**
+* One address, and nothing a mail header could be split on.
+*
+* Stricter than the standard on purpose: a comma or a semicolon is how one recipient becomes a hundred, and a line
+* break is how a subject becomes a second header. A flow renders what a visitor typed, so this is where that stops.
+*/
+var ADDRESS = /^[^\s@,;<>"]+@[^\s@,;<>"]+\.[^\s@,;<>"]+$/;
+var MAX_SUBJECT = 200;
+var MAX_TEXT = 2e4;
+var emailTasks = [{
+	namespace: "email",
+	action: "send",
+	title: "Send Email",
+	description: "Sends a plain-text message through the transport this deployment configured",
+	params: {
+		to: {
+			type: "text",
+			canBind: true,
+			defaultValue: "",
+			label: "To"
+		},
+		subject: {
+			type: "text",
+			canBind: true,
+			defaultValue: "",
+			label: "Subject"
+		},
+		text: {
+			type: "codemirror-text",
+			canBind: true,
+			defaultValue: "",
+			label: "Text"
+		},
+		replyTo: {
+			type: "text",
+			canBind: true,
+			defaultValue: "",
+			label: "Reply to"
+		}
+	},
+	run: async ({ to, subject, text, replyTo }, ctx) => {
+		if (!ctx.email) throw new Error("This server has no email transport");
+		const recipient = to.trim();
+		if (!ADDRESS.test(recipient)) throw new Error("The recipient is not one email address");
+		const answerTo = replyTo.trim();
+		if (answerTo !== "" && !ADDRESS.test(answerTo)) throw new Error("The reply-to is not one email address");
+		const title = subject.trim();
+		if (title === "" || /[\r\n]/.test(title) || title.length > MAX_SUBJECT) throw new Error(`The subject must be one line of 1 to ${MAX_SUBJECT} characters`);
+		if (text.trim() === "" || text.length > MAX_TEXT) throw new Error(`The text must have 1 to ${MAX_TEXT} characters`);
+		await ctx.email.send({
+			spaceId: ctx.spaceId,
+			to: recipient,
+			subject: title,
+			text,
+			...answerTo === "" ? {} : { replyTo: answerTo }
+		});
+		return { sent: true };
+	}
+}];
+//#endregion
+export { emailTasks };

package/dist/modules/actions/tasks/email.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/modules/actions/tasks/registry.d.ts

@@ -1,5 +1,12 @@
 import { ActionTask, ActionTaskRegistry } from '../types';
 export declare const taskName: (task: Pick<ActionTask, "namespace" | "action">) => string;
+/** The shipped tasks that are only real when the deployment supplied what they run through. */
+export type TaskRegistryOptions = {
+    /** At least one database driver is registered, so `db.query` has an engine to run against. */
+    db?: boolean;
+    /** An email transport is configured, so `email.send` has somewhere to hand a message. */
+    email?: boolean;
+};
 /**
  * Builds the set of tasks this server can run.
  *
@@ -7,4 +14,4 @@ export declare const taskName: (task: Pick<ActionTask, "namespace" | "action">)
  * name is unreachable from any document, and one shadowing a built-in silently changes what every existing action
  * in that deployment does. Both are invisible until a run misbehaves in production.
  */
-export declare const createTaskRegistry: (custom?: ActionTask<never>[], hasDbDrivers?: boolean) => ActionTaskRegistry;
+export declare const createTaskRegistry: (custom?: ActionTask<never>[], { db, email }?: TaskRegistryOptions) => ActionTaskRegistry;

package/dist/modules/actions/tasks/registry.js

@@ -1,9 +1,14 @@
 import { builtinTasks } from "./builtins.js";
 import { dbTasks } from "./db.js";
+import { emailTasks } from "./email.js";
 //#region src/modules/actions/tasks/registry.ts
 var NAME_PATTERN = /^[a-z][a-zA-Z0-9]*$/;
 var taskName = (task) => `${task.namespace}.${task.action}`;
-var reservedNamespaces = new Set([...builtinTasks, ...dbTasks].map((task) => task.namespace));
+var reservedNamespaces = new Set([
+	...builtinTasks,
+	...dbTasks,
+	...emailTasks
+].map((task) => task.namespace));
 /**
 * Builds the set of tasks this server can run.
 *
@@ -11,9 +16,13 @@ var reservedNamespaces = new Set([...builtinTasks, ...dbTasks].map((task) => tas
 * name is unreachable from any document, and one shadowing a built-in silently changes what every existing action
 * in that deployment does. Both are invisible until a run misbehaves in production.
 */
-var createTaskRegistry = (custom = [], hasDbDrivers = false) => {
+var createTaskRegistry = (custom = [], { db = false, email = false } = {}) => {
 	const tasks = /* @__PURE__ */ new Map();
-	(hasDbDrivers ? [...builtinTasks, ...dbTasks] : builtinTasks).forEach((task) => tasks.set(taskName(task), {
+	[
+		...builtinTasks,
+		...db ? dbTasks : [],
+		...email ? emailTasks : []
+	].forEach((task) => tasks.set(taskName(task), {
 		...task,
 		name: taskName(task)
 	}));

package/dist/modules/actions/types.d.ts

@@ -1,4 +1,4 @@
-import { ActionEntry, ActionLimits, ActionRejectRecord, ActionRunRecord, ActionRunStatus, ActionTriggerType, ConnectorManifest, Environment, InteractionCallbackParam, InteractionNode, InteractionNodeStatus, SpaceRevision, SSRUser } from '@plitzi/sdk-shared';
+import { ActionEmailAdapter, ActionEntry, ActionLimits, ActionRejectRecord, ActionRunRecord, ActionRunStatus, ActionTriggerType, ConnectorManifest, Environment, InteractionCallbackParam, InteractionNode, InteractionNodeStatus, SpaceRevision, SSRUser } from '@plitzi/sdk-shared';
 /** Resolved secret material, as the connector engine already models it. */
 export type ActionCredential = Record<string, string>;
 /**
@@ -109,6 +109,8 @@ export type ActionTaskContext = {
     kv: ActionKvStore;
     /** The database engines this deployment registered, for the `db.query` task. */
     dbDrivers: ActionDbDriver[];
+    /** The transport this deployment gave the `email.send` task. Absent → that task is not offered at all. */
+    email?: ActionEmailAdapter;
     /** Pushes a `data` frame to a streaming caller. A no-op when nobody negotiated a stream. */
     emit: (chunk: unknown) => void;
 };
@@ -162,6 +164,8 @@ export type ActionsConfig = {
     };
     /** Database engines this deployment lets a flow reach. Empty → the `db.query` task is not offered at all. */
     dbDrivers?: ActionDbDriver[];
+    /** How a flow's mail leaves this server. Absent → the `email.send` task is not offered at all. */
+    email?: ActionEmailAdapter;
     /**
      * Called once per run that started, for a deployment that keeps a record.
      *
@@ -197,7 +201,7 @@ export type ActionsConfig = {
 };
 /** Re-exported so the module's own files import one place, and a deployment writing an `onRun` or an `onReject`
  *  sees the same shapes the module emits. */
-export type { ActionRejectRecord, ActionRunRecord } from '@plitzi/sdk-shared';
+export type { ActionEmailAdapter, ActionEmailMessage, ActionRejectRecord, ActionRunRecord } from '@plitzi/sdk-shared';
 export type ResolvedActionLimits = Required<ActionLimits>;
 export type ActionRunRequest = {
     entry: ActionEntry;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plitzi/sdk-server",
-  "version": "0.35.3",
+  "version": "0.35.4",
   "license": "AGPL-3.0",
   "files": [
     "dist",
@@ -58,8 +58,8 @@
   "type": "module",
   "sideEffects": false,
   "dependencies": {
-    "@plitzi/plitzi-sdk": "0.35.3",
-    "@plitzi/sdk-shared": "0.35.3",
+    "@plitzi/plitzi-sdk": "0.35.4",
+    "@plitzi/sdk-shared": "0.35.4",
     "ejs": "^6.0.1",
     "esbuild": "^0.28.2",
     "jsonwebtoken": "^9.0.3"