@stackbone/cli 0.2.4 → 0.2.5

package/migrations/0022_trigger_subscriptions_mailbox.sql

@@ -0,0 +1,19 @@
+-- 0022_trigger_subscriptions_mailbox.sql — add mailbox column to trigger_subscriptions
+-- The mailbox identifies which mailbox a mailbox-scoped trigger polls. When resolving
+-- a declarative poll, the mailbox is injected into the arg the connector declares via
+-- `mailboxParam` (e.g. Outlook app-only's `user-id`). Nullable for backward compatibility
+-- with existing subscriptions.
+
+ALTER TABLE stackbone_platform.trigger_subscriptions
+ADD COLUMN mailbox text;
+
+-- Last-resort integrity guard against a direct DB insert that skips the register
+-- endpoint's validation. The SOURCE OF TRUTH for "this trigger needs a mailbox" is
+-- the connector definition's `mailboxParam` (enforced by the poll engine + register
+-- endpoint); SQL can't read that, so this constraint hardcodes today's only
+-- mailbox-scoped connector. Adding another one means updating this constraint too.
+ALTER TABLE stackbone_platform.trigger_subscriptions
+ADD CONSTRAINT chk_outlook_app_only_requires_mailbox
+CHECK (
+  (connector != 'outlook-app-only' OR mailbox IS NOT NULL)
+);

package/migrations/0023_runs_waiting_status.sql

@@ -0,0 +1,20 @@
+-- 0023_runs_waiting_status.sql — widen the runs status CHECK for serialized
+-- (FIFO) execution (STA-104).
+--
+-- A serialized workflow trigger enqueued behind an active serial run is mirrored
+-- into `stackbone_platform.runs` as a `waiting` row (started_at NULL — it has not
+-- run yet) so both `stackbone dev` and the Studio runs view can surface the queue
+-- read-only. When the FIFO gate admits the trigger and the next run starts, the
+-- waiting row is cleared. The original CHECK (0001 listed
+-- `running/done/failed/interrupted`) predates this value and would reject the
+-- insert. Widen `runs_status_check` to match `runStatusSchema`.
+--
+-- No trigger change is needed: the existing pg_notify fan-out (0001
+-- notify_run_event) already emits `run.created` on the waiting INSERT and
+-- `run.started` on the started_at NULL→NOT-NULL transition when the run starts,
+-- so open Studio views refresh through the existing SSE channel. Self-host and
+-- cloud both run these migrations, so the behavior is identical.
+ALTER TABLE stackbone_platform.runs DROP CONSTRAINT IF EXISTS runs_status_check;
+ALTER TABLE stackbone_platform.runs
+    ADD CONSTRAINT runs_status_check
+    CHECK (status IN ('running', 'done', 'failed', 'interrupted', 'waiting'));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stackbone/cli",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "license": "UNLICENSED",
   "type": "module",
   "bin": {