@leed-ai/cli 0.0.0-stage → 6.19.0

package/dist/static/customer-site-worker/src/proxyHeaders.ts

@@ -0,0 +1,47 @@
+import type { Context } from "hono";
+import type { Env } from "./types";
+
+/**
+ * Build the header set the customer-functions service binding expects on every
+ * proxied request. Shared by `proxyToFunctions` (proxy.ts) and `proxyMcp`
+ * (mcp-proxy.ts), which inject the identical trusted context.
+ *
+ * Clones the inbound request headers (so the visitor's `Cookie` — including the
+ * Docs MCP `__lid`/`__sid` set during the OAuth authorize flow — round-trips to
+ * the origin), then stamps the trusted values the origin relies on:
+ *  - `companyId` — the per-site tenant id (trusted; baked into this worker).
+ *  - `preview` — whether this is a preview build.
+ *  - `turnstileSecretKey` — forwarded for the origin's Turnstile checks.
+ *  - `originUrl` — the visitor-facing request URL.
+ *  - `x-real-ip` — the client IP. Cloudflare delivers it to this Worker as
+ *    `cf-connecting-ip` (Miniflare sets `127.0.0.1` for local `wrangler dev`);
+ *    customer-functions' middleware reads it under the `x-real-ip` name.
+ *    `Headers.set` overwrites any client-supplied value, so it is not spoofable.
+ */
+export function buildProxyHeaders(c: Context<{ Bindings: Env }>): Headers {
+  const headers = new Headers(c.req.raw.headers);
+  headers.set("companyId", c.env.COMPANY_ID);
+  headers.set("preview", String(c.env.PREVIEW_SITE));
+  headers.set("turnstileSecretKey", c.env.TURNSTILE_SECRET_KEY);
+  headers.set("originUrl", c.req.url);
+  headers.set("x-real-ip", c.req.header("cf-connecting-ip") ?? "");
+  return headers;
+}
+
+/**
+ * Dispatch a proxied request to customer-functions (#284).
+ *
+ * Production path: the `FUNCTIONS` service binding. Local-dev override: when
+ * `FUNCTIONS_ORIGIN` is set, the request is re-targeted at that origin (keeping
+ * the inbound path + query) and sent via global `fetch`, bypassing wrangler's
+ * cross-`wrangler dev` registry. Both branches are identical except the target —
+ * same `init` (method/headers/body/redirect), so callers share one request shape.
+ */
+export function fetchFunctions(c: Context<{ Bindings: Env }>, init: RequestInit): Promise<Response> {
+  if (c.env.FUNCTIONS_ORIGIN) {
+    const inbound = new URL(c.req.url);
+    const target = new URL(inbound.pathname + inbound.search, c.env.FUNCTIONS_ORIGIN);
+    return fetch(new Request(target, init));
+  }
+  return c.env.FUNCTIONS.fetch(new Request(c.req.url, init));
+}

package/dist/static/customer-site-worker/src/tier.ts

@@ -0,0 +1,40 @@
+/**
+ * Entitlement tier ladder for edge gating (#329).
+ *
+ * Lives in the worker because the worker is the constrained side: it is a
+ * standalone hono-only bundle (the build copies its `src/` + an isolated
+ * package.json with only `hono` into the customer site repo) and so CANNOT
+ * import `@leed/*` — `hasFeature` and `FEATURE_MIN_TIER` are unreachable here.
+ * The same reason `constants.ts` and the `DocResource` mirror live in this
+ * directory.
+ *
+ * So the tier is baked into the worker as `ENTITLEMENT_TIER` and compared here.
+ * The ladder itself is duplicated, which is safe — it is four values that define
+ * the pricing model — but the per-feature MINIMUM below is exactly the kind of
+ * value that moves. `tierDrift.test.ts` on the site-management side (which CAN
+ * import both) asserts these constants still match `FEATURE_MIN_TIER`, so a
+ * change to the catalog fails a test instead of silently un-gating a customer.
+ */
+
+/** Ordered low → high. Mirrors `TIER_RANK` in `@leed/data-types` featureCatalog. */
+export const TIER_RANK: Record<string, number> = {
+  free: 0,
+  starter: 1,
+  growth: 2,
+  enterprise: 3,
+};
+
+/** Minimum tier for live docs search — mirrors `FEATURE_MIN_TIER.docsLiveSearch`. */
+export const DOCS_LIVE_SEARCH_MIN_TIER = "starter";
+
+/**
+ * Whether `tier` reaches `minimum` on the ladder.
+ *
+ * FAIL-CLOSED on anything unrecognized, matching `hasFeature`: an unknown or
+ * missing tier meets no paid minimum. The one caller compensates for the
+ * "missing" case deliberately — see the guard in `index.ts`.
+ */
+export function meetsTier(tier: string | undefined, minimum: string): boolean {
+  if (!tier || !Object.hasOwn(TIER_RANK, tier)) return false;
+  return TIER_RANK[tier] >= TIER_RANK[minimum];
+}

