@flowdular/sdk 0.2.4 → 0.3.1

package/modules/automations/migrations/0006_automations_list_sort_indexes.up.sql

@@ -0,0 +1,11 @@
+-- The schedule and trigger lists page by keyset over the same order they show,
+-- lower(label) then id, or updated_at then id, so each order gets an index
+-- that starts with the tenant and ends with the id the keyset breaks ties on.
+CREATE INDEX IF NOT EXISTS automations_schedules_tenant_label_key_idx
+  ON automations_schedules (tenant_id, lower(label), id);
+CREATE INDEX IF NOT EXISTS automations_schedules_tenant_updated_idx
+  ON automations_schedules (tenant_id, updated_at, id);
+CREATE INDEX IF NOT EXISTS automations_triggers_tenant_label_key_idx
+  ON automations_triggers (tenant_id, lower(label), id);
+CREATE INDEX IF NOT EXISTS automations_triggers_tenant_updated_idx
+  ON automations_triggers (tenant_id, updated_at, id);

package/modules/automations/module.json

@@ -3,9 +3,9 @@
 	"schemaVersion": 1,
 	"id": "automations.core",
 	"package": "@flowdular/module-automations",
-	"version": "0.4.0",
+	"version": "0.6.7",
 	"profile": "full",
-	"capabilities": ["api", "database", "client", "translations"],
+	"capabilities": ["api", "database", "client", "translations", "cli"],
 	"platform": {
 		"server": true,
 		"client": true
@@ -13,19 +13,37 @@
 	"dependencies": [
 		{
 			"id": "system.core",
-			"range": "0.5.0"
+			"range": "^0.7.0"
 		},
 		{
 			"id": "auth.core",
-			"range": "0.10.0"
+			"range": "^0.13.0"
 		},
 		{
 			"id": "agents.core",
-			"range": "0.9.1"
+			"range": "^0.12.0"
+		},
+		{
+			"id": "workflows.core",
+			"range": "^0.6.0"
+		}
+	],
+	"provides": ["automations.targets.v1", "automations.execution.v1"],
+	"requires": [
+		{
+			"id": "agents.run-queue"
+		},
+		{
+			"id": "workflows.execution.v1",
+			"optional": true
 		}
 	],
 	"tenancy": "required",
 	"locales": ["en", "pl"],
 	"stability": "experimental",
-	"platformApi": "0.1.0"
+	"cli": {
+		"catalog": "src/cli/commands.json",
+		"entry": "src/cli/index.ts"
+	},
+	"platformApi": "^0.1.0"
 }

