@volter/twin-inngest 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,131 @@
+# @volter/twin-inngest
+
+> **Legacy connector helpers:** this package still has callable helpers using the retired v1
+> `syncPull` API. Those paths require migration before use on the current kernel;
+> older helper descriptions below do not establish current compatibility. Check the
+> [generated index](../../../generated/INDEX.md) for protocol standing and use the
+> [shared model](../../../docs/concepts/the-model.md) for current state semantics.
+
+Local Inngest twin for the **durable-execution workflow-orchestration** surface: event send
+(Event API), function register/introspect (SDK exec protocol), and a REAL kernel-persisted
+**step machine** — `step.run` memoize/replay, `step.sleep`/`sleepUntil` instant-advance,
+`step.waitForEvent` gating, and exact retry-attempt counting — plus run status/get/list and
+event-based cancellation, built on the shared `@volter/world-core` kernel. API-first vendor (no
+product UI to mirror — the dev-server/cloud dashboard is a run-inspection state view, not an
+agent navigation target).
+
+```bash
+bun packages/twin/inngest/src/cli.ts
+```
+
+## Three API surfaces + host/path split
+
+Real Inngest addresses THREE distinct surfaces with overlapping shapes, routed here by
+`routeInngestSurface` (path-primary — see `inngest-twin.ts` header):
+
+1. **Event API** — `POST /e/{eventKey}` — GROUNDED against the installed `inngest@4.12.0` SDK's
+   own compiled source (`Inngest.send()` builds `new URL('e/'+eventKey, eventBaseUrl)`, and its
+   `options.baseUrl` / `INNGEST_BASE_URL` / `INNGEST_EVENT_API_BASE_URL` env override — VERIFIED
+   live before `inngest-sdk.integration.test.ts` was written — routes `.send()` at any host,
+   including this twin).
+2. **SDK exec protocol** — `/api/inngest` (GET introspect, PUT register, POST — a **twin-only
+   simplification**, see below) and `/fn/register` (POST — the real SDK's actual outbound
+   registration target, grounded from `InngestCommHandler.js`'s `inngestRegisterUrl`).
+3. **Dev-server/cloud v2 REST API** — `/api/v2/*` — GROUNDED at this EXACT path from a
+   live-fetched first-party OpenAPI document (`api-docs.inngest.com/api-specs/v2.json`,
+   `servers[1].url == "http://localhost:8288/api/v2"`) — this **corrects** the original build
+   spec's speculative `/v1/*` guess (a genuine, disclosed grounding upgrade, not a demotion).
+
+## The durable-execution step machine (the signature strength)
+
+`inngest-runtime.ts` is written FRESH for this pack. This twin does **not** execute real user
+code — there is no sandboxed JS runtime here. A function's steps are **declared** up front (a
+`step_plan` array on the `functions.register` body — a twin-only extension of the real wire
+payload; the real SDK infers steps by re-running the handler up to its next `step.*()` call,
+which a local twin cannot reproduce without a real running app). Given a declared plan, the twin
+reproduces the real durable-execution **semantics** faithfully:
+
+- **`steps.run_memoized` / `steps.replay_deterministic`** — every step's output is persisted to a
+  `step:<runId>::<stepId>` kernel row. Re-invoking (polling) a run **replays** every already-
+  completed step by reading its persisted output back out of the kernel — never recomputing it —
+  before advancing to the next uncompleted step. A 2-step run where step-2's output is a hash
+  function of step-1's memoized output proves this: an empty kernel (the mutation-test's
+  `httpEmpty` saboteur) makes step-1 "replay" as missing, so step-2's value comes out wrong.
+- **`steps.sleep_instant`** — `Sleep`/`sleepUntil` steps complete on first touch, no wall clock.
+- **`steps.wait_for_event_*`** — a `WaitForEvent` step holds the run at `RUNNING` (never jumps to
+  `COMPLETED`) until a matching-name event arrives; a non-matching event never resolves it; an
+  optional declared poll-count timeout resolves it with `output: null` (a **deterministic
+  poll-count**, never a real wall-clock timeout).
+- **`steps.retry_*`** — a step can declare `failTimes: N` (fail N times, then succeed on attempt
+  N+1); `attempts` is an exact, kernel-persisted counter. Exceeding the configured
+  `config.retries` (default 4, doc-unverified exact vendor default) transitions the **run** to
+  `FAILED` with an error, never silently succeeding.
+
+`exec.sdk_executor_roundtrip` — a real running app + real step handler functions Inngest calls
+into over HTTP — is the filed `todo`.
+
+## Cancellation is event-based, not a REST call
+
+The REAL Inngest cancellation mechanism (grounded live,
+`inngest.com/docs/features/inngest-functions/cancellation`): a function declares
+`cancelOn: [{event, if}]`; sending a matching event cancels its non-terminal runs. The
+live-fetched v2 OpenAPI document has **no REST cancel-run endpoint at all** — this twin's
+`runs.cancel_via_event` capability models the real mechanism, not a fabricated `DELETE`. The `if`
+CEL-style expression (grounded shape: `event.data.id == async.data.id`) is matched on **event
+name only** today (config-acceptance done); full expression evaluation is
+`scheduling.cancel_if_expression` (todo).
+
+## Coverage
+
+This is a v1 slice of the Inngest API, not the full surface. Modeled **`done`** (38): event
+send (single/batch/idempotent/validation), function register/re-register/introspect/trigger-
+match/fanout/cron-registration, run created/get/status-progression/isolation/unknown-404/
+event-runs-list/cancel-via-event/cancel-conflict, the full step machine (memoize, **replay**,
+sequential progression, sleep, **waitForEvent** gate/resolve/wrong-name/timeout, **retry** exact-
+count/then-success/exhausted), concurrency config echo, HMAC sign/verify/tamper, read-only/
+unmodeled-route safety, kernel-persisted state, conformance snapshot, and a handle-driven
+connector pull (idempotent).
+
+Left as **`todo`** (32, honest gaps — includes several REAL, live-confirmed v2 REST endpoints not
+yet modeled): the real SDK-executor round-trip and its real wire step-op protocol, cross-function
+`InvokeFunction`, parallel step fan-out, Inngest Connect (persistent WS execution channel), real
+cron-tick/debounce/throttle/rate-limit/batching/priority/singleton/concurrency-key enforcement
+physics, the `cancelOn` `if`-expression evaluator, `POST /runs/{id}/rerun` and
+`GET /runs/{id}/trace` (both REAL v2 endpoints, live-fetched, not yet modeled), real pagination
+over the event-runs list, multi-trigger functions, `step.ai` / AI Gateway, event-key/signing-key
+auth parity, the FULL v2 error-code taxonomy, 429 rate-limiting, connector push + step-trace pull,
+and fixture seeding. `events.get_by_id` is filed `todo` but **confirmed absent** from the real v2
+REST API (no `GET /events/{id}` path exists at all — only `GET /events/{id}/runs`) — kept for
+forward-compatibility, not because it's a live gap.
+
+**Planned (todo):** enforce the accepted flow-control config deterministically — concurrency
+limits, throttle, debounce, rate-limit and event batching are accepted and echoed back today but
+never enforced (`inngest.scheduling.flow_control_enforcement`) — and evaluate a cron trigger
+against the injected clock so a scheduled function actually runs
+(`inngest.scheduling.cron_evaluation`).
+
+See `src/inngest-capabilities.ts` for the full manifest (the real vendor surface is the
+denominator — coverage is honest and partial until the twin reaches it).
+
+## A note on grounding corrections over the original build spec
+
+This pack's build spec cited several shapes from doc-prose against `origin/twin-pinecone`,
+flagged for re-verification. Three genuine corrections came out of that re-verification (all
+disclosed in the landing commits, see spec-sources.json):
+
+- The dev-server/cloud REST management API lives at **`/api/v2/*`**, not `/v1/*` (live-fetched
+  first-party OpenAPI document, `api-docs.inngest.com/api-specs/v2.json`).
+- The real run-status enum is **`QUEUED | RUNNING | COMPLETED | FAILED | CANCELLED`** (uppercase,
+  with a `QUEUED` pre-run state — the v2 OpenAPI `v2FunctionRunStatus` schema), not the
+  spec-assumed mixed-case `Running/Completed/Failed/Cancelled`.
+- The `x-inngest-signature` header format is **`t=<unix_seconds>&s=<hex_hmac>`**
+  (`URLSearchParams`-encoded, SDK-source confirmed), not a bare hex signature; and the real
+  comm-handler's reject status for an invalid signature is **401** (`unauthorizedResponse`,
+  SDK-source confirmed), not the spec-cited 500 — filed as an annotation on
+  `auth.signature_500_reject_parity` (todo), not claimed either way as `done`.
+
+## No webhooks module
+
+Unlike replicate/fal/clerk, Inngest's Event API / exec protocol / v2 REST surface has no
+webhook-delivery concept of its own for this v1 slice — signing (`inngest-signing.ts`) covers the
+real executor↔SDK HMAC request-signing scheme instead, which is this pack's crypto surface.

