@leed-ai/cli 0.0.0-stage → 6.19.0

package/dist/static/templates/sandbox/src/_includes/header-includes.hbs

@@ -0,0 +1,25 @@
+{{!--
+header-includes.hbs: the site's own additions to <head>, on every page.
+
+Leed's head partial, `leed/head.hbs`, renders this file first in <head>, on
+every page that calls it: the pages site-template.hbs wraps, Leed's
+unsubscribe pages, and the documentation and API pages. Those last are built
+on Leed's own documentation layouts, which are NOT wrapped in
+site-template.hbs, so a tag written there never reaches the documentation
+set. Written here, it reaches every page.
+
+There is nothing to turn on: no CMS flag and no plan tier. `leed/head.hbs`
+checks `templateExists "header-includes.hbs"`, so the file existing is what
+enables it.
+
+Put here what must be true on every page, docs included: a preload for a
+self-hosted web font (never a font host, which logs every visitor), site
+verification metas, analytics and
+other site-wide scripts (deferred), theme-color, the web manifest, and PNG
+and touch icon fallbacks. Tags only one kind of page needs go in that page
+type's layout. The description, canonical URL, social cards and the SVG
+favicon (the company favicon set in the CMS) are already written by
+`leed/head.hbs`.
+
+This file renders nothing until you add a tag below this comment.
+--}}

package/dist/static/templates/sandbox/src/_includes/header.hbs

@@ -0,0 +1,5 @@
+{{!-- Start Top Menu  --}}
+<header class="fixed w-full bg-[var(--site-header-bg-color,white)] grid justify-items-center z-40">
+    <!-- header menu goes here -->
+</header>
+{{!-- End Top Menu --}}

package/dist/static/templates/sandbox/src/_includes/site-template.hbs

@@ -0,0 +1,23 @@
+<!DOCTYPE html>
+<html lang="en" class="scroll-smooth js-focus-visible code-theme-atom-fruit">
+
+<head>
+    <title>{{ title }} | {{ siteTitle }}</title>
+
+    <meta name="viewport" content="width=device-width">
+
+    {{> leed/head }}
+</head>
+<body class="flex flex-col h-screen antialiased text-base text-(--site-text-color) bg-(--site-bg-color)">
+{{> header }}
+
+{{!-- We need to set the top margin, because it changes based on the header height --}}
+<div class="grow mt-(--height-header)">
+{{!-- Start Body Content --}}
+{{> @partial-block}}
+{{!-- End Body Content --}}
+</div>
+
+{{> footer }}
+</body>
+</html>

package/dist/static/templates/sandbox/src/_layouts/empty.hbs

@@ -0,0 +1,2 @@
+{{!-- Empty Layout --}}
+{{{ process content }}}

package/dist/static/templates/sandbox/src/index.hbs