package/modules/automations/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@flowdular/module-automations",
-	"version": "0.4.0",
+	"version": "0.6.7",
 	"type": "module",
 	"exports": {
 		".": "./src/index.ts",
@@ -14,12 +14,15 @@
 		"test": "vitest run"
 	},
 	"dependencies": {
+		"@flowdular/cli-protocol": "workspace:*",
 		"@flowdular/client": "workspace:*",
 		"@flowdular/contracts": "workspace:*",
 		"@flowdular/database": "workspace:*",
+		"@flowdular/harness": "workspace:*",
 		"@flowdular/kernel": "workspace:*",
 		"@flowdular/module-agents": "workspace:*",
 		"@flowdular/module-auth": "workspace:*",
+		"@flowdular/module-workflows": "workspace:*",
 		"@flowdular/server": "workspace:*",
 		"@flowdular/ui": "workspace:*",
 		"octane": "0.1.51",

package/modules/automations/spec/module.yaml

@@ -1,22 +1,25 @@
 schemaVersion: 1
 id: automations.core
-specVersion: 0.4.0
+specVersion: 0.6.7
 status: approved
 name: Automations Core
-description: Runs agents without a person present, on a schedule or from a signed webhook, as a module a workspace can leave uninstalled.
+description: Runs agents or published workflows without a person present, on a schedule or from a signed webhook, as a module a workspace can leave uninstalled.
 profile: full
 capabilities:
   - api
   - database
   - client
   - translations
+  - cli
 dependencies:
   - id: system.core
-    range: 0.5.0
+    range: ^0.7.0
   - id: auth.core
-    range: 0.10.0
+    range: ^0.13.0
   - id: agents.core
-    range: 0.9.1
+    range: ^0.12.0
+  - id: workflows.core
+    range: ^0.6.0
 tenancy: required
 locales:
   - en
@@ -25,14 +28,24 @@ invariants:
   - Automations never reads or writes another module's database; it reaches agents.core only through the agents.run-queue platform capability.
   - A workspace with automations.core disabled keeps every agent capability, including manual runs, usage accounting, and budget caps.
   - A schedule fires at most once per slot, and a slot missed while the platform was down is skipped, never replayed.
+  - A cadence is either every:N whole minutes from 1 to 10080, or a five field cron expression with no seconds, bounded in length, whose fields accept *, numbers, three letter month and weekday names, lists, ranges and steps. An expression the module cannot honour, including one no real date matches, is refused when it is saved with the stable code INVALID_CADENCE.
+  - A cron slot is a wall clock time in the workspace zone read from the shared system.core.timeZone setting, resolved to one UTC instant that is what the schedule stores. A wall time a daylight saving change removes is skipped, a wall time that occurs twice fires at the first of the two, and an interval cadence carries no zone and never reads one.
+  - Changing the workspace time zone moves that workspace's pending cron slots into the new zone at once, each write conditional on the slot that was read, so a slot already due keeps the fire it owes and a concurrent fire wins.
   - A webhook request is accepted only with a fresh, valid signature; every refusal returns one identical response and the reason goes to the audit trail alone.
   - The trigger secret is stored encrypted with the key held outside the database, and is returned in full only at creation and rotation.
   - A schedule or trigger whose agent no longer exists disables itself and records why, because a cross-module reference cannot be a foreign key.
   - Automation events are appended to a hash-chained audit trail that verifies independently of the agents trail.
-  - The scheduler poll interval is an automations.core platform setting with a bounded deployment default, so installing the module does not add an undeclared clock policy to agents.core.
+  - The scheduler is the platform job runner on the automations.core poll interval setting, a platform setting with a bounded deployment default so installing the module does not add an undeclared clock policy to agents.core, claiming a bounded page of routing columns read on the background role, one schedule fired per claim, and one schedule that cannot be read or fired costing no other schedule in the pass.
   - A schedule stores its raw input template; only the queued run snapshot receives a single-pass resolved value from scope-filtered variable sources.
   - Every request-time read and write runs on a tenant-scoped PostgreSQL handle under forced row-level security. The scheduler poll and the webhook trigger lookup are the only cross-tenant reads, they run on a separate read-only role, and that role is granted only the columns that route the work to a tenant under a policy of the table itself.
   - A due schedule found by the cross-tenant poll, and a trigger found by the cross-tenant webhook lookup, are read again under the tenant that row named before anything acts on them, and a slot whose next run time moved in between is skipped.
+  - Automations reaches workflows.core only through the public workflows.execution.v1 capability. It owns no workflow worker, execution history, revision snapshot, or workflow permission, and while that capability is absent the workflow target is unavailable, existing workflow target configuration is retained, and automatic firing is skipped with safe audit evidence.
+  - A schedule or webhook can select a workflow only when the configuring user can read published workflows, execute workflow runs, and holds every permission the selected published workflow requires. The permission snapshot is captured from trusted authorization context and cannot be supplied or widened by a schedule template, webhook body, or adapter input.
+  - An automatic workflow invocation runs as the automations.core service actor with the configuring user in configuredBy and the schedule or trigger as a separate origin. Run now keeps the requesting user as the workflow actor with module origin automations.core and operation schedules.run-now.
+  - A workflow invocation uses a stable tenant-scoped idempotency key derived from the persisted schedule slot, the accepted webhook signature digest, or the Run now request id, so a repeated delivery resolves to the original run and a key reused for different input is refused by workflows.core without a retry under a new key.
+  - A missing, archived, unpublished, or newly unauthorized workflow never falls back to another workflow or agent and never substitutes a revision selected outside workflows.core; the schedule or trigger is made visibly unavailable until an authorized user updates it.
+  - The automations-workflows.schedule.run agent tool lets a workflow run node fire an automation schedule whose target is an agent only, under a node-derived idempotency key, so neither a workflow nor an agent can re-enter itself through an automation. The caller kind is the invocation the harness states, a kind it does not state counting as an agent run, so every agent run is refused and a workflow action runs whatever its run actor is; the actor is identity only and must hold automations.schedules.manage.
+  - automations.core declares one data class to the platform registry, automations.core.audit-events, holding the audit trail. It is exportable, and its export walks one workspace by keyset in bounded pages under this module's own tenant-scoped transaction. It carries no retention period and no sweep, because the trail is hash chained from its first event and removing the oldest links by age would make the chain unverifiable; schedules and webhook triggers are configuration a person manages, so they are not declared as a class that ages.
 permissions:
   - id: automations.schedules.read
     description: Read schedules in the active tenant.
@@ -46,7 +59,12 @@ dataOwnership:
   - automations.core owns schedule definitions, webhook trigger definitions, their encrypted secrets, and its own audit trail.
   - agents.core keeps runs, run history, token usage, cost accounting, and budget caps, so cost protection survives with automations uninstalled.
   - Automations stores an agent identifier and never copies agent definitions, skills, or provider credentials.
+  - For a workflow target automations.core stores the published workflow key, the configuring user, the trusted permission snapshot, and the run correlation; workflows.core keeps the selected revision, execution payload, evidence, usage, cost, status, cancellation, and run history.
 acceptanceScenarios:
+  - id: AUTO-DATA-CLASS-EXPORT
+    given: Two workspaces hold automation audit events and the platform has sealed the data class registry.
+    when: The workspace export runs the automations.core.audit-events operation for one of them.
+    then: Every event of that workspace is written to the sink by a bounded keyset walk with the oldest and newest event time in the summary, the other workspace contributes nothing, a workspace without events answers no rows and no range, and the class declares no sweep so the hash chain keeps its first link.
   - id: AUTO-SCHEDULE-FIRES
     given: An enabled schedule on an existing agent is due.
     when: The worker ticks twice inside the same slot.
@@ -55,6 +73,18 @@ acceptanceScenarios:
     given: An enabled schedule was due several intervals ago because the platform was stopped.
     when: The worker ticks after the platform starts.
     then: One run is enqueued and the skipped slots are not replayed.
+  - id: AUTO-CRON-NEXT-RUN
+    given: A schedule manager saves a cron cadence in a workspace whose time zone is set.
+    when: The next run is computed, and later the workspace changes its time zone.
+    then: The stored next run is the first matching wall clock minute in that zone expressed in UTC, the schedules screen shows it in that zone, and the workspace's pending cron slots move when the zone changes while every:N schedules keep theirs.
+  - id: AUTO-CRON-DST
+    given: A daily cron slot falls in the hour a daylight saving change removes, and on another date in the hour it repeats.
+    when: The next run is computed across both transitions.
+    then: The removed slot is skipped for that day rather than moved, the repeated slot fires once at the first of its two readings, a computation from inside the repeated hour never answers a time already past, and the local hour is unchanged on every other day.
+  - id: AUTO-CRON-INVALID
+    given: A cadence is neither every:N in range nor a cron expression this module can honour.
+    when: A schedule manager saves it.
+    then: The server refuses with INVALID_CADENCE before anything is stored, and a stored cadence that stops being honourable disables its schedule with the reason instead of firing a slot it cannot advance past.
   - id: AUTO-WEBHOOK-ACCEPT
     given: A caller signs the body with the trigger secret and a fresh timestamp.
     when: The request reaches the public fire endpoint.
@@ -86,8 +116,52 @@ acceptanceScenarios:
   - id: AUTO-SCHEDULE-VARIABLES
     given: A schedule manager can read the variables offered by the schedule editor, including agent.name through the agents.run-queue public capability.
     when: The manager saves a template containing known variables and the schedule queues a run.
-    then: Unknown or forbidden variables are rejected, the stored schedule keeps the raw template, and the run receives one-pass resolved input from the active tenant only.
+    then: Unknown or forbidden variables are rejected, the stored schedule keeps the raw template, and the run receives one-pass resolved input from the active tenant only. The editor reads its variables, agents, targets and the workspace zone from one automations.options read apart from the schedule list, and the schedules screen reads that list in pages of at most 200 rows sorted by label or updatedAt with the enabled filter and label search applied on the server, through an opaque cursor bound to the tenant, the sort and the filters.
   - id: AUTO-POLL-NARROW
     given: Two workspaces each own an enabled schedule that is due.
     when: The scheduler polls for due work across tenants.
     then: The poll returns only the workspace id, schedule id and next run time; the label, input template, configuring actor and permission snapshot are unreadable on that connection, and it cannot write.
+  - id: AUTO-WORKFLOW-REGISTER
+    given: automations.core and workflows.core are composed.
+    when: Platform composition completes before module start hooks run.
+    then: Exactly one workflow target adapter is available to automations.core, a duplicate registration stops boot, and no second scheduler, webhook ingress, or workflow worker starts.
+  - id: AUTO-WORKFLOW-OPTIONAL
+    given: workflows.core is unavailable.
+    when: A user opens automations or an automatic trigger becomes due.
+    then: Agent targets continue to work, workflow targets are hidden or marked unavailable, existing workflow target configuration is retained, no workflow run is created, and automations records a safe unavailable outcome without reading workflow storage.
+  - id: AUTO-WORKFLOW-CONFIGURE
+    given: A user can manage the schedule or trigger, read workflow definitions, execute workflow runs, and holds every permission required by a published workflow.
+    when: The user selects that workflow as the automation target.
+    then: automations.core stores the workflow key, configuring user, trusted permission snapshot, and target input configuration without copying a workflow revision, graph, secret, or execution record. The schedule and trigger forms take their target choices from the same automations.options read, and the triggers screen reads its list in pages of at most 200 rows sorted by label or updatedAt with the enabled filter and label search applied on the server, through an opaque cursor bound to the tenant, the sort and the filters.
+  - id: AUTO-WORKFLOW-CONFIGURE-DENY
+    given: A user lacks automation management, workflow read, workflow execution, or one permission required by the selected workflow.
+    when: The user attempts to create or update a workflow schedule or trigger.
+    then: automations.core refuses before persisting the target and grants no permission of its own.
+  - id: AUTO-WORKFLOW-SCHEDULE
+    given: An enabled workflow schedule is due for a persisted slot and its once-resolved input template produces bounded JSON.
+    when: The automations worker fires that slot more than once because of polling or recovery.
+    then: One workflow is enqueued by published key with a schedule origin, the automations.core service actor, the configuring user, the trusted permission snapshot, and the same slot-derived idempotency key, and automations stores the returned run correlation.
+  - id: AUTO-WORKFLOW-RUN-NOW
+    given: An authorized user selects Run now on a workflow schedule and still holds every permission required by its published workflow.
+    when: automations.core invokes the target with a bounded request identifier.
+    then: The workflow actor is the real requesting user, the origin is module automations.core with operation schedules.run-now, the permission snapshot is the caller's current trusted snapshot, and the idempotency key derives from the request.
+  - id: AUTO-WORKFLOW-WEBHOOK
+    given: An enabled workflow trigger receives a fresh valid signature and a bounded JSON body.
+    when: The same signed request is delivered more than once.
+    then: automations.core verifies ingress once per delivery, passes the parsed JSON unchanged with a webhook origin and a stable signature-digest key, workflows.core returns the same run, and neither module exposes the secret or raw signature.
+  - id: AUTO-WORKFLOW-TENANT
+    given: Two tenants use the same workflow key and equivalent schedule or trigger identifiers and payloads.
+    when: Their automations fire.
+    then: Each invocation uses only its trusted tenant context, idempotency is isolated per tenant, each run resolves that tenant's published workflow, and neither tenant can observe or affect the other's target or run.
+  - id: AUTO-WORKFLOW-UNAVAILABLE-TARGET
+    given: A configured workflow is archived, unpublished, missing, or no longer authorized by the stored permission snapshot.
+    when: Its schedule or webhook attempts to fire.
+    then: workflows.core refuses with its stable code, no fallback target or revision is selected, automations records a safe correlated failure, and the schedule or trigger is made visibly unavailable until an authorized user updates it.
+  - id: AUTO-WORKFLOW-IDEMPOTENCY-CONFLICT
+    given: An automation source reuses a persisted slot or accepted signature digest with a different workflow key or parsed input hash.
+    when: automations.core calls workflows.execution.v1 with the existing idempotency key.
+    then: workflows.core returns WORKFLOW_IDEMPOTENCY_CONFLICT, no second run is created, and automations records the refusal without retrying under a new key.
+  - id: AUTO-WORKFLOW-ACTION
+    given: A workflow run node calls the automations-workflows.schedule.run tool with a durable node idempotency key.
+    when: The call is reached as a workflow action or as an agent run, with an actor that may be a user, a service, or an agent, and with or without automations.schedules.manage and the key.
+    then: Only a workflow action call whose actor holds the permission fires the schedule, whatever kind that actor is, the schedule may dispatch an agent target only, a retried node attempt reuses the same automation key, and every agent run, actorless call, or caller without the permission or key is refused before automations executes.

package/modules/automations/src/api/endpoints.ts

@@ -1,8 +1,14 @@
+import { randomBytes } from 'node:crypto';
 import {
+	decodeCursor,
 	defineEndpoint,
+	encodeCursor,
+	HttpProblem,
 	jsonResponse,
+	pageResponse,
 	problemResponse,
 	readJsonObject,
+	readPageQuery,
 	requiredString,
 } from '@flowdular/sdk/server';
 import type { AuthRuntime } from '@flowdular/sdk/modules/auth/server';
@@ -17,6 +23,12 @@ import type { CreateAutomationScheduleInput } from '../domain/types.ts';
 import { scheduleVariablesForScopes } from '../domain/variables.ts';
 import type { AutomationsRuntime } from '../server/runtime.ts';
 import { AutomationsServiceError } from '../services/automations-service.ts';
+import {
+	AUTOMATION_LIST_SORT_KEYS,
+	type AutomationListCursor,
+	type AutomationListQuery,
+	type AutomationListSortKey,
+} from '../services/repository.ts';
 import {
 	MAX_TRIGGER_BODY_BYTES,
 	TRIGGER_SIGNATURE_HEADER,
@@ -68,7 +80,7 @@ function scheduleInput(
 			min: 1,
 			max: 10_000,
 		}),
-		cadence: requiredString(value, 'cadence', { min: 7, max: 32 }),
+		cadence: requiredString(value, 'cadence', { min: 7, max: 200 }),
 		enabled: requiredBoolean(value, 'enabled'),
 	};
 }