package/dist/static/customer-site-worker/src/types.ts

@@ -0,0 +1,82 @@
+/**
+ * Vendored mirror of the Docs MCP `DocResource` (#284).
+ *
+ * The canonical Zod schema lives with the Docs MCP server at
+ * `apps/customer-functions/src/mcp/docResource.ts`. This worker is a standalone
+ * hono-only bundle — the build copies its `src/` + an isolated package.json
+ * (only `hono`) into the customer site repo, and wrangler runs `bun install`
+ * against that package.json — so it CANNOT import any `@leed/*` workspace
+ * package. The Docs MCP hydration only needs the shape to fill `content`, so this
+ * hand-written interface is kept intentionally in sync with the canonical Zod
+ * schema. Keep the two structurally compatible.
+ */
+export interface DocResource {
+  pageId?: string;
+  path: string;
+  url: string;
+  title?: string;
+  setId?: string;
+  content?: string;
+  error?: string;
+}
+
+/** The content-bearing tool-response envelope the site-worker hydrates. */
+export interface DocResourcesPayload {
+  resources: DocResource[];
+}
+
+export interface Env {
+  ASSETS: Fetcher;
+  FUNCTIONS: Fetcher;
+  /**
+   * Local-dev override (#284). When set (only in devMode wrangler configs),
+   * proxied requests go to this origin via global `fetch` instead of the
+   * `FUNCTIONS` service binding. Works around wrangler's cross-`wrangler dev`
+   * registry not reliably linking `customer-functions-dev` locally. Never
+   * emitted for public/preview builds — production keeps the service binding.
+   */
+  FUNCTIONS_ORIGIN?: string;
+  COMPANY_ID: string;
+  VALID_ORIGINS: string;
+  PREVIEW_SITE: boolean;
+  TURNSTILE_SECRET_KEY: string;
+  /**
+   * Per-customer MCP entitlement (#284, #294). Boolean wrangler var, baked
+   * into the generated wrangler config from the company's `entitlements.mcp`.
+   * When false the site-worker short-circuits AT THE EDGE both the `/mcp` +
+   * OAuth surface (the request never reaches customer-functions; customer-
+   * functions keeps its own `entitlements.mcp` check as defense-in-depth) and
+   * the `/.well-known/webmcp` + `/.well-known/agent.json` surfaces (404).
+   */
+  MCP_ENABLED: boolean;
+  /**
+   * The company's entitlement tier (#329) — `free` | `starter` | `growth` |
+   * `enterprise`. Baked so the edge can gate on the SAME tier ladder the rest of
+   * the platform uses, rather than a per-feature boolean per gate.
+   *
+   * Optional: a worker generated before this var existed carries no tier, and
+   * must DEFER to customer-functions rather than 404 its own search — so the
+   * guard checks for absence explicitly instead of relying on fail-closed
+   * `meetsTier`.
+   */
+  ENTITLEMENT_TIER?: string;
+  /**
+   * Commit SHA baked into this worker version at build time. Emitted on
+   * every response as `X-Site-Version` so `curl -I` against a customer
+   * site reveals which commit is currently live.
+   */
+  SITE_VERSION: string;
+  /**
+   * Plaintext "true"/"false" — when "true" the workers.dev hostname is
+   * gated and any request hitting it without the CMS proxy header is 301'd
+   * to PRIMARY_DOMAIN. Emitted as "true" on public builds once the custom
+   * domain becomes active (preview builds always emit "false" — they
+   * disable workers.dev outright instead). #266
+   */
+  REDIRECT_TO_PRIMARY_DOMAIN: string;
+  /**
+   * Canonical custom domain — destination for the workers.dev redirect.
+   * Same value as the route hostname in wrangler.jsonc for this Worker.
+   */
+  PRIMARY_DOMAIN: string;
+}