package/dist/src/cli.d.ts

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+export {};

package/dist/src/cli.js

@@ -0,0 +1,26 @@
+#!/usr/bin/env node
+import { keepProcessAlive } from '@volter/world-core/lifecycle';
+// world-inngest CLI: serve the KERNEL-BACKED Inngest API twin, or run conformance. State
+// lives in the @volter/world-core action log (no in-memory side-store). Conformance is dev-only +
+// lazy-imported so the bin runs without @volter/world-tooling (E2).
+import { hasFlag, optionValue } from '@volter/world-core/args';
+import { createInngestTwinServer } from "./inngest-server.js";
+const [cmd, ...rest] = process.argv.slice(2);
+const port = Number(optionValue(rest, '--port', String(process.env.PORT ?? '0'))) || undefined;
+const root = optionValue(rest, '--root') || undefined;
+const readOnly = hasFlag(rest, '--read-only'); // a twin accepts writes unless started read-only
+if (cmd === 'serve' || cmd === undefined) {
+    const s = await createInngestTwinServer({ readOnly, ...(root ? { root } : {}), ...(port ? { port } : {}) });
+    process.stdout.write(`inngest twin (durable-execution workflow orchestration: events/functions/runs/steps, host/path split)${readOnly ? ' [read-only]' : ''} at http://127.0.0.1:${s.port}\n`);
+    await keepProcessAlive();
+}
+else if (cmd === 'conformance') {
+    const { checkInngestConformance } = await import("./inngest-conformance.js");
+    const report = checkInngestConformance();
+    process.stdout.write(`${JSON.stringify(report, null, 2)}\n`);
+    if (!report.ok)
+        process.exitCode = 1;
+}
+else {
+    process.stdout.write('Usage: world-inngest serve|conformance [--port N] [--root DIR] [--read-only]\n');
+}

