@voltro/plugin-webhooks 0.25.0 → 0.26.0

package/dist/mixin.d.ts

@@ -118,6 +118,30 @@ export declare const _voltroWebhookTargetsTable: Table<"_voltro_webhook_targets"
     readonly signing: ColumnBuilder<unknown, "json", boolean>;
     /** Serialised `RetryPolicy` — see `retry.ts`. */
     readonly retry: ColumnBuilder<unknown, "json", boolean>;
+    /**
+     * The APP's own scoping dimension. Opaque to the framework.
+     *
+     * Stored and returned verbatim, never interpreted — the framework does not
+     * know what a team, a project or a workspace is, and does not need to. Reads
+     * filter on equality against the json you wrote:
+     *
+     *   subscribe({ event, url, scope: { teamId: 'q970…' } })
+     *   listTargets({ scope: { teamId } })
+     *
+     * It exists because `.with(tenant())` is one level too coarse for real
+     * deployments. A consumer's endpoints are scoped to a TEAM and a tenant has
+     * many teams; every read filters by it and every write guards on it, so
+     * without this column the plugin cannot hold their rows at all and they keep
+     * a parallel table.
+     *
+     * The precedent is `_voltro_presence.meta`, and it is worth stating because
+     * it decided a migration: that column is json the framework stores and never
+     * interprets, and it is the ONLY reason the same consumer's presence
+     * migration was lossless — their three denormalised columns went straight in.
+     * The general form: a plugin that stores rows in an app's database on the
+     * app's behalf needs one place for the app's own dimension.
+     */
+    readonly scope: ColumnBuilder<unknown, "json", boolean>;
     /** Optional predicate filter (subset of `Predicate`) — the engine
      *  evaluates this against each emit's payload to decide whether
      *  this target receives the delivery. */
@@ -206,6 +230,30 @@ export declare const webhookTables: () => readonly [ Table<"_voltro_webhook_targ
     readonly signing: ColumnBuilder<unknown, "json", boolean>;
     /** Serialised `RetryPolicy` — see `retry.ts`. */
     readonly retry: ColumnBuilder<unknown, "json", boolean>;
+    /**
+     * The APP's own scoping dimension. Opaque to the framework.
+     *
+     * Stored and returned verbatim, never interpreted — the framework does not
+     * know what a team, a project or a workspace is, and does not need to. Reads
+     * filter on equality against the json you wrote:
+     *
+     *   subscribe({ event, url, scope: { teamId: 'q970…' } })
+     *   listTargets({ scope: { teamId } })
+     *
+     * It exists because `.with(tenant())` is one level too coarse for real
+     * deployments. A consumer's endpoints are scoped to a TEAM and a tenant has
+     * many teams; every read filters by it and every write guards on it, so
+     * without this column the plugin cannot hold their rows at all and they keep
+     * a parallel table.
+     *
+     * The precedent is `_voltro_presence.meta`, and it is worth stating because
+     * it decided a migration: that column is json the framework stores and never
+     * interprets, and it is the ONLY reason the same consumer's presence
+     * migration was lossless — their three denormalised columns went straight in.
+     * The general form: a plugin that stores rows in an app's database on the
+     * app's behalf needs one place for the app's own dimension.
+     */
+    readonly scope: ColumnBuilder<unknown, "json", boolean>;
     /** Optional predicate filter (subset of `Predicate`) — the engine
      *  evaluates this against each emit's payload to decide whether
      *  this target receives the delivery. */

package/dist/mixin.js

@@ -8,6 +8,7 @@ var u = o("_voltro_webhook_targets", {
 	secret: s(),
 	signing: r(),
 	retry: r(),
+	scope: r().nullable(),
 	filter: r().nullable(),
 	headers: r().nullable(),
 	rateLimitPerMinute: n().nullable(),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@voltro/plugin-webhooks",
-  "version": "0.25.0",
+  "version": "0.26.0",
   "description": "Webhooks plugin — first-class outgoing (multi-target, durable-workflow delivery, HMAC signing, retry policies, rate limits) + incoming (signature verification, idempotency, provider templates for Stripe / GitHub / Slack / generic).",
   "keywords": [
     "voltro",
@@ -48,12 +48,12 @@
   },
   "dependencies": {
     "@effect/workflow": "^0.19.0",
-    "@voltro/database": "0.25.0",
-    "@voltro/integration-http": "0.25.0",
-    "@voltro/logger": "0.25.0",
-    "@voltro/plugin-multitenancy": "0.25.0",
-    "@voltro/protocol": "0.25.0",
-    "@voltro/runtime": "0.25.0"
+    "@voltro/database": "0.26.0",
+    "@voltro/integration-http": "0.26.0",
+    "@voltro/logger": "0.26.0",
+    "@voltro/plugin-multitenancy": "0.26.0",
+    "@voltro/protocol": "0.26.0",
+    "@voltro/runtime": "0.26.0"
   },
   "peerDependencies": {
     "effect": "^3.22.0"