package/dist/static/customer-site-worker/test/functions-mock.worker.js

@@ -0,0 +1,50 @@
+/**
+ * Auxiliary worker standing in for the `customer-functions` service binding in
+ * the customer-site-worker workerd integration test (#284). Plain JS because the
+ * workers-pool loads auxiliary `scriptPath` modules without TS transformation.
+ *
+ * Routes:
+ *  - `/mcp/oauth/authorize` — mirrors the production OAuth authorize grant:
+ *    reads the forwarded body and answers with a 302 → client `redirect_uri`,
+ *    echoing the body back on `X-Forwarded-Body` so the proxy test can confirm
+ *    it forwarded the body intact.
+ *  - `/__302` / `/__follow_target` — a real redirect boundary used by the
+ *    mechanism test to prove WHY the proxy must buffer the request body: a
+ *    `fetch(..., { redirect: "follow" })` whose body is a one-time-use stream
+ *    throws "encountered a redirect requiring the body to be retransmitted" on
+ *    the 302, while a buffered (ArrayBuffer) body replays cleanly.
+ *
+ * Reached through the customer-site-worker's real `FUNCTIONS` service binding,
+ * so the proxy's `FUNCTIONS.fetch(... redirect: "manual")` call crosses the
+ * genuine workerd subrequest boundary the node-pool unit tests mock away.
+ */
+export default {
+  async fetch(request) {
+    const url = new URL(request.url);
+
+    if (url.pathname === "/mcp/oauth/authorize") {
+      const forwarded = await request.text();
+      return new Response(null, {
+        status: 302,
+        headers: {
+          Location: "https://client.example.com/cb?code=abc&state=xyz",
+          "X-Forwarded-Body": forwarded,
+        },
+      });
+    }
+
+    if (url.pathname === "/__302") {
+      return new Response(null, { status: 302, headers: { Location: "/__follow_target" } });
+    }
+    if (url.pathname === "/__follow_target") {
+      // Reached only after workerd follows the 302 above (a 302 of a POST
+      // becomes a bodyless GET per the fetch spec). Its presence proves the
+      // followed-redirect path completed without the body-retransmit throw.
+      return new Response("ok", { headers: { "X-Replayed": "1" } });
+    }
+
+    return new Response(JSON.stringify({ jsonrpc: "2.0", id: 1, result: { ok: true } }), {
+      headers: { "content-type": "application/json" },
+    });
+  },
+};

package/dist/static/customer-site-worker/tsconfig.json

@@ -0,0 +1,19 @@
+{
+  "compilerOptions": {
+    "target": "ESNext",
+    "module": "ESNext",
+    "moduleResolution": "bundler",
+    "lib": ["ESNext"],
+    "types": ["@cloudflare/workers-types"],
+    "strict": true,
+    "skipLibCheck": true,
+    "esModuleInterop": true,
+    "forceConsistentCasingInFileNames": true
+  },
+  "include": ["src/**/*.ts"],
+  // Co-located tests (run by vitest, excluded from the customer bundle by the
+  // build's copy filter) pull in test-only virtual modules like `cloudflare:test`
+  // that this production-bundle tsconfig has no types for. Keep them out of this
+  // project's typecheck — the test suites are typechecked by vitest. (#284)
+  "exclude": ["src/**/*.test.ts", "src/**/*.spec.ts"]
+}

package/dist/static/customer-site-worker/vitest.workers.config.ts