package/dist/src/index.d.ts

@@ -0,0 +1,10 @@
+export { handleInngestTwinRequest, routeInngestSurface, inngestTwinSnapshot, INNGEST_RESOURCE_TYPES, } from './inngest-twin.js';
+export type { InngestRequest, InngestResponse, InngestResourceType, InngestSurface, InngestTwinSnapshot, } from './inngest-twin.js';
+export { createInngestTwinFetch, createInngestTwinServer, type InngestTwinFetchOptions } from './inngest-server.js';
+export { mapEvent, mapRun, pullInngestEvents, pullInngestRuns, syncInngestFromReal, } from './inngest-connector.js';
+export type { InngestLikeClient, InngestEventHandle, InngestRunHandle, InngestRealEvent, InngestRealRun, InngestBudgetedOptions } from './inngest-connector.js';
+export { INNGEST_BUDGETED_METHODS, INNGEST_BUDGET_CEILING, INNGEST_BUDGET_MAX_RETRY_AFTER_S, INNGEST_BUDGET_WINDOW_MS, INNGEST_CALL_WEIGHTS, INNGEST_RATE_BUDGET, InngestBudget, InngestBudgetError, inngestBudgetPath, inngestCallWeight, inngestClientBudget, guardInngestClient, } from './inngest-budget.js';
+export type { InngestBudgetErrorKind, InngestBudgetOptions, InngestBudgetReservation, InngestBudgetSnapshot } from './inngest-budget.js';
+export { INNGEST_SIGNING_KEY_TYPE, inngestSigningKey, mintInngestSigningKey, storedInngestSigningKey, signInngestRequest, buildInngestSignatureHeader, verifyInngestSignature, InngestSignatureError, } from './inngest-signing.js';
+import type { TwinPack } from '@volter/world-core';
+export declare const pack: TwinPack;

