feat(automation): schedule flow trigger — auto-launch flows on cron/interval/once

[xuyushun441-sys]

What

The time-based sibling of #1421 (record-change trigger). Completes the schedule arm of the automation engine's FlowTrigger extension point so a flow whose start node declares a schedule auto-launches on cron / interval / once — no manual engine.execute().

No engine change — the engine already parses a flow's start node into a schedule binding (flow.type === 'schedule' or a start-node config.schedule descriptor); that shipped with #1421. This PR is purely the concrete trigger plugin.

New plugin: @objectstack/plugin-trigger-schedule

• ScheduleTrigger implements the engine's FlowTrigger extension point and delegates timing to the platform IJobService (the 'job' service). It stays adapter-agnostic — the job service selects a cron-capable adapter (durable DbJobAdapter / CronJobAdapter) for cron schedules and the interval adapter for the rest.
• normalizeSchedule accepts the canonical JobSchedule plus ergonomic shorthands: a bare cron string, { cron } / { expression }, { every } / { intervalMs }, { at }.
• On fire, the flow runs with event: 'schedule' and params: { jobId, flowName, schedule }; the engine's start-condition gate still applies.
• Error-isolated — a scheduled flow failure is logged and swallowed, never crashing the job runner.
• Per-flow job name (flow-schedule:<flowName>) so stop() cancels exactly one flow; idempotent re-bind.
• Lazy job-service resolution per bind, so the job service's kernel:ready adapter upgrade (interval → durable Db) is always picked up.
• Graceful degrade when the automation or job service is absent (kernel:ready + getService, mirroring plugin-audit / the record-change trigger).
• Depends on com.objectstack.service.job so its adapter upgrade runs first.

Usage

kernel
  .use(new AutomationServicePlugin())  // engine + flows
  .use(new JobServicePlugin())         // the 'job' service (cron/interval/db)
  .use(new ScheduleTriggerPlugin());   // ← makes schedule flows live

Tests

17 tests: normalizeSchedule shapes / shorthands / rejects, schedule+cancel, config.schedule fallback, fire→context, error isolation, stop, idempotency, plugin wiring + graceful degrade + lazy resolution. Builds clean (full DTS typecheck). service-automation 104 (no regression — no engine change).

Follow-up

This completes the two trigger types the plan scoped (record-change + schedule). Strong-typing the start-trigger config in spec (engine reads it defensively today) remains an optional later cleanup.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
spec	Ready	Preview, Comment	May 31, 2026 11:18pm