@@ -0,0 +1,61 @@
+import { cloudflareTest } from "@cloudflare/vitest-plugin";
+import { defineConfig } from "vitest/config";
+
+/**
+ * Workers-pool (Miniflare / workerd) config for the customer-site-worker (#284).
+ *
+ * The existing `mcp-proxy.test.ts` unit tests run in the NODE pool with a
+ * hand-built `env` whose `FUNCTIONS.fetch` is a plain `vi.fn()` — so they never
+ * exercise workerd's real subrequest machinery and PASSED even while the live
+ * proxy threw the "one-time-use body … requiring the body to be retransmitted"
+ * error on the OAuth-302. This config boots the actual worker (`src/index.ts`)
+ * in workerd; the `FUNCTIONS` binding is a real auxiliary mock worker
+ * (`test/functions-mock.worker.js`) that answers the OAuth authorize grant with
+ * the 302 → client `redirect_uri`, so the `.worker.test` suite drives the proxy
+ * across the genuine service-binding boundary. The node-pool tests are
+ * untouched: the site-management root config excludes the `.worker.test` glob.
+ */
+export default defineConfig({
+  plugins: [
+    cloudflareTest({
+      main: "./src/index.ts",
+      // No wrangler.jsonc lives in this dir (the production config is generated
+      // per-customer by the wrangler generator at build time), so the worker is
+      // configured inline here.
+      miniflare: {
+        compatibilityDate: "2026-04-07",
+        serviceBindings: {
+          // The customer-functions stand-in (see test/functions-mock.worker.js).
+          FUNCTIONS: "functions-mock",
+          // ASSETS is only consulted on page-resources hydration, never on a 302.
+          ASSETS: async () => new Response("should-not-be-called", { status: 404 }),
+        },
+        bindings: {
+          COMPANY_ID: "co-test",
+          VALID_ORIGINS: JSON.stringify(["https://docs.example.com"]),
+          PREVIEW_SITE: false,
+          TURNSTILE_SECRET_KEY: "ts-test",
+          SITE_VERSION: "abcdef0",
+          REDIRECT_TO_PRIMARY_DOMAIN: "false",
+          PRIMARY_DOMAIN: "docs.example.com",
+          MCP_ENABLED: true,
+        },
+        workers: [
+          {
+            name: "functions-mock",
+            modules: true,
+            scriptPath: "./test/functions-mock.worker.js",
+            compatibilityDate: "2026-04-07",
+          },
+        ],
+      },
+    }),
+  ],
+  test: {
+    name: "customer-site-worker-workers",
+    include: ["src/**/*.worker.test.ts"],
+    globals: true,
+    testTimeout: 30000,
+    teardownTimeout: 5000,
+  },
+});

package/dist/static/install/husky/colors.mjs

@@ -0,0 +1,5 @@
+const tty = process.stderr.isTTY;
+const wrap = (code) => (s) => (tty ? `\x1b[${code}m${s}\x1b[0m` : s);
+
+export const red = wrap("1;31");
+export const yellow = wrap("33");

package/dist/static/install/husky/hooks/commit-msg

@@ -0,0 +1 @@
+node .husky/valid-commit-msg.mjs "$1"

package/dist/static/install/husky/hooks/pre-commit

@@ -0,0 +1 @@
+node .husky/valid-command.mjs "commit"

package/dist/static/install/husky/hooks/pre-push

@@ -0,0 +1 @@
+node .husky/valid-command.mjs "push"

package/dist/static/install/husky/valid-command.mjs

@@ -0,0 +1,29 @@
+import { execSync as shell } from "node:child_process";
+import { red, yellow } from "./colors.mjs";
+
+const args = process.argv.slice(2);
+const [command] = args;
+
+/**
+ * We use git to see if the leed.invoked flag was set.
+ */
+let invokedByScript = false;
+try {
+  invokedByScript = shell("git config --get leed.invoked").toString().trim();
+} catch (_e) {
+  // any exit code other than zero is caught
+}
+
+/**
+ * If it was not invoked by our application, we spit out an error
+ * and the application help command.
+ */
+if (invokedByScript !== "true") {
+  console.error(red(`\n\tYou cannot '${command}' directly, please use:\n`));
+  if (command === "commit") {
+    console.error(yellow(`\t\tleed site commit -m "update details"\n`));
+  } else if (command === "push") {
+    console.error(yellow(`\t\tleed site push\n`));
+  }
+  process.exit(18); // Exit with error code to block the commit
+}

package/dist/static/install/husky/valid-commit-msg.mjs