package/dist/src/index.js

@@ -0,0 +1,61 @@
+// @volter/twin-inngest — the Inngest durable-execution / event-driven workflow-orchestration
+// twin, built on the shared @volter/world-core kernel. REST transport over three surfaces: the Event
+// API (POST /e/{eventKey}), the SDK execution protocol (/api/inngest, /fn/register), and the
+// dev-server/cloud v2 REST management API (/api/v2/*, GROUNDED at that exact path from a
+// live-fetched first-party OpenAPI document — see inngest-twin.ts header). State lives entirely
+// in the kernel action log (no side-store).
+//
+// THE DECLARED STEP PLAN: this twin does not run user code — a function's steps
+// are DECLARED (at register time, or by a test) as an ordered `step_plan`, and the twin advances
+// that plan deterministically with REAL kernel-persisted memoization/replay (step outputs are
+// read back from the kernel on every re-invocation, never recomputed), instant sleep/sleepUntil
+// advance (no wall clock), waitForEvent gating (holds a run at a step until a matching event
+// arrives, or a deterministic poll-count timeout), and an exact retry-attempt counter. This is
+// the manifest files calling into a real running app as `exec.sdk_executor_roundtrip`.
+export { handleInngestTwinRequest, routeInngestSurface, inngestTwinSnapshot, INNGEST_RESOURCE_TYPES, } from "./inngest-twin.js";
+export { createInngestTwinFetch, createInngestTwinServer } from "./inngest-server.js";
+export { mapEvent, mapRun, pullInngestEvents, pullInngestRuns, syncInngestFromReal, } from "./inngest-connector.js";
+// The client-side rate budget — the fail-closed backstop every live call goes through. The
+// MECHANISM is the kernel's shared, vendor-agnostic `RateBudget`; what lives here is this vendor's
+// DECLARATION (window/ceiling/per-method weights) plus `guardInngestClient`, the choke point the
+// connector entrypoints apply unconditionally. Exported so an operator can inspect spend
+// (`snapshot`) and a caller can catch `InngestBudgetError` by type; there is deliberately no export
+// that disables the guard.
+export { INNGEST_BUDGETED_METHODS, INNGEST_BUDGET_CEILING, INNGEST_BUDGET_MAX_RETRY_AFTER_S, INNGEST_BUDGET_WINDOW_MS, INNGEST_CALL_WEIGHTS, INNGEST_RATE_BUDGET, InngestBudget, InngestBudgetError, inngestBudgetPath, inngestCallWeight, inngestClientBudget, guardInngestClient, } from "./inngest-budget.js";
+export { INNGEST_SIGNING_KEY_TYPE, inngestSigningKey, mintInngestSigningKey, storedInngestSigningKey, signInngestRequest, buildInngestSignatureHeader, verifyInngestSignature, InngestSignatureError, } from "./inngest-signing.js";
+import { INNGEST_RATE_BUDGET as RATE_BUDGET } from "./inngest-budget.js";
+export const pack = {
+    // The SAME object inngest-budget.ts declares at module load — one source of truth, so registering
+    // the pack and importing the connector can never arm two different ceilings.
+    rateBudget: RATE_BUDGET,
+    vendor: 'inngest',
+    transport: 'rest',
+    archetype: 'crud',
+    bin: 'world-inngest',
+    // The subject types the twin SERVES over its own API — the R2 resource-level claim, held in
+    // lockstep with inngest-twin.ts's INNGEST_RESOURCE_TYPES. `signing_key` IS here: the world's
+    // executor<->SDK signing key is minted once from real entropy and persisted
+    // (inngest-signing.ts), and `GET /api/v2/keys/signing` establishes it on first touch — a real
+    // held subject, not a name with nothing behind it. What that route serves stays masked.
+    resources: ['event', 'function', 'run', 'step', 'signing_key'],
+    // World wiring — declared HERE, not in init.ts's central table (descriptor-first exemplar (adding-a-twin.md §3)).
+    endpointEnv: {
+        name: 'INNGEST_BASE_URL',
+        templates: { INNGEST_EVENT_API_BASE_URL: '${url}' },
+        note: 'no injector entry: the inngest SDK is base-URL-configured through INNGEST_BASE_URL / INNGEST_EVENT_API_BASE_URL.',
+    },
+    specSource: 'inngest-conformance.ts (self-referential endpoint/resource inventory) — grounded read-only against inngest.com/docs, the installed inngest@4.12.0 npm package source (npm pack), and the live-fetched v2 REST OpenAPI document (api-docs.inngest.com/api-specs/v2.json); see spec-sources.json.',
+    description: 'Inngest durable-execution workflow-orchestration twin — event send (Event API), function register/introspect (SDK exec protocol), and a kernel-persisted step machine (step.run memoize/replay, sleep/sleepUntil instant-advance, waitForEvent gating, exact retry-attempt counters), run status/get/list, event-based cancellation, HMAC-SHA256 executor<->SDK request signing. Twin does not execute real user code — steps are declared, not run. Kernel-backed.',
+    browserRouting: { apiPathPrefix: '/', loaderHost: 'http://localhost:8288' },
+    // INTERCEPTION RULING — hostsNone, the pack's own home for it: SDK is base-URL-configured by
+    // design (options.baseUrl / INNGEST_BASE_URL / INNGEST_EVENT_API_BASE_URL, verified in the
+    // pack README) — worlds wire the twin through those vars.
+    hostsNone: "SDK is base-URL-configured by design (options.baseUrl / INNGEST_BASE_URL / INNGEST_EVENT_API_BASE_URL, verified in the pack README) — worlds wire the twin through those vars",
+    // Adoption, moved off the central maps unchanged (descriptor-first back-migration, adding-a-twin.md §3,
+    // 2026-08-31).
+    adoption: {
+        // Inngest's official Python SDK - same distribution name as the npm one.
+        pypi: ['inngest'],
+        sdks: ['inngest'], envStems: ['INNGEST'],
+    },
+};

package/dist/src/inngest-budget.d.ts

@@ -0,0 +1,83 @@
+import { RateBudget, type RateBudgetDeclaration, type RateBudgetOptions, type RateBudgetReservation, type RateBudgetSnapshot } from '@volter/world-core';
+import type { InngestLikeClient } from './inngest-connector.js';
+/** Rolling window, in ms. Spend older than this is pruned. */
+export declare const INNGEST_BUDGET_WINDOW_MS = 60000;
+/** Weighted units allowed inside one window. See the header for where this number comes from. */
+export declare const INNGEST_BUDGET_CEILING = 60;
+/** Seconds. A `Retry-After` above this means the credential is throttled hard — fail loudly. */
+export declare const INNGEST_BUDGET_MAX_RETRY_AFTER_S = 300;
+/** Per-call cost, keyed by the client method the guard is about to invoke. See the header. */
+export declare const INNGEST_CALL_WEIGHTS: {
+    /** Every modeled call. Inngest publishes no per-endpoint rate to differentiate. */
+    readonly other: 2;
+};
+/**
+ * The client methods this pack PRICES BY NAME, as dotted paths into the injected client.
+ *
+ * Two kinds of entry: (a) every method this connector actually calls, and (b) an endpoint the
+ * VENDOR documents in a distinct tier which a consumer can reach through the guarded client even
+ * though this connector never calls it (see the weights section of the header). Used to build the
+ * guarded surface — and, in the pack's own suite, the counting fake.
+ *
+ * NOT a closed list, and not a claim about the injected client's shape. A path the real client does
+ * not have is SKIPPED (this connector's members are optional; inventing one would turn "observe
+ * nothing" into "call something that isn't there"), and a method absent from this list is still
+ * PRICED at `defaultWeight` when a caller reaches for it — an unmodeled endpoint must never be
+ * free, and dropping one would be worse than free because it would be invisible.
+ */
+export declare const INNGEST_BUDGETED_METHODS: readonly ["events.get", "runs.get"];
+/** THE PACK'S DECLARATION — pure data, the only Inngest-specific thing in the whole budget. */
+export declare const INNGEST_RATE_BUDGET: RateBudgetDeclaration;
+/** Price one Inngest call by its client method key (a dotted path, e.g. `events.get`). */
+export declare function inngestCallWeight(method: string): number;
+/** Where Inngest's ledger lives. Token-keyed and cwd-independent by default (the vendor limits per
+ *  credential, so a cwd-scoped ledger would hand the same credential a fresh allowance in every
+ *  checkout, worktree and CI matrix leg); pass `root` to opt into world-scoped accounting. */
+export declare function inngestBudgetPath(opts?: {
+    root?: string;
+    token?: string;
+} | string): string;
+/** Construction options for Inngest's budget. The vendor is fixed; everything else may only TIGHTEN. */
+export type InngestBudgetOptions = Omit<RateBudgetOptions, 'vendor'>;
+/**
+ * Inngest's budget — the shared kernel guard bound to this vendor's declaration. A real subclass,
+ * not an alias, so `budget instanceof InngestBudget` means "a budget that accounts against this
+ * vendor's ledger under this vendor's ceiling": another vendor's `RateBudget` (with its own,
+ * possibly larger, ceiling) is NOT assignable where one of these is required.
+ */
+export declare class InngestBudget extends RateBudget {
+    constructor(opts?: InngestBudgetOptions);
+}
+export type { RateBudgetErrorKind as InngestBudgetErrorKind } from '@volter/world-core';
+export { RateBudgetError as InngestBudgetError } from '@volter/world-core';
+export type InngestBudgetReservation = RateBudgetReservation;
+export type InngestBudgetSnapshot = RateBudgetSnapshot;
+/** What every budgeted connector entrypoint accepts. There is deliberately no option that turns the
+ *  guard OFF — only ones that say WHICH ledger and clock to account against. */
+export type InngestBudgetedOptions = {
+    /** An existing budget to share across calls. Omit and one is constructed. Cannot be null. */
+    budget?: InngestBudget;
+    /** Construction options for the default budget (ledger path, clock). Cannot loosen it. */
+    budgetOptions?: InngestBudgetOptions;
+};
+/** Pull the budget wiring out of a caller's opts bag, so an entrypoint can forward it verbatim. */
+export declare function inngestBudgetOf(opts: InngestBudgetedOptions): InngestBudgetedOptions;
+/** Is this client already behind a budget? Returns the budget it is behind, if so. */
+export declare function inngestClientBudget(client: unknown): RateBudget | undefined;
+/**
+ * Wrap an INJECTED Inngest client so EVERY call it makes is charged against the shared budget
+ * BEFORE the request goes out. This pack's connector never constructs the transport itself (the
+ * consumer injects a client that satisfies `InngestLikeClient` structurally), so the guard is a
+ * DECORATOR rather than a factory — which is exactly why every connector entrypoint applies it
+ * UNCONDITIONALLY instead of trusting the caller to have done it.
+ *
+ * IDEMPOTENT: wrapping an already-guarded client returns it unchanged, so a caller who forgot is
+ * protected and a caller who wrapped deliberately is not double-charged.
+ *
+ * A method that THROWS is still inspected: an SDK typically RAISES on a 429 rather than returning
+ * it, and that error's back-off is exactly the signal that must become a persisted cooldown. Losing
+ * it would leave the ledger cheerfully spending into a throttled credential. The original error is
+ * always re-raised afterwards — the budget never swallows a vendor failure — EXCEPT when the
+ * back-off is beyond the cap, where the budget's own louder "stop calling" error takes precedence.
+ */
+export declare function guardInngestClient(client: InngestLikeClient, opts?: InngestBudgetedOptions): InngestLikeClient;