@@ -0,0 +1,20 @@
+---
+{
+  "title": "Your sandbox site",
+  "publishedAt": "2026-01-01T00:00:00.000Z",
+  "modifiedAt": "2026-01-01T00:00:00.000Z",
+  "pageTypeId": "ph-pt-1",
+  "pageId": "ph-page-1"
+}
+---
+
+{{#>site-template}}
+
+<h1>Your sandbox site</h1>
+<p>This site runs on your machine only. It is not connected to a Leed account, so you can design and build it freely.</p>
+<ul>
+  <li>Preview it with <code>leed site build --serve</code>.</li>
+  <li>When you are happy with it, move it into Leed with <code>/leed:site-sandbox-move</code> in Claude.</li>
+</ul>
+
+{{/site-template}}

package/dist/static/templates/sandbox/src/robots.hbs

@@ -0,0 +1,9 @@
+---
+{
+    "permalink": "/robots.txt",
+    "eleventyExcludeFromCollections": true
+}
+---
+user-agent: *
+
+sitemap: {{ siteUrl }}/sitemap.xml

package/dist/static/templates/sandbox/src/src.11tydata.json

@@ -0,0 +1,39 @@
+{
+  "dateFormat": "MMM D, YYYY",
+  "deployment": {
+    "public": {
+      "domain": "localhost:8080",
+      "pagesDomain": "localhost:8080",
+      "turnstilePublicKey": "1x00000000000000000000AA",
+      "customDomainActive": false
+    },
+    "preview": {
+      "domain": "localhost:8080",
+      "pagesDomain": "localhost:8080",
+      "turnstilePublicKey": "1x00000000000000000000AA",
+      "customDomainActive": false
+    }
+  },
+  "ogCard": {
+    "title": "My sandbox site",
+    "description": "A Leed site built locally, before it has an account."
+  },
+  "paging": {
+    "minimum": 6,
+    "size": 9
+  },
+  "readingWpm": 250,
+  "siteDescription": "A Leed site built locally, before it has an account.",
+  "siteLocale": "en-us",
+  "siteTitle": "My sandbox site",
+  "documentationConfiguration": {
+    "menus": {
+      "top": "ph-menu-1",
+      "bottom": "ph-menu-2"
+    }
+  },
+  "entitlements": {
+    "tier": "enterprise",
+    "mcp": false
+  }
+}

package/dist/static/templates/sandbox/tailwind/site/base.css

@@ -0,0 +1,44 @@
+/*
+  The default border color has changed to `currentColor` in Tailwind CSS v4,
+  so we've added these compatibility styles to make sure everything still
+  looks the same as it did with Tailwind CSS v3.
+
+  If we ever want to remove these styles, we need to add an explicit border
+  color utility to any element that depends on these defaults.
+*/
+h1 {
+  @apply font-extrabold text-4xl sm:text-6xl text-(--site-header-1-color);
+}
+
+h2 {
+  @apply font-bold text-3xl sm:text-4xl mt-6 text-(--site-header-2-color);
+}
+
+h3 {
+  @apply font-extrabold text-xl sm:text-2xl mt-5 text-(--site-header-3-color);
+}
+
+h4 {
+  @apply font-bold text-xl sm:text-xl mt-4 text-(--site-header-4-color);
+}
+
+h1,
+h2,
+h3,
+h4,
+h5,
+h6 {
+  letter-spacing: -0.025em;
+}
+
+p {
+  @apply mt-4;
+}
+
+a {
+  @apply text-(--site-anchor-text-color) hover:text-(--site-anchor-text-color-hover) active:text-(--site-anchor-text-color-active);
+}
+
+pre {
+  @apply mt-8;
+}

package/dist/static/templates/sandbox/tailwind/site.config.css

@@ -0,0 +1,3 @@
+@import "tailwindcss" source("../src");
+
+@import "./site/base.css" layer(base);

package/dist/thrown-sukVkp_1.js

@@ -0,0 +1,113 @@
+/**
+* SPDX-FileCopyrightText: © 2024-2025 Leed, Inc.
+* SPDX-License-Identifier: LicenseRef-Leed-EULA
+*/
+import { i as externalCommandDetails, r as cliErrorFrom } from "./errors-CqKamGCu.js";
+//#region src/cli/output/thrown.ts
+/**
+* Machine-readable codes for errors that are NOT `CliUserError` (#333).
+*
+* `cliErrorFrom` maps anything that is not a `CliUserError` to
+* `internal_error`, which is correct for a genuine fault and wrong for the
+* throws this CLI makes deliberately from its `preAction` hooks — a missing
+* site checkout, an uninitialized site, a raw-content directory that
+* is not there. Those are ordinary user situations with a real remedy, and an
+* agent that reads `internal_error` for them files a bug instead of running
+* `leed site init`.
+*
+* They cannot simply become `CliUserError`s: `src/cli/index.ts` renders that
+* class as `Error: <message>` plus a hint line, while a plain `Error` reaches
+* the user through `log.error("The following error occurred: …")`. Both
+* renderings are pinned by the Phase 1 baseline, so changing the class changes
+* user-visible output.
+*
+* So the code travels ALONGSIDE the error instead of changing what it is: a
+* non-enumerable symbol property carrying the code, an optional cleaner
+* message for the JSON document, a hint and details. The thrown value keeps its
+* class, its `message` and its stack, so every human-mode path renders exactly
+* as before; only the `--json` branch reads the annotation.
+*
+* The property is non-enumerable and symbol-keyed on purpose: `util.inspect`
+* hides both by default, so an error that is later dumped with `console.error`
+* (src/cli/commit.ts) shows nothing new.
+*/
+/** Where the annotation is parked on the thrown value. */
+const ANNOTATION = Symbol.for("leed.cli.thrownAnnotation");
+/**
+* Attach `annotation` to `thrown` and return it, so a throw site reads
+* `throw annotateThrown(Error(MESSAGE), { code: "not_a_site_repo", hint })`.
+*
+* Non-object throws (a bare string) are returned untouched rather than
+* rejected: annotating is an enrichment, and failing to enrich must never turn
+* into a second failure on top of the one being reported.
+*/
+function annotateThrown(thrown, annotation) {
+	if (typeof thrown === "object" && thrown !== null) Object.defineProperty(thrown, ANNOTATION, {
+		value: annotation,
+		enumerable: false,
+		configurable: true,
+		writable: true
+	});
+	return thrown;
+}
+/** The annotation on `thrown`, or `null` when it carries none. */
+function annotationOf(thrown) {
+	if (typeof thrown !== "object" || thrown === null) return null;
+	const found = thrown[ANNOTATION];
+	if (typeof found !== "object" || found === null) return null;
+	return typeof found.code === "string" ? found : null;
+}
+/**
+* Convert anything thrown into the envelope's `error` object, honoring an
+* annotation when the throw site left one.
+*
+* Falls back to `cliErrorFrom`, so a `CliUserError` still keeps its own code,
+* message and hint and an unannotated fault is still `internal_error`.
+*/
+function cliErrorFromThrown(thrown) {
+	const annotation = annotationOf(thrown);
+	if (!annotation) return cliErrorFrom(thrown);
+	const message = annotation.message ?? messageOf(thrown);
+	const details = annotation.details ?? (annotation.code === "external_command_failed" ? externalCommandDetails(thrown) : void 0);
+	return {
+		code: annotation.code,
+		message,
+		...annotation.hint ? { hint: annotation.hint } : {},
+		...details ? { details } : {},
+		...annotation.next && annotation.next.length > 0 ? { next: [...annotation.next] } : {}
+	};
+}
+function messageOf(thrown) {
+	if (thrown instanceof Error) return thrown.message;
+	if (typeof thrown === "string") return thrown;
+	return String(thrown);
+}
+/** How many schema issues are worth listing before the rest are counted. */
+const MAX_SUMMARIZED_ISSUES = 8;
+/**
+* Summarize a `ZodError` as `path: message` pairs.
+*
+* The raw error's `message` is a multi-kilobyte JSON dump of every issue with
+* its input echoed back — unreadable for a person and useless for an agent,
+* which branches on `code` rather than parsing prose. This is what goes in
+* `error.details` instead, so the caller learns WHICH field is wrong without
+* the document swallowing the whole config file.
+*
+* Duck-typed on `issues` rather than `instanceof ZodError`: the CLI is bundled
+* and the schemas come from `@leed/data-types`, so two zod copies in one
+* process is a realistic failure mode for an identity check and a silent one.
+* Anything without an `issues` array falls back to its own message.
+*/
+function summarizeSchemaIssues(thrown) {
+	const issues = thrown?.issues;
+	if (!Array.isArray(issues) || issues.length === 0) return messageOf(thrown);
+	const listed = issues.slice(0, MAX_SUMMARIZED_ISSUES).map((issue) => {
+		const raw = issue ?? {};
+		return `${Array.isArray(raw.path) && raw.path.length > 0 ? raw.path.join(".") : "(root)"}: ${typeof raw.message === "string" ? raw.message : "invalid"}`;
+	});
+	const remaining = issues.length - listed.length;
+	if (remaining > 0) listed.push(`… and ${remaining} more problem${remaining === 1 ? "" : "s"}`);
+	return listed.join("; ");
+}
+//#endregion
+export { cliErrorFromThrown as n, summarizeSchemaIssues as r, annotateThrown as t };