@@ -0,0 +1,20 @@
+import fs from "node:fs";
+import { red, yellow } from "./colors.mjs";
+
+// Read the commit message from the file passed by Git
+const commitMessageFile = process.argv[2];
+const commitMessage = fs.readFileSync(commitMessageFile, "utf-8").trim();
+
+const startMsg = "@leed/site-management=>";
+const pos = commitMessage.indexOf(startMsg);
+if (pos > -1) {
+  const data = commitMessage.substring(startMsg.length);
+  const json = JSON.parse(data);
+  if (json.userId && json.version && json.message) {
+    process.exit(0);
+  }
+}
+
+console.error(red("\n\tYou cannot commit directly to this repo, please use:\n"));
+console.error(yellow(`\t\tleed site commit -m "reason for update"\n`));
+process.exit(18); // Exit with error code to block the commit

package/dist/static/install/package.json

@@ -0,0 +1,10 @@
+{
+    "name": "@leed/site",
+    "version": "1.0.0",
+    "description": "Website being built by Leed",
+    "type": "module",
+    "author": "Leed AI",
+    "scripts": {},
+    "devDependencies": {
+    }
+}

package/dist/static/install/packages.txt

@@ -0,0 +1,4 @@
+@tailwindcss/forms@0.5.11
+@tailwindcss/typography@0.5.19
+tailwindcss@4.2.4
+husky@9.1.7

package/dist/static/install/tasks.json

@@ -0,0 +1,111 @@
+{
+  "version": "2.0.0",
+  "_description": "VS Code Tasks to simplify execution of the application",
+  "command": "leed",
+  "tasks": [
+    {
+      "label": "Run Webserver",
+      "type": "shell",
+      "args": ["site", "build", "--serve"],
+      "problemMatcher": [],
+      "group": {
+        "kind": "build",
+        "isDefault": true
+      }
+    },
+    {
+      "label": "Build",
+      "type": "shell",
+      "args": ["site", "build"],
+      "problemMatcher": [],
+      "group": {
+        "kind": "build",
+        "isDefault": true
+      }
+    },
+    {
+      "label": "Build (debug)",
+      "type": "shell",
+      "args": ["site", "build", "-d"],
+      "problemMatcher": [],
+      "group": {
+        "kind": "build",
+        "isDefault": true
+      }
+    },
+    {
+      "label": "Site Validation",
+      "type": "shell",
+      "args": ["site", "validate"],
+      "problemMatcher": [],
+      "group": {
+        "kind": "build",
+        "isDefault": true
+      }
+    },
+    {
+      "label": "Site Validation - Reset (Dry-Run)",
+      "type": "shell",
+      "args": ["site", "validate", "-r", "--dry-run"],
+      "problemMatcher": [],
+      "group": {
+        "kind": "build",
+        "isDefault": true
+      }
+    },
+    {
+      "label": "Site Validation - Reset",
+      "type": "shell",
+      "args": ["site", "validate", "-r"],
+      "problemMatcher": [],
+      "group": {
+        "kind": "build",
+        "isDefault": true
+      }
+    },
+    {
+      "label": "Commit Changes",
+      "type": "shell",
+      "args": ["site", "commit", "-m ${input:commitMsg}"],
+      "problemMatcher": []
+    },
+    {
+      "label": "Push to Staging",
+      "type": "shell",
+      "args": ["site", "push"],
+      "problemMatcher": []
+    },
+    {
+      "label": "Pull Latest from Staging",
+      "type": "shell",
+      "command": "git pull",
+      "problemMatcher": []
+    },
+    {
+      "label": "Login",
+      "type": "shell",
+      "args": ["auth", "login", "--browser"],
+      "problemMatcher": []
+    },
+    {
+      "label": "Logout",
+      "type": "shell",
+      "args": ["auth", "logout"],
+      "problemMatcher": []
+    },
+    {
+      "label": "Auth Status",
+      "type": "shell",
+      "args": ["auth", "status"],
+      "problemMatcher": []
+    }
+  ],
+  "inputs": [
+    {
+      "id": "commitMsg",
+      "type": "promptString",
+      "description": "Enter a commit message",
+      "default": "update site content"
+    }
+  ]
+}