@@ -98,6 +110,114 @@ function optionalTargetInput(value: Record<string, unknown>) {
 	return Object.keys(target).length === 0 ? undefined : target;
 }
 
+const LIST_PAGE_LIMIT = 50;
+const MAX_LIST_PAGE_LIMIT = 200;
+const MAX_LIST_SEARCH_LENGTH = 120;
+
+function invalid(message: string): HttpProblem {
+	return new HttpProblem('INVALID_INPUT', message, 400);
+}
+
+function invalidCursor(): HttpProblem {
+	return new HttpProblem(
+		'CURSOR_INVALID',
+		'The page cursor is not valid.',
+		400,
+	);
+}
+
+interface ListRequest {
+	readonly query: AutomationListQuery;
+	/* Travels inside the cursor, so a cursor answers only the request that
+	   minted it: the same workspace, order and filters. */
+	readonly scope: Record<string, string>;
+}
+
+function listRequest(
+	url: URL,
+	tenantId: string,
+	cursorSecret: Uint8Array,
+): ListRequest {
+	const page = readPageQuery(url, {
+		maxLimit: MAX_LIST_PAGE_LIMIT,
+		defaultLimit: LIST_PAGE_LIMIT,
+	});
+	const sort = url.searchParams.get('sort') ?? 'label';
+	if (!AUTOMATION_LIST_SORT_KEYS.includes(sort as AutomationListSortKey)) {
+		throw invalid(
+			`sort must be one of ${AUTOMATION_LIST_SORT_KEYS.join(', ')}.`,
+		);
+	}
+	const direction = url.searchParams.get('direction') ?? 'asc';
+	if (direction !== 'asc' && direction !== 'desc') {
+		throw invalid('direction must be asc or desc.');
+	}
+	const enabledValue = url.searchParams.get('enabled') ?? '';
+	if (
+		enabledValue !== '' &&
+		enabledValue !== 'true' &&
+		enabledValue !== 'false'
+	) {
+		throw invalid('enabled must be true or false.');
+	}
+	const search = (url.searchParams.get('q') ?? '').trim();
+	if (search.length > MAX_LIST_SEARCH_LENGTH) {
+		throw invalid(`q is at most ${MAX_LIST_SEARCH_LENGTH} characters.`);
+	}
+	const scope = {
+		tenant: tenantId,
+		sort,
+		direction,
+		enabled: enabledValue,
+		q: search,
+	};
+	let after: AutomationListCursor | null = null;
+	if (page.cursor) {
+		const cursor = decodeCursor(page.cursor, cursorSecret);
+		for (const [key, value] of Object.entries(scope)) {
+			if (cursor[key] !== value) throw invalidCursor();
+		}
+		if (
+			typeof cursor.id !== 'string' ||
+			typeof cursor.value !== (sort === 'label' ? 'string' : 'number')
+		) {
+			throw invalidCursor();
+		}
+		after = { value: cursor.value!, id: cursor.id };
+	}
+	return {
+		query: {
+			sort: sort as AutomationListSortKey,
+			direction,
+			...(enabledValue === '' ? {} : { enabled: enabledValue === 'true' }),
+			...(search === '' ? {} : { search }),
+			limit: page.limit,
+			after,
+		},
+		scope,
+	};
+}
+
+function listResponse<Item>(
+	page: {
+		readonly items: readonly Item[];
+		readonly next: AutomationListCursor | null;
+	},
+	request: ListRequest,
+	cursorSecret: Uint8Array,
+): Response {
+	return pageResponse({
+		items: page.items,
+		limit: request.query.limit,
+		nextCursor: page.next
+			? encodeCursor(
+					{ ...request.scope, value: page.next.value, id: page.next.id },
+					cursorSecret,
+				)
+			: null,
+	});
+}
+
 function triggerRejection(): Response {
 	return jsonResponse(
 		{
@@ -114,25 +234,48 @@ export function createAutomationsRoutes(
 	auth: AuthRuntime,
 	runtime: AutomationsRuntime,
 ) {
-	const listSchedules = defineEndpoint({
-		id: 'automations.schedules.list',
-		path: '/api/automations/schedules',
+	/* Module-owned and never stored: a cursor names a position in one
+	   workspace's own list, so a restart invalidating one costs a client the
+	   first page. */
+	const cursorSecret = randomBytes(32);
+	const options = defineEndpoint({
+		id: 'automations.options',
+		path: '/api/automations/options',
 		methods: ['GET'],
 		access: { kind: 'permission', permission: AUTOMATIONS_PERMISSIONS.read },
 		resolveIdentity: endpointIdentityFromContext,
 		handler: async ({ octane }) => {
 			const principal = principalFromContext(octane)!;
+			const schedules = await runtime.scheduleService();
 			return jsonResponse({
-				schedules: await (
-					await runtime.scheduleService()
-				).list(principal.tenantId),
+				timeZone: schedules.timeZone(principal.tenantId),
 				variables: scheduleVariablesForScopes(principal.scopes),
-				agents: await (
-					await runtime.scheduleService()
-				).agents(principal.tenantId),
-				targets: await (
-					await runtime.scheduleService()
-				).targetOptions(
+				agents: await schedules.agents(principal.tenantId),
+				targets: await schedules.targetOptions(
+					principal.tenantId,
+					userActor(principal),
+					principal.scopes,
+				),
+			});
+		},
+	});
+	/* The trigger form's half of the options, so a principal holding only the
+	   trigger permissions still gets its targets. */
+	const triggerOptions = defineEndpoint({
+		id: 'automations.triggers.options',
+		path: '/api/automations/triggers/options',
+		methods: ['GET'],
+		access: {
+			kind: 'permission',
+			permission: AUTOMATIONS_PERMISSIONS.triggersRead,
+		},
+		resolveIdentity: endpointIdentityFromContext,
+		handler: async ({ octane }) => {
+			const principal = principalFromContext(octane)!;
+			const schedules = await runtime.scheduleService();
+			return jsonResponse({
+				agents: await schedules.agents(principal.tenantId),
+				targets: await schedules.targetOptions(
 					principal.tenantId,
 					userActor(principal),
 					principal.scopes,
@@ -140,6 +283,32 @@ export function createAutomationsRoutes(
 			});
 		},
 	});
+	const listSchedules = defineEndpoint({
+		id: 'automations.schedules.list',
+		path: '/api/automations/schedules',
+		methods: ['GET'],
+		access: { kind: 'permission', permission: AUTOMATIONS_PERMISSIONS.read },
+		resolveIdentity: endpointIdentityFromContext,
+		handler: async ({ octane }) => {
+			try {
+				const principal = principalFromContext(octane)!;
+				const request = listRequest(
+					new URL(octane.request.url),
+					principal.tenantId,
+					cursorSecret,
+				);
+				return listResponse(
+					await (
+						await runtime.scheduleService()
+					).list(principal.tenantId, request.query),
+					request,
+					cursorSecret,
+				);
+			} catch (error) {
+				return failure(error);
+			}
+		},
+	});
 	const createSchedule = defineEndpoint({
 		id: 'automations.schedules.create',
 		path: '/api/automations/schedules',
@@ -261,22 +430,23 @@ export function createAutomationsRoutes(
 		},
 		resolveIdentity: endpointIdentityFromContext,
 		handler: async ({ octane }) => {
-			const principal = principalFromContext(octane)!;
-			return jsonResponse({
-				triggers: await (
-					await runtime.triggerService()
-				).list(principal.tenantId),
-				agents: await (
-					await runtime.scheduleService()
-				).agents(principal.tenantId),
-				targets: await (
-					await runtime.scheduleService()
-				).targetOptions(
+			try {
+				const principal = principalFromContext(octane)!;
+				const request = listRequest(
+					new URL(octane.request.url),
 					principal.tenantId,
-					userActor(principal),
-					principal.scopes,
-				),
-			});
+					cursorSecret,
+				);
+				return listResponse(
+					await (
+						await runtime.triggerService()
+					).list(principal.tenantId, request.query),
+					request,
+					cursorSecret,
+				);
+			} catch (error) {
+				return failure(error);
+			}
 		},
 	});
 	const createTrigger = defineEndpoint({
@@ -449,11 +619,13 @@ export function createAutomationsRoutes(
 		},
 	});
 	return [
+		options.serverRoute,
 		listSchedules.serverRoute,
 		createSchedule.serverRoute,
 		updateSchedule.serverRoute,
 		deleteSchedule.serverRoute,
 		runSchedule.serverRoute,
+		triggerOptions.serverRoute,
 		listTriggers.serverRoute,
 		createTrigger.serverRoute,
 		updateTrigger.serverRoute,
@@ -465,11 +637,13 @@ export function createAutomationsRoutes(
 }
 
 export const endpoints = [
+	'automations.options',
 	'automations.schedules.list',
 	'automations.schedules.create',
 	'automations.schedules.update',
 	'automations.schedules.delete',
 	'automations.schedules.run',
+	'automations.triggers.options',
 	'automations.triggers.list',
 	'automations.triggers.create',
 	'automations.triggers.update',

package/modules/automations/src/cli/commands.json

@@ -0,0 +1,17 @@
+{
+	"protocolVersion": 1,
+	"moduleId": "automations.core",
+	"commands": [
+		{
+			"path": ["automations", "secrets-rotate"],
+			"capability": {
+				"id": "automations.secrets.rotate",
+				"version": 1,
+				"summary": "Re-seal stored trigger secrets with the current encryption key.",
+				"risk": "process",
+				"requiresApprovedSpec": false,
+				"supportsDryRun": true
+			}
+		}
+	]
+}