@vendoai/vendo 0.4.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,28 @@
+# @vendoai/vendo
+
+Vendo puts an agent inside your product. Customers can build views, act through
+your APIs, and automate work inside your brand and guardrails.
+
+```bash
+npm install @vendoai/vendo
+npx vendo init
+```
+
+This is the default composition: the public wire handler, React provider,
+policy-bound agent and app blocks, persistence, MCP door, and the `vendo` CLI.
+Install individual `@vendoai/*` blocks only when you want to compose Vendo
+yourself.
+
+Vendo extracts host APIs as signed-in-user tools, renders theme-driven React
+surfaces, applies approvals and audit at one execution choke point, and uses
+PGlite locally with the same schema on production Postgres. The store runtime
+(`createStore`, `envSecrets`, `storeSecrets`, `secretStore`) is re-exported
+from `@vendoai/vendo/server` for production deploys.
+
+The composed agent reads `.vendo/brief.md` and the component catalog + theme
+into its system prompt, cancels a turn when the client disconnects, and caps
+tool steps per turn via `agent.maxSteps` (default 20) with a visible
+step-limit notice in the stream.
+
+Read the [quickstart](https://docs.vendo.run/quickstart) and
+[CLI reference](https://docs.vendo.run/reference/cli).

package/bin/vendo.mjs

@@ -0,0 +1,4 @@
+#!/usr/bin/env node
+import { main } from "../dist/cli.js";
+
+process.exitCode = await main(process.argv.slice(2));

package/dist/ai-sdk.d.ts

@@ -0,0 +1,35 @@
+import { type ToolSet } from "ai";
+import type { Vendo } from "./server.js";
+/**
+ * `@vendoai/vendo/ai-sdk` — the BYO-agent seam for AI SDK loops (frozen
+ * contract: docs/superpowers/specs/2026-07-20-existing-agents-contracts.md §2).
+ * One thin format shim over the framework-neutral tool pack in
+ * `@vendoai/agent`, executing through `vendo.guardedTools` — the guard-bound
+ * registry Vendo's own loop shares, decorated to park pending-approval calls
+ * so `<VendoApprovalEmbed>` can resume them over the wire — plus
+ * `agent.asRunner()` behind `vendo_delegate`. No tool reachable from the host
+ * loop has an unguarded route.
+ */
+export { VENDO_CREATE_APP_TOOL, VENDO_DELEGATE_TOOL, VENDO_TOOL_PACK_PREFIX, type VendoDelegateResult, type VendoToolPackFilter, type VendoToolPackOptions, } from "@vendoai/agent";
+import type { VendoToolPackOptions } from "@vendoai/agent";
+/**
+ * Build the Vendo tool pack as an AI SDK `ToolSet` for `streamText`/
+ * `generateText`. Built PER REQUEST: tool execution needs a principal-scoped
+ * RunContext, so resolve the caller's principal first and spread the result
+ * into your route handler's `tools`:
+ *
+ * ```ts
+ * const result = streamText({
+ *   model,
+ *   messages,
+ *   tools: { ...myTools, ...(await vendoTools(vendo, { principal })) },
+ * });
+ * ```
+ *
+ * A `vendo_*` tool returns either a versioned envelope — `vendo/app-ref@1`
+ * (render with `<VendoAppEmbed>`) or `vendo/approval-ref@1` (parks server-side;
+ * render with `<VendoApprovalEmbed>`) — or plain data, meaning the guarded call
+ * executed cleanly. `options.sessionId` carries the host session id into audit;
+ * unset, the shim mints one per pack build.
+ */
+export declare function vendoTools(vendo: Vendo, options: VendoToolPackOptions): Promise<ToolSet>;

package/dist/ai-sdk.js

@@ -0,0 +1,62 @@
+import { buildVendoToolPack } from "@vendoai/agent";
+import { VendoError } from "@vendoai/core";
+import { dynamicTool, jsonSchema } from "ai";
+/**
+ * `@vendoai/vendo/ai-sdk` — the BYO-agent seam for AI SDK loops (frozen
+ * contract: docs/superpowers/specs/2026-07-20-existing-agents-contracts.md §2).
+ * One thin format shim over the framework-neutral tool pack in
+ * `@vendoai/agent`, executing through `vendo.guardedTools` — the guard-bound
+ * registry Vendo's own loop shares, decorated to park pending-approval calls
+ * so `<VendoApprovalEmbed>` can resume them over the wire — plus
+ * `agent.asRunner()` behind `vendo_delegate`. No tool reachable from the host
+ * loop has an unguarded route.
+ */
+export { VENDO_CREATE_APP_TOOL, VENDO_DELEGATE_TOOL, VENDO_TOOL_PACK_PREFIX, } from "@vendoai/agent";
+/**
+ * Build the Vendo tool pack as an AI SDK `ToolSet` for `streamText`/
+ * `generateText`. Built PER REQUEST: tool execution needs a principal-scoped
+ * RunContext, so resolve the caller's principal first and spread the result
+ * into your route handler's `tools`:
+ *
+ * ```ts
+ * const result = streamText({
+ *   model,
+ *   messages,
+ *   tools: { ...myTools, ...(await vendoTools(vendo, { principal })) },
+ * });
+ * ```
+ *
+ * A `vendo_*` tool returns either a versioned envelope — `vendo/app-ref@1`
+ * (render with `<VendoAppEmbed>`) or `vendo/approval-ref@1` (parks server-side;
+ * render with `<VendoApprovalEmbed>`) — or plain data, meaning the guarded call
+ * executed cleanly. `options.sessionId` carries the host session id into audit;
+ * unset, the shim mints one per pack build.
+ */
+export async function vendoTools(vendo, options) {
+    if (typeof options?.principal?.kind !== "string" || typeof options.principal.subject !== "string") {
+        throw new VendoError("validation", "vendoTools requires a principal — resolve the host session's user before building the pack");
+    }
+    // The frozen context tuple for a BYO loop: a chat surface that is not
+    // Vendo's, with the user present. Park-and-resume replays pin this tuple.
+    const ctx = {
+        principal: options.principal,
+        venue: "chat",
+        presence: "present",
+        sessionId: options.sessionId ?? `session_${globalThis.crypto.randomUUID()}`,
+    };
+    const pack = await buildVendoToolPack({
+        registry: vendo.guardedTools,
+        runner: vendo.agent.asRunner(),
+        ...(options.include === undefined ? {} : { include: options.include }),
+        ...(options.exclude === undefined ? {} : { exclude: options.exclude }),
+    });
+    const tools = {};
+    for (const entry of pack) {
+        tools[entry.name] = dynamicTool({
+            description: entry.description,
+            inputSchema: jsonSchema(entry.inputSchema),
+            execute: (input, { toolCallId }) => entry.execute(input, { ctx, callId: toolCallId }),
+        });
+    }
+    return tools;
+}

package/dist/auth-presets/auth-js.d.ts

@@ -0,0 +1,14 @@
+import type { HostAuthPreset, HostAuthPresetOptions } from "./shared.js";
+/**
+ * 09-vendo §2.1 — the Auth.js host-identity preset. Zero-argument in the
+ * standard case: the secret is AUTH_SECRET, the secure-cookie posture follows
+ * VENDO_BASE_URL (https → `__Secure-` names), and the principal's display
+ * derives from the session token's name/email claims. An optional subject→user
+ * resolver overrides claims-derived identity for BOTH the principal display and
+ * the actAs session claims; its null means "subject unknown to host" (the
+ * session is treated as absent, actAs declines, the door's lookup returns null).
+ *
+ * The actAs half IS the shipped `@vendoai/actions/presets` authJsPreset — one
+ * minting story (04 §2.1), configured from these same options.
+ */
+export declare function authJs(options?: HostAuthPresetOptions): HostAuthPreset;

package/dist/auth-presets/auth-js.js

@@ -0,0 +1,91 @@
+// authJsPreset ships on its own subpath, not the shared "@vendoai/actions/presets"
+// barrel: it is the only preset there with a top-level optional-peer dynamic
+// import (@auth/core/jwt), and bundlers resolve every `export ... from` target
+// in a barrel file regardless of which export a consumer uses (corpus-triage
+// Task 9 — mirrors the same split done for this file's own vendo-side barrel).
+import { authJsPreset } from "@vendoai/actions/presets/auth-js";
+import { environment } from "../wire/shared.js";
+import { actAsClaimsFromUser, composeHostAuthPreset, lazyActAs, lazyModule, loginRedirect, makeUserResolver, resolvePresetSecret, userFromNameEmailClaims, } from "./identity.js";
+/** Same optional-dependency strategy as the actions preset's own encoder
+    (packages/actions presets/auth-js.ts): `@auth/core` is an optional
+    peerDependency loaded lazily on first use — a host wiring authJs() already
+    runs Auth.js, so it is present next to their auth setup. The failure is an
+    actionable install instruction, not a bare module-not-found. */
+const MISSING_AUTH_CORE_MESSAGE = "authJs() reads the Auth.js session through @auth/core, which is not installed. Install it alongside your Auth.js setup: npm install @auth/core";
+const MISSING_SECRET_MESSAGE = "authJs() has no session secret: set AUTH_SECRET (mirroring Auth.js itself) or pass authJs({ secret }).";
+/** Node's dynamic-import failure for a package that simply isn't installed. */
+function isAuthCoreNotFound(error) {
+    return error instanceof Error
+        && error.code === "ERR_MODULE_NOT_FOUND"
+        && error.message.includes("@auth/core");
+}
+const loadGetToken = lazyModule(() => import("@auth/core/jwt").then((module) => module.getToken), MISSING_AUTH_CORE_MESSAGE);
+/** Secure-cookie posture, generalized from demo-bank's isSecureDeployment: the
+    deployment is secure exactly when the operator-set VENDO_BASE_URL parses as
+    an https URL — TLS terminates at a trusted proxy and Auth.js is using its
+    `__Secure-` cookie names. Same trusted-origin channel the umbrella already
+    uses for anon-cookie hardening and door metadata; never derived from
+    forwarded headers. */
+function isSecureDeployment() {
+    const base = environment("VENDO_BASE_URL");
+    if (base === undefined)
+        return false;
+    try {
+        return new URL(base).protocol === "https:";
+    }
+    catch {
+        return false;
+    }
+}
+/**
+ * 09-vendo §2.1 — the Auth.js host-identity preset. Zero-argument in the
+ * standard case: the secret is AUTH_SECRET, the secure-cookie posture follows
+ * VENDO_BASE_URL (https → `__Secure-` names), and the principal's display
+ * derives from the session token's name/email claims. An optional subject→user
+ * resolver overrides claims-derived identity for BOTH the principal display and
+ * the actAs session claims; its null means "subject unknown to host" (the
+ * session is treated as absent, actAs declines, the door's lookup returns null).
+ *
+ * The actAs half IS the shipped `@vendoai/actions/presets` authJsPreset — one
+ * minting story (04 §2.1), configured from these same options.
+ */
+export function authJs(options = {}) {
+    const { secret, user } = options;
+    const sessionClaims = async (request) => {
+        const getToken = await loadGetToken();
+        return getToken({
+            req: request,
+            secret: await resolvePresetSecret(secret, "AUTH_SECRET", MISSING_SECRET_MESSAGE),
+            secureCookie: isSecureDeployment(),
+        });
+    };
+    // Away + MCP execution: the shipped Auth.js minting preset, fed the same
+    // secret/posture/identity this preset resolves sessions with. Built lazily
+    // on FIRST MINT and cached (its TokenCache survives across calls): the
+    // secure-cookie posture then resolves at use time like the secret does,
+    // never racing env loading at composition. A missing @auth/core fails with
+    // the same actionable install error as the other two halves, not the
+    // encoder's bare module-not-found.
+    const mint = lazyActAs(() => authJsPreset({
+        ...(secret === undefined ? {} : { secret }),
+        secureCookie: isSecureDeployment(),
+        ...(user === undefined ? {} : { claims: actAsClaimsFromUser(user) }),
+    }));
+    const actAs = async (principal, grant) => {
+        try {
+            return await mint(principal, grant);
+        }
+        catch (error) {
+            if (isAuthCoreNotFound(error)) {
+                throw new Error(MISSING_AUTH_CORE_MESSAGE, { cause: error });
+            }
+            throw error;
+        }
+    };
+    return composeHostAuthPreset({
+        sessionClaims,
+        resolveUser: makeUserResolver(user, userFromNameEmailClaims),
+        actAs,
+        login: (request, returnTo) => loginRedirect(request, returnTo),
+    });
+}

package/dist/auth-presets/auth0.d.ts

@@ -0,0 +1,23 @@
+import type { HostAuthPreset, HostAuthPresetOptions } from "./shared.js";
+/**
+ * 09-vendo §2.1 — the Auth0 host-identity preset. Zero-argument in the
+ * standard case: the tenant reads Auth0's own env (AUTH0_DOMAIN, or the v3
+ * AUTH0_ISSUER_BASE_URL; AUTH0_AUDIENCE enforced when set), the session is
+ * the Auth0-issued RS256 JWT presented as Authorization: Bearer and verified
+ * against the tenant JWKS with the issuer check, and display derives from the
+ * OIDC name/email claims. The optional subject→user resolver has the same
+ * semantics as authJs (null = subject unknown → decline/null). The Auth0
+ * SDK's encrypted `appSession` cookie is SDK-internal and stays with the
+ * host's own middleware — it is not a verifiable token.
+ *
+ * Auth0 holds the private keys for its RS256 sessions, so the actAs half is
+ * the shipped away-token producer (`auth0Preset`, 04 §2.1) — minting a
+ * host-owned `VendoAway` token under VENDO_AWAY_TOKEN_SECRET; the matching
+ * verify half stays host-mounted middleware (producer/verify split). The
+ * `secret` option therefore overrides the AWAY-TOKEN secret (the preset's
+ * system-equivalent shared secret).
+ *
+ * The door's sessionless redirect follows the Auth0 v4 SDK's route
+ * convention: /auth/login, which natively honors returnTo.
+ */
+export declare function auth0(options?: HostAuthPresetOptions): HostAuthPreset;

package/dist/auth-presets/auth0.js

@@ -0,0 +1,98 @@
+import { auth0Preset } from "@vendoai/actions/presets";
+import { environment } from "../wire/shared.js";
+import { actAsClaimsFromUser, bearerToken, composeHostAuthPreset, lazyActAs, lazyModule, loginRedirect, makeUserResolver, userFromNameEmailClaims, } from "./identity.js";
+/** Same optional-dependency strategy as authJs's @auth/core: jose is an
+    optional peerDependency loaded lazily on first use (Auth0's RS256 tokens
+    verify against the tenant JWKS — provider-held keys, 04 §2.1, so a JOSE
+    verifier is required and jose is the SDK Auth0's own libraries build on).
+    The failure is an actionable install instruction, not a bare
+    module-not-found. */
+const MISSING_JOSE_MESSAGE = "auth0() verifies Auth0 session tokens through jose, which is not installed. Install it next to your Auth0 setup: npm install jose";
+const MISSING_DOMAIN_MESSAGE = "auth0() has no tenant domain: set AUTH0_DOMAIN (e.g. your-tenant.us.auth0.com — mirroring the Auth0 SDKs) or AUTH0_ISSUER_BASE_URL.";
+const loadJose = lazyModule(() => import("jose").then((module) => module), MISSING_JOSE_MESSAGE);
+/** The tenant issuer per Auth0's env conventions: AUTH0_DOMAIN (the v4 SDK's
+    bare domain, scheme tolerated), else AUTH0_ISSUER_BASE_URL (the v3 SDK's
+    full URL). Auth0 issuers always carry the trailing slash. */
+function tenantIssuer() {
+    const domain = environment("AUTH0_DOMAIN");
+    if (domain !== undefined) {
+        return domain.startsWith("http://") || domain.startsWith("https://")
+            ? `${new URL(domain).origin}/`
+            : `https://${domain}/`;
+    }
+    const base = environment("AUTH0_ISSUER_BASE_URL");
+    if (base !== undefined) {
+        try {
+            return `${new URL(base).origin}/`;
+        }
+        catch {
+            throw new Error(MISSING_DOMAIN_MESSAGE);
+        }
+    }
+    throw new Error(MISSING_DOMAIN_MESSAGE);
+}
+/** jose's remote JWKS resolvers cache fetched keys per instance — keep one per
+    tenant URL so verification never refetches per request. */
+const jwksByUrl = new Map();
+function tenantJwks(jose, issuer) {
+    const url = new URL(".well-known/jwks.json", issuer).toString();
+    let jwks = jwksByUrl.get(url);
+    if (jwks === undefined) {
+        jwks = jose.createRemoteJWKSet(new URL(url));
+        jwksByUrl.set(url, jwks);
+    }
+    return jwks;
+}
+/**
+ * 09-vendo §2.1 — the Auth0 host-identity preset. Zero-argument in the
+ * standard case: the tenant reads Auth0's own env (AUTH0_DOMAIN, or the v3
+ * AUTH0_ISSUER_BASE_URL; AUTH0_AUDIENCE enforced when set), the session is
+ * the Auth0-issued RS256 JWT presented as Authorization: Bearer and verified
+ * against the tenant JWKS with the issuer check, and display derives from the
+ * OIDC name/email claims. The optional subject→user resolver has the same
+ * semantics as authJs (null = subject unknown → decline/null). The Auth0
+ * SDK's encrypted `appSession` cookie is SDK-internal and stays with the
+ * host's own middleware — it is not a verifiable token.
+ *
+ * Auth0 holds the private keys for its RS256 sessions, so the actAs half is
+ * the shipped away-token producer (`auth0Preset`, 04 §2.1) — minting a
+ * host-owned `VendoAway` token under VENDO_AWAY_TOKEN_SECRET; the matching
+ * verify half stays host-mounted middleware (producer/verify split). The
+ * `secret` option therefore overrides the AWAY-TOKEN secret (the preset's
+ * system-equivalent shared secret).
+ *
+ * The door's sessionless redirect follows the Auth0 v4 SDK's route
+ * convention: /auth/login, which natively honors returnTo.
+ */
+export function auth0(options = {}) {
+    const { secret, user } = options;
+    const sessionClaims = async (request) => {
+        const token = bearerToken(request);
+        if (token === undefined)
+            return null;
+        const issuer = tenantIssuer();
+        const audience = environment("AUTH0_AUDIENCE");
+        const jose = await loadJose();
+        try {
+            const { payload } = await jose.jwtVerify(token, tenantJwks(jose, issuer), {
+                issuer,
+                ...(audience === undefined ? {} : { audience }),
+            });
+            return payload;
+        }
+        catch {
+            return null; // unverifiable/expired/foreign token = no session
+        }
+    };
+    return composeHostAuthPreset({
+        sessionClaims,
+        resolveUser: makeUserResolver(user, userFromNameEmailClaims),
+        // Away + MCP execution: the shipped away-token producer half (04 §2.1);
+        // the host mounts the matching verify middleware on its API.
+        actAs: lazyActAs(() => auth0Preset({
+            ...(secret === undefined ? {} : { secret }),
+            ...(user === undefined ? {} : { claims: actAsClaimsFromUser(user) }),
+        }).actAs),
+        login: (request, returnTo) => loginRedirect(request, returnTo, "/auth/login"),
+    });
+}

package/dist/auth-presets/clerk.d.ts

@@ -0,0 +1,23 @@
+import type { HostAuthPreset, HostAuthPresetOptions } from "./shared.js";
+/**
+ * 09-vendo §2.1 — the Clerk host-identity preset. Zero-argument in the
+ * standard case: session verification reads Clerk's own env (CLERK_SECRET_KEY;
+ * CLERK_JWT_KEY when set enables Clerk's networkless path and is preferred),
+ * the session token comes off the request per Clerk's conventions (the
+ * `__session` cookie or Authorization: Bearer), and display derives from
+ * name/email claims. The optional subject→user resolver has the same
+ * semantics as authJs (null = subject unknown → decline/null).
+ *
+ * Clerk holds the private keys for its RS256 sessions, so the actAs half is
+ * the shipped away-token producer (`clerkPreset`, 04 §2.1) — minting a
+ * host-owned `VendoAway` token under VENDO_AWAY_TOKEN_SECRET; the matching
+ * verify half stays host-mounted middleware (producer/verify split). The
+ * `secret` option therefore overrides the AWAY-TOKEN secret (the preset's
+ * system-equivalent shared secret), never the Clerk secret key, which is an
+ * API credential and stays env-only.
+ *
+ * The door's sessionless redirect follows Clerk's sign-in convention:
+ * NEXT_PUBLIC_CLERK_SIGN_IN_URL when set, else /sign-in, carrying both the
+ * standard returnTo and Clerk's redirect_url.
+ */
+export declare function clerk(options?: HostAuthPresetOptions): HostAuthPreset;

package/dist/auth-presets/clerk.js

@@ -0,0 +1,65 @@
+import { clerkPreset } from "@vendoai/actions/presets";
+import { environment } from "../wire/shared.js";
+import { actAsClaimsFromUser, bearerToken, composeHostAuthPreset, cookieValue, lazyActAs, lazyModule, loginRedirect, makeUserResolver, userFromNameEmailClaims, } from "./identity.js";
+/** Same optional-dependency strategy as authJs's @auth/core: @clerk/backend is
+    an optional peerDependency loaded lazily on first use — a host wiring
+    clerk() already runs Clerk, so it is present next to their auth setup. The
+    failure is an actionable install instruction, not a bare module-not-found. */
+const MISSING_CLERK_BACKEND_MESSAGE = "clerk() reads the Clerk session through @clerk/backend, which is not installed. Install it alongside your Clerk setup: npm install @clerk/backend";
+const MISSING_KEY_MESSAGE = "clerk() has no verification key: set CLERK_SECRET_KEY (mirroring Clerk's own SDKs), optionally with CLERK_JWT_KEY (the instance's PEM public key) for networkless verification.";
+const loadVerifyToken = lazyModule(() => import("@clerk/backend").then((module) => module.verifyToken), MISSING_CLERK_BACKEND_MESSAGE);
+/**
+ * 09-vendo §2.1 — the Clerk host-identity preset. Zero-argument in the
+ * standard case: session verification reads Clerk's own env (CLERK_SECRET_KEY;
+ * CLERK_JWT_KEY when set enables Clerk's networkless path and is preferred),
+ * the session token comes off the request per Clerk's conventions (the
+ * `__session` cookie or Authorization: Bearer), and display derives from
+ * name/email claims. The optional subject→user resolver has the same
+ * semantics as authJs (null = subject unknown → decline/null).
+ *
+ * Clerk holds the private keys for its RS256 sessions, so the actAs half is
+ * the shipped away-token producer (`clerkPreset`, 04 §2.1) — minting a
+ * host-owned `VendoAway` token under VENDO_AWAY_TOKEN_SECRET; the matching
+ * verify half stays host-mounted middleware (producer/verify split). The
+ * `secret` option therefore overrides the AWAY-TOKEN secret (the preset's
+ * system-equivalent shared secret), never the Clerk secret key, which is an
+ * API credential and stays env-only.
+ *
+ * The door's sessionless redirect follows Clerk's sign-in convention:
+ * NEXT_PUBLIC_CLERK_SIGN_IN_URL when set, else /sign-in, carrying both the
+ * standard returnTo and Clerk's redirect_url.
+ */
+export function clerk(options = {}) {
+    const { secret, user } = options;
+    const sessionClaims = async (request) => {
+        const token = bearerToken(request) ?? cookieValue(request, "__session");
+        if (token === undefined)
+            return null;
+        const jwtKey = environment("CLERK_JWT_KEY");
+        const secretKey = environment("CLERK_SECRET_KEY");
+        if (jwtKey === undefined && secretKey === undefined) {
+            throw new Error(MISSING_KEY_MESSAGE);
+        }
+        const verifyToken = await loadVerifyToken();
+        try {
+            return await verifyToken(token, {
+                ...(jwtKey === undefined ? {} : { jwtKey }),
+                ...(secretKey === undefined ? {} : { secretKey }),
+            });
+        }
+        catch {
+            return null; // unverifiable/expired token = no session, mirroring authJs
+        }
+    };
+    return composeHostAuthPreset({
+        sessionClaims,
+        resolveUser: makeUserResolver(user, userFromNameEmailClaims),
+        // Away + MCP execution: the shipped away-token producer half (04 §2.1);
+        // the host mounts the matching verify middleware on its API.
+        actAs: lazyActAs(() => clerkPreset({
+            ...(secret === undefined ? {} : { secret }),
+            ...(user === undefined ? {} : { claims: actAsClaimsFromUser(user) }),
+        }).actAs),
+        login: (request, returnTo) => loginRedirect(request, returnTo, environment("NEXT_PUBLIC_CLERK_SIGN_IN_URL") ?? "/sign-in", { redirect_url: returnTo }),
+    });
+}