@vxil/config 0.3.1 → 0.4.0

package/dist/index.d.ts

@@ -118,7 +118,14 @@ export type FunctionTrigger = {
 } | {
     kind: 'queue';
     source: string;
-} | {
+}
+/** `webhook`: the function is woken by a webhook_subscription fan-out whose
+ *  target_url is `<edge>/v1/internal/fn/trigger/<name>?tenant=<id>`. `source` is
+ *  an event-name PREFIX filter (e.g. 'payments.'), enforced at delivery — a
+ *  non-matching event is ACK-200 skipped. Declaring the binding is what opts the
+ *  function into event delivery; a receiver that declares only `cron` keeps the
+ *  older cron+{} wake. */
+ | {
     kind: 'webhook';
     source: string;
 } | {
@@ -142,10 +149,34 @@ export interface FunctionDef {
     secrets?: string[];
     /** Outbound host allowlist (deny-by-default egress guard). */
     egressAllow?: string[];
+    /** Per-function resource declarations. Both optional; both clamped server-side.
+     *  `memoryMb` was REMOVED (2026-09-18): memory is fixed by the managed runtime
+     *  and is not per-dispatch selectable. A config that still declares it pushes
+     *  fine — the key is stripped, and `vxil plan --explain` marks it DROPPED. */
     limits?: {
+        /** per-dispatch isolate CPU ceiling, ms (5..300000). Only ever TIGHTENS the
+         *  platform cap.
+         *
+         *  IT ALSO RAISES YOUR BILL on a metered tenant, and that is worth reading
+         *  twice: it raises (never lowers) the per-invoke credit reserve, whose floor
+         *  is the manifest default — and the reserve is the CEILING the pro-rated
+         *  settle clamps into, because the settle can never commit more than the hold
+         *  it releases from. So an invoke whose wall time exceeds `defaultLimits.cpuMs`
+         *  (50) settles at its MEASURED wall-ms instead of being capped at 50:
+         *  declaring `cpuMs: 1000` makes an 800 ms invoke cost 800 instead of 50.
+         *  Declaring only `timeoutMs` leaves metering byte-identical.
+         *
+         *  It does NOT affect anyone else's availability: the account-wide daily
+         *  capacity budget counts the platform's own per-invoke estimate, never this
+         *  value (workers/functions-v1/src/capacity.ts `capacityReserveCpuMs`). */
         cpuMs?: number;
+        /** wall budget for ONE outbound fetch this function makes, ms (1000..120000,
+         *  default 30000). Not a whole-invocation budget: three 25 s fetches still
+         *  take 75 s. The invocation is bounded separately by the platform's own
+         *  deadline (`FN_MAX_INVOKE_MS`, default ≥ 5 minutes), which raising this
+         *  value widens with you. The vxil API callback leg keeps the platform's
+         *  own 30 s bound. */
         timeoutMs?: number;
-        memoryMb?: number;
     };
     enabled?: boolean;
     /** optional typed contract surfaced by `vxil gen` (Level 1, §4.5). */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vxil/config",
-  "version": "0.3.1",
+  "version": "0.4.0",
   "description": "Typed vxil.config.ts authoring for the vxil backend platform — defineConfig, feature and cms field definitions (published for @vxil/cli).",
   "license": "MIT",
   "homepage": "https://vxil.com",
@@ -22,7 +22,7 @@
     "src"
   ],
   "dependencies": {
-    "@vxil/feature-configs": "0.3.1"
+    "@vxil/feature-configs": "0.4.0"
   },
   "publishConfig": {
     "access": "public"

package/src/index.ts

@@ -137,6 +137,12 @@ export type FunctionTrigger =
   | { kind: 'http'; path?: string }
   | { kind: 'cron'; schedule: string }
   | { kind: 'queue'; source: string }
+  /** `webhook`: the function is woken by a webhook_subscription fan-out whose
+   *  target_url is `<edge>/v1/internal/fn/trigger/<name>?tenant=<id>`. `source` is
+   *  an event-name PREFIX filter (e.g. 'payments.'), enforced at delivery — a
+   *  non-matching event is ACK-200 skipped. Declaring the binding is what opts the
+   *  function into event delivery; a receiver that declares only `cron` keeps the
+   *  older cron+{} wake. */
   | { kind: 'webhook'; source: string }
   | { kind: 'cmsHook'; collection: string; event: 'beforeCreate' | 'beforeUpdate' | 'beforeWrite' }
   | { kind: 'authHook'; event?: AuthHookEvent };
@@ -154,7 +160,35 @@ export interface FunctionDef {
   secrets?: string[];
   /** Outbound host allowlist (deny-by-default egress guard). */
   egressAllow?: string[];
-  limits?: { cpuMs?: number; timeoutMs?: number; memoryMb?: number };
+  /** Per-function resource declarations. Both optional; both clamped server-side.
+   *  `memoryMb` was REMOVED (2026-09-18): memory is fixed by the managed runtime
+   *  and is not per-dispatch selectable. A config that still declares it pushes
+   *  fine — the key is stripped, and `vxil plan --explain` marks it DROPPED. */
+  limits?: {
+    /** per-dispatch isolate CPU ceiling, ms (5..300000). Only ever TIGHTENS the
+     *  platform cap.
+     *
+     *  IT ALSO RAISES YOUR BILL on a metered tenant, and that is worth reading
+     *  twice: it raises (never lowers) the per-invoke credit reserve, whose floor
+     *  is the manifest default — and the reserve is the CEILING the pro-rated
+     *  settle clamps into, because the settle can never commit more than the hold
+     *  it releases from. So an invoke whose wall time exceeds `defaultLimits.cpuMs`
+     *  (50) settles at its MEASURED wall-ms instead of being capped at 50:
+     *  declaring `cpuMs: 1000` makes an 800 ms invoke cost 800 instead of 50.
+     *  Declaring only `timeoutMs` leaves metering byte-identical.
+     *
+     *  It does NOT affect anyone else's availability: the account-wide daily
+     *  capacity budget counts the platform's own per-invoke estimate, never this
+     *  value (workers/functions-v1/src/capacity.ts `capacityReserveCpuMs`). */
+    cpuMs?: number;
+    /** wall budget for ONE outbound fetch this function makes, ms (1000..120000,
+     *  default 30000). Not a whole-invocation budget: three 25 s fetches still
+     *  take 75 s. The invocation is bounded separately by the platform's own
+     *  deadline (`FN_MAX_INVOKE_MS`, default ≥ 5 minutes), which raising this
+     *  value widens with you. The vxil API callback leg keeps the platform's
+     *  own 30 s bound. */
+    timeoutMs?: number;
+  };
   enabled?: boolean;
   /** optional typed contract surfaced by `vxil gen` (Level 1, §4.5). */
   signature?: { input?: unknown; output?: unknown };