@jay-framework/jay-stack-cli 0.22.2 → 0.23.1

package/agent-kit-template/plugin/add-menu-guide.md

@@ -0,0 +1,114 @@
+# AIditor Add-Menu Items
+
+Plugins contribute items to the AIditor's Add Menu via YAML catalog files generated by the agent-kit handler.
+
+The agent-kit handler writes to `agent-kit/aiditor/add-menu/<plugin-name>.yaml`. The AIditor discovers and loads all YAML files in this directory.
+
+## Required and recommended fields
+
+```yaml
+items:
+  - id: my-plugin:feature-name # required — unique, stable
+    title: Feature Name # required — shown in the add menu
+    category: My Plugin # required — top-level nav label
+    prompt: | # required — injected verbatim into agent task
+      Use headless component @my-org/my-plugin / contract feature-name.
+      Read agent-kit/designer/feature-name.md for usage guide.
+    pluginName: my-plugin # required — plugin attribution
+    packageName: '@my-org/my-plugin' # required — visibility filter
+    subCategory: Components # optional — second nav level
+```
+
+`pluginName` and `packageName` must always be set and must match the plugin's `plugin.yaml` name and npm package name respectively. AIditor uses them to filter items — only items whose `packageName` or `pluginName` matches an installed plugin are visible.
+
+## Interaction mode
+
+Every item should declare how the user attaches it:
+
+```yaml
+interaction:
+  mode: reference # default — attach as context or @mention
+```
+
+```yaml
+interaction:
+  mode: stage-place # click/drag onto live preview
+  stagePromptTemplate: | # placed at the marker location
+    Add a product card at this location using wix-stores/product-widget.
+```
+
+Use `reference` for data sources (contracts, categories). Use `stage-place` for visual elements the user places on the page (components, design tokens, effects).
+
+## Browse size
+
+Controls card size in the browse grid:
+
+```yaml
+browse:
+  size: small # 4 per row — color swatches, small tokens
+  size: medium # 2 per row — default
+  size: large # 1 per row — full-width previews
+```
+
+## Presentation (preview)
+
+Optional visual preview in the browse grid:
+
+```yaml
+# Static image
+presentation:
+  type: image
+  src: thumbnails/my-plugin/feature.png
+
+# HTML fragment — must use @scope for CSS isolation
+presentation:
+  type: html-fragment
+  html: |
+    <div>
+      <style>@scope { .demo { color: blue; } }</style>
+      <div class="demo">Preview content</div>
+    </div>
+```
+
+Html-fragment rules:
+
+- Single root `<div>`
+- `<style>` with `@scope { }` (even if CSS is inline-only)
+- No `<script>`, no `on*` handlers
+- Keep under 8 KB
+
+## TypeScript type
+
+Import `AddMenuItem` from `@jay-framework/plugin-validator` for type-safe item construction:
+
+```typescript
+import type { AddMenuItem } from '@jay-framework/plugin-validator';
+
+const items: AddMenuItem[] = [
+  {
+    id: 'my-plugin:feature',
+    title: 'Feature',
+    category: 'My Plugin',
+    pluginName: 'my-plugin',
+    packageName: '@my-org/my-plugin',
+    interaction: { mode: 'stage-place', stagePromptTemplate: 'Add feature here.' },
+    prompt: 'Use headless @my-org/my-plugin / contract feature.',
+  },
+];
+```
+
+## YAML serialization
+
+When writing YAML with `js-yaml`, use `noRefs: true` to prevent anchor/alias syntax (`&ref_0` / `*ref_0`) which the AIditor does not support:
+
+```typescript
+fs.writeFileSync(outputPath, yaml.dump({ items }, { lineWidth: 120, noRefs: true }), 'utf-8');
+```
+
+## Project settings (separate surface)
+
+Add Menu and **Project settings** are both materialized by the `agentkit` handler but use different paths and schemas. For a settings tab in AIditor, follow [aiditor-settings-guide.md](aiditor-settings-guide.md) — do not fold settings discovery into add-menu YAML.
+
+## Full reference
+
+See `agent-kit/plugin/aiditor-add-menu.md` (installed by `jay-stack setup aiditor`) for the full Add Menu contributor guide including validation rules, browse packing, and surface-specific behavior.

package/agent-kit-template/plugin/aiditor-settings-guide.md

@@ -0,0 +1,296 @@
+# AIditor Project Settings — Plugin Contributor Guide
+
+**Audience:** Plugin authors and AI agents adding a **Project settings** tab to a Jay Stack plugin.
+
+**Related guides:** [setup-guide.md](setup-guide.md) (agent-kit handler), [plugin-routes.md](plugin-routes.md) (`devOnly` routes), [add-menu-guide.md](add-menu-guide.md) (Add Menu — orthogonal surface). After `jay-stack setup aiditor`, see also `agent-kit/plugin/aiditor-add-menu.md` for AIditor runtime behavior (iframe, postMessage).
+
+---
+
+## What is Project settings?
+
+AIditor **Project settings** shows one tab per **installed** plugin that has a materialized discovery file under `agent-kit/aiditor/settings/`. Each tab embeds the plugin's settings **route** in an iframe (`?_jay_embed=true`).
+
+This is separate from:
+
+| Surface              | Purpose                                          | Plugin output                                        |
+| -------------------- | ------------------------------------------------ | ---------------------------------------------------- |
+| **Add Menu**         | Attach agent context to a change request         | `agent-kit/aiditor/add-menu/*.yaml`                  |
+| **Project settings** | Configure the project; run backend ops from a UI | `agent-kit/aiditor/settings/*.yaml` + dev-only route |
+| **Headless on page** | Site runtime                                     | contracts + components                               |
+
+---
+
+## Contributor checklist
+
+Follow these steps in order. Skipping a step is the most common reason a tab never appears.
+
+1. **Ship template in the npm package** at `agent-kit/aiditor/settings.template.yaml` (exact path — validated by `jay-stack validate-plugin`).
+2. **List `agent-kit/` in `package.json` `files`** so the template is included in the published npm tarball and available under `node_modules` after install.
+3. **Declare `agentkit` in `plugin.yaml`** and materialize the template in the agent-kit handler to `agent-kit/aiditor/settings/<plugin-name>.yaml` in the **project** root (not inside the package).
+4. **Declare a matching route** in `plugin.yaml` `routes[]` with **`devOnly: true`** (settings UIs are dev-server tooling).
+5. **Implement the settings page** — `lib/pages/settings/page.jay-html` + page component; use plugin **actions** or **jay-commands** for mutations (never arbitrary shell).
+6. **Run `jay-stack agent-kit`** in the consuming project and confirm the YAML file exists.
+7. **Run `jay-stack validate-plugin`** — fix errors; heed warnings for missing `devOnly` or route mismatch.
+
+---
+
+## Package layout
+
+```
+my-plugin/
+├── agent-kit/
+│   └── aiditor/
+│       └── settings.template.yaml    # shipped in package — source for copy/generate
+├── lib/
+│   ├── aiditor/
+│   │   └── write-settings-contribution.ts   # materialization helper
+│   ├── pages/
+│   │   └── settings/
+│   │       ├── page.jay-html
+│   │       └── page.ts
+│   └── agentkit.ts                  # calls materialize + other agent-kit work
+├── plugin.yaml
+└── package.json                     # "files": [..., "agent-kit"]
+```
+
+**Materialized output (project only, gitignored or committed per team policy):**
+
+```
+<project-root>/agent-kit/aiditor/settings/my-plugin.yaml
+```
+
+Use `<plugin>.generated.yaml` only for fixture/dogfood plugins that intentionally differ from the shipped template name.
+
+---
+
+## Settings template schema
+
+```yaml
+# agent-kit/aiditor/settings.template.yaml
+label: Media Manager # required — tab title in Project settings (text only in v1)
+route: /my-plugin/settings # required — must match plugin.yaml routes[].path
+pluginName: my-plugin # optional — defaults from output filename (my-plugin.yaml)
+requires: # optional — tab blocked until dependency setup succeeds
+  - plugin: wix-server-client
+    status: configured # only "configured" is valid in v1
+```
+
+Validate locally with types from `@jay-framework/plugin-validator`:
+
+```typescript
+import { validateAiditorSettingsFile } from '@jay-framework/plugin-validator';
+```
+
+---
+
+## plugin.yaml route
+
+Settings pages are **[dev-only plugin routes](plugin-routes.md#dev-only-routes)**. They are served on the dev server, hidden from page-navigation pickers that filter `devOnly`, and loaded by AIditor via explicit route URL.
+
+```yaml
+name: my-plugin
+agentkit: generateMyAgentKit
+
+routes:
+  - path: /my-plugin/settings
+    jayHtml: ./lib/pages/settings/page.jay-html
+    component: myPluginSettingsPage
+    description: Project settings — configure my-plugin for this project
+    devOnly: true
+```
+
+See [plugin-routes.md](plugin-routes.md) for route authoring, project override precedence, and standalone URL behavior.
+
+---
+
+## Materialize in the agent-kit handler
+
+**Do not** write settings YAML in the `setup` handler. Settings discovery is regenerated on **`jay-stack agent-kit`**, same as Add Menu catalogs.
+
+```typescript
+import type {
+  PluginAgentKitContext,
+  PluginAgentKitResult,
+} from '@jay-framework/stack-server-runtime';
+import { materializeMyPluginAiditorSettings } from './aiditor/write-settings-contribution.js';
+
+export async function generateMyAgentKit(
+  ctx: PluginAgentKitContext,
+): Promise<PluginAgentKitResult> {
+  const created: string[] = [];
+
+  const settingsPath = materializeMyPluginAiditorSettings(ctx.projectRoot, ctx.force);
+  if (settingsPath) created.push(settingsPath);
+
+  // ... add-menu, references, etc.
+
+  return {
+    agentKitCreated: created,
+    message: created.length ? `Wrote ${created.join(', ')}` : 'Up to date',
+  };
+}
+```
+
+### Static copy vs generated YAML
+
+| Case                              | Pattern                                                                                                |
+| --------------------------------- | ------------------------------------------------------------------------------------------------------ |
+| Fixed label + route               | Copy `settings.template.yaml` → `settings/<plugin>.yaml`                                               |
+| Label/route depends on live data  | Build YAML object in handler; write with `yaml.stringify`                                              |
+| Add Menu rebuild from settings UI | Write `add-menu/<plugin>.generated.yaml` only — never overwrite hand-authored `add-menu/<plugin>.yaml` |
+
+---
+
+## Resolving the packaged template path (required)
+
+Agent-kit handlers run from **bundled** `dist/index.js` in published packages. A fixed `path.join(__dirname, '..')` hop count **breaks** when the module lives under `dist/` vs `lib/` (Vitest) vs nested bundles.
+
+**Use a walk-up resolver** until `agent-kit/aiditor/settings.template.yaml` exists under a parent directory:
+
+```typescript
+import * as fs from 'node:fs';
+import * as path from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+export const AIDITOR_SETTINGS_OUTPUT_REL = 'agent-kit/aiditor/settings/my-plugin.yaml';
+const SETTINGS_TEMPLATE_REL = 'agent-kit/aiditor/settings.template.yaml';
+
+/**
+ * Resolve a file shipped inside the plugin package (agent-kit templates, etc.).
+ * Works from dist/index.js (production) and lib/aiditor/*.ts (Vitest).
+ */
+export function resolvePackagedAgentKitPath(
+  relativePath: string,
+  moduleUrl: string = import.meta.url,
+): string | null {
+  let directory = path.dirname(fileURLToPath(moduleUrl));
+  for (let depth = 0; depth < 4; depth++) {
+    const candidate = path.join(directory, relativePath);
+    if (fs.existsSync(candidate)) {
+      return candidate;
+    }
+    const parent = path.dirname(directory);
+    if (parent === directory) break;
+    directory = parent;
+  }
+  return null;
+}
+
+export function writeAiditorSettingsContribution(
+  projectRoot: string,
+  templatePath: string,
+  force = false,
+): string | null {
+  const outputPath = path.join(projectRoot, AIDITOR_SETTINGS_OUTPUT_REL);
+  if (fs.existsSync(outputPath) && !force) {
+    return null;
+  }
+  fs.mkdirSync(path.dirname(outputPath), { recursive: true });
+  fs.copyFileSync(templatePath, outputPath);
+  return AIDITOR_SETTINGS_OUTPUT_REL;
+}
+
+export function materializeMyPluginAiditorSettings(
+  projectRoot: string,
+  force = false,
+): string | null {
+  const templatePath = resolvePackagedAgentKitPath(SETTINGS_TEMPLATE_REL);
+  if (!templatePath) {
+    return null;
+  }
+  return writeAiditorSettingsContribution(projectRoot, templatePath, force);
+}
+```
+
+### Common mistakes
+
+| Mistake                                                                 | Symptom                                                                                                 |
+| ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
+| `path.join(dirname(import.meta.url), '..', '..')` from bundled code     | Walks to `node_modules/@jay-framework/` — template not found, **no settings YAML**                      |
+| **No client bundle** (`index.client.ts` + `vite build` without `--ssr`) | Settings iframe SSR works; Vite errors on hydrate — `Failed to resolve import .../dist/index.client.js` |
+| Writing YAML inside the package instead of `ctx.projectRoot`            | Tab missing in consumer project                                                                         |
+| Route in template ≠ `plugin.yaml` `routes[].path`                       | `validate-plugin` warning `settings-route-missing`; iframe 404                                          |
+| Missing `devOnly: true`                                                 | `settings-route-dev-only` warning; route may appear in page pickers                                     |
+| Template present but no `agentkit` handler                              | `settings-missing-agentkit-handler` warning                                                             |
+| `agent-kit/` not in `package.json` `files`                              | Template missing after `yarn add`                                                                       |
+
+**Reference implementations:**
+
+- `@jay-framework/design-system-validator` — `lib/aiditor/write-settings-contribution.ts` (walk-up resolver)
+- `@jay-framework/wix-media` — same pattern (prefer walk-up over single `..` from `dist/`)
+
+---
+
+## Settings page responsibilities
+
+The embedded settings route should:
+
+1. **About / onboarding** — what the plugin does, which `config/` files matter, links to agent-kit docs.
+2. **Run backend work** via plugin **actions** (`makeJayAction`) or **`jay-stack run <plugin>/<command>`** — not `child_process` shell.
+3. **Write project-owned generated files only** — e.g. `agent-kit/aiditor/add-menu/<plugin>.generated.yaml`, reference data under `agent-kit/references/`.
+4. **Never collect API keys or OAuth secrets** in settings forms — credentials belong in `setup` → `config/`.
+
+### Notify AIditor when Add Menu catalog changes
+
+After regenerating add-menu YAML from settings:
+
+```typescript
+window.parent.postMessage({ type: 'aiditor:addMenuCatalogChanged' }, window.location.origin);
+```
+
+### Optional — submit an agent task (explicit user click only)
+
+```typescript
+window.parent.postMessage(
+  {
+    type: 'aiditor:submitAgentTask',
+    prompt: '…',
+    context: { pageRoute: '/', renderedUrl: window.location.origin },
+  },
+  window.location.origin,
+);
+```
+
+Full iframe and discovery behavior: `agent-kit/plugin/aiditor-add-menu.md` (installed by `jay-stack setup aiditor`).
+
+---
+
+## Validation (`jay-stack validate-plugin`)
+
+When `agent-kit/aiditor/settings.template.yaml` exists, the validator:
+
+- Parses schema (`label`, `route`, optional `requires`, `pluginName`)
+- Warns if `route` is not in `plugin.yaml` `routes[]`
+- Warns if matching route lacks `devOnly: true`
+- Warns if template exists but `agentkit` is not declared
+
+Fix all **errors** before publish; treat **warnings** as required for AIditor-facing plugins.
+
+---
+
+## Verification
+
+In a project that depends on your plugin:
+
+```bash
+jay-stack agent-kit
+ls agent-kit/aiditor/settings/my-plugin.yaml   # must exist
+jay-stack validate-plugin /path/to/my-plugin     # or from package root
+```
+
+In AIditor: open **Project settings** — tab label matches `label`; iframe loads `route` with `?_jay_embed=true`. If `requires` is set, tab stays blocked until dependency `setup` reports `configured`.
+
+**Dogfood fixture:** `jay-stack setup aiditor` on a starter project with the plugin-settings-fixture local plugin (see aiditor package examples).
+
+---
+
+## AI agent quick reference
+
+When asked to "add Project settings for plugin X":
+
+1. Read this file and `plugin-routes.md` (`devOnly`).
+2. Add `agent-kit/aiditor/settings.template.yaml` + ensure `package.json` ships `agent-kit/`.
+3. Add `lib/aiditor/write-settings-contribution.ts` with **`resolvePackagedAgentKitPath`** — do not hard-code `..` depth.
+4. Wire materialization into existing `agentkit` handler; return path in `agentKitCreated`.
+5. Add `routes[]` entry with `devOnly: true` and implement settings page.
+6. Do **not** duplicate Add Menu schema here — use [add-menu-guide.md](add-menu-guide.md) for catalog items.

package/agent-kit-template/plugin/dev-server-service.md

@@ -135,3 +135,5 @@ The parent constructs the frozen page URL:
 route + '?_jay_freeze=' + id                        // full page
 route + '?_jay_freeze=' + id + '&format=fragment'   // shadow DOM fragment
 ```
+
+See also **Dev-only routes** in `plugin-routes.md` — settings pages loaded in AIditor Project settings use `_jay_embed` but are not blocked from direct URL access.

package/agent-kit-template/plugin/plugin-routes.md

@@ -45,6 +45,8 @@ A plugin route is a **headless component + jay-html template + route path**. It
 </html>
 ```
 
+**Jay-html expression rules** — plugin route templates use the same binding syntax as project pages. `if` and `{…}` resolve **tag names only**; no `.length`, method calls, or bracket indexing. For empty lists, expose `hasItems: boolean` or `itemCount: number` in ViewState / the inline `application/jay-data` block. See [jay-html-template-syntax.md](../designer/jay-html-template-syntax.md#expression-limits-important).
+
 ### 2. Create the page component
 
 ```typescript
@@ -144,3 +146,50 @@ Each plugin should choose a recognizable route prefix to avoid collisions:
 - `/cms/...` — content management
 
 There is no enforced convention — just pick a prefix that's unique and descriptive.
+
+## Dev-only routes
+
+Some plugin pages are **dev-server tooling** — internal dashboards, QA fixtures, builder settings UIs. Mark them with `devOnly: true` so consumers of `listRoutes()` can distinguish them from public site pages. Production builds do not yet exclude `devOnly` routes — that is planned for a future framework release.
+
+```yaml
+routes:
+  - path: /my-plugin/admin
+    jayHtml: ./lib/pages/admin/page.jay-html
+    component: adminPage
+    devOnly: true
+    description: Dev-server admin UI
+```
+
+### What `devOnly` does (framework)
+
+| Concern                        | Behavior                                                             |
+| ------------------------------ | -------------------------------------------------------------------- |
+| Dev server HTTP                | **Served normally** — direct URL works                               |
+| `listRoutes()` / `RouteInfo`   | Includes route with `devOnly: true`                                  |
+| Page navigation UIs            | **Consumer choice** — tools may filter `devOnly` routes from pickers |
+| Routes loaded by explicit path | **Unaffected** — embed/host tools pass a known route URL             |
+| Production build               | **Deferred** — future task excludes dev-only routes                  |
+
+### Standalone access
+
+Dev-only pages remain reachable at their URL on the dev server (new browser tab, bookmark). **This is intentional** — useful for debugging and optional standalone experiences.
+
+Plugin authors decide how to handle visitors who open the URL outside an embedding host:
+
+- **Redirect / gate** — explain the page is meant for a design tool
+- **Standalone mode** — offer the same UI with appropriate copy
+- **Hybrid** — embed in tool + "open in new tab" for power users
+
+Example: detect iframe context (`?_jay_embed=true` or `window.parent !== window`) and adjust messaging.
+
+### AIditor Project settings routes
+
+Settings tabs embed a plugin route by URL. The usual pattern:
+
+1. Ship `agent-kit/aiditor/settings.template.yaml` with `route` matching `routes[].path`
+2. Materialize to `agent-kit/aiditor/settings/<plugin>.yaml` in the **project** via the `agentkit` handler
+3. Set **`devOnly: true`** on that route entry
+
+AIditor filters `devOnly` routes from the **Pages** dropdown but loads the settings iframe by explicit path — HTTP must remain available on the dev server.
+
+Full contributor steps: [aiditor-settings-guide.md](aiditor-settings-guide.md). Runtime iframe protocol: `agent-kit/plugin/aiditor-add-menu.md` (after `jay-stack setup aiditor`).

package/agent-kit-template/plugin/setup-guide.md

@@ -254,27 +254,15 @@ export async function generateMyAgentKit(
 | Generate data from live services (product catalogs, CMS schemas)     | `agentkit` | Needs services initialized; refreshed on each agent-kit run |
 | Validate credentials / API keys                                      | `setup`    | Part of initial project configuration                       |
 | Write AIditor add-menu from project-specific data (DESIGN.md tokens) | `agentkit` | Data comes from project files at agent-kit time             |
+| Materialize AIditor Project settings tab discovery                   | `agentkit` | Copy/generate `agent-kit/aiditor/settings/<plugin>.yaml`    |
 
 ## AIditor Add-Menu Items
 
-The agent-kit handler writes to `agent-kit/aiditor/add-menu/<plugin-name>.yaml`. The AIditor discovers and loads all YAML files in this directory.
+See [add-menu-guide.md](add-menu-guide.md) for the complete add-menu item schema, interaction modes, browse sizes, presentation formats, and TypeScript types.
 
-Each item:
+## AIditor Project Settings
 
-```yaml
-items:
-  - id: my-plugin:feature-name # unique ID
-    title: Feature Name # shown in the add menu
-    category: My Plugin # grouping
-    subCategory: Components # sub-grouping
-    pluginName: my-plugin # optional: plugin attribution
-    packageName: '@my-org/my-plugin' # optional: npm package name
-    prompt: | # instructions for the AI agent
-      Use headless component @my-org/my-plugin / contract feature-name.
-      Read agent-kit/designer/feature-name.md for usage guide.
-```
-
-See `agent-kit/plugin/aiditor-add-menu.md` (installed by `jay-stack setup aiditor`) for the full contributor guide.
+See [aiditor-settings-guide.md](aiditor-settings-guide.md) for the full checklist: `settings.template.yaml` in the package, walk-up path resolution from bundled `dist/`, `devOnly` route in `plugin.yaml`, and settings page responsibilities (actions, postMessage, no secrets in forms).
 
 ## Exporting Handlers
 

package/dist/index.d.ts

@@ -1,14 +1,10 @@
 import { LogLevel } from '@jay-framework/logger';
-import { PublishMessage, PublishResponse, SaveImageMessage, SaveImageResponse, HasImageMessage, HasImageResponse, GetProjectInfoMessage, GetProjectInfoResponse, ExportMessage, ExportResponse, ImportMessage, ImportResponse, ProjectPage, Plugin } from '@jay-framework/editor-protocol';
 export { MaterializeContractsOptions, MaterializeResult, PluginContractEntry, PluginsIndex, PluginsIndexEntry, listContracts, materializeContracts } from '@jay-framework/stack-server-runtime';
 
 interface StartDevServerOptions {
     projectPath?: string;
-    /** Enable test endpoints (/_jay/health, /_jay/shutdown) */
     testMode?: boolean;
-    /** Auto-shutdown after N seconds */
     timeout?: number;
-    /** Log level for output */
     logLevel?: LogLevel;
 }
 declare function startDevServer(options?: StartDevServerOptions): Promise<void>;
@@ -21,92 +17,9 @@ interface JayConfig {
         publicFolder?: string;
         configBase?: string;
     };
-    editorServer?: {
-        portRange?: [number, number];
-        editorId?: string;
-    };
 }
 declare function loadConfig(): JayConfig;
 declare function getConfigWithDefaults(config: JayConfig): Required<JayConfig>;
 declare function updateConfig(updates: Partial<JayConfig>): void;
 
-declare function createEditorHandlers(config: Required<JayConfig>, tsConfigPath: string, projectRoot: string): {
-    onPublish: (params: PublishMessage) => Promise<PublishResponse>;
-    onSaveImage: (params: SaveImageMessage) => Promise<SaveImageResponse>;
-    onHasImage: (params: HasImageMessage) => Promise<HasImageResponse>;
-    onGetProjectInfo: (params: GetProjectInfoMessage) => Promise<GetProjectInfoResponse>;
-    onExport: <TVendorDoc>(params: ExportMessage<TVendorDoc>) => Promise<ExportResponse>;
-    onImport: <TVendorDoc_1>(params: ImportMessage<TVendorDoc_1>) => Promise<ImportResponse<TVendorDoc_1>>;
-};
-
-/**
- * Vendor Interface
- *
- * Each vendor (e.g., Figma, Sketch, Adobe XD) implements this interface
- * to provide conversion from their native format to Jay HTML format.
- */
-
-/**
- * Result of vendor conversion containing body HTML, fonts, and contract data
- */
-interface VendorConversionResult {
-    /**
-     * The body HTML content (without <html>, <head>, or <body> tags)
-     */
-    bodyHtml: string;
-    /**
-     * Set of font family names used in the document
-     */
-    fontFamilies: Set<string>;
-    /**
-     * Optional contract data for the page
-     * If provided, will be used to generate the jay-data script tag
-     */
-    contractData?: {
-        /**
-         * Contract name
-         */
-        name: string;
-        /**
-         * Contract tags in YAML format
-         */
-        tagsYaml: string;
-    };
-}
-interface Vendor<TVendorDoc = any> {
-    /**
-     * The unique identifier for this vendor (e.g., 'figma', 'sketch', 'xd')
-     */
-    vendorId: string;
-    /**
-     * Convert vendor document to body HTML with metadata
-     *
-     * @param vendorDoc - The vendor's native document format (e.g., Figma SectionNode)
-     * @param pageUrl - The page URL/route (e.g., '/home', '/products')
-     * @returns Conversion result with body HTML, fonts, and contract data
-     */
-    convertToBodyHtml(vendorDoc: TVendorDoc, pageUrl: string, projectPage: ProjectPage, plugins: Plugin[]): Promise<VendorConversionResult>;
-}
-
-/**
- * Get a vendor by ID
- *
- * @param vendorId - The vendor ID
- * @returns The vendor or undefined if not found
- */
-declare function getVendor(vendorId: string): Vendor | undefined;
-/**
- * Check if a vendor exists
- *
- * @param vendorId - The vendor ID
- * @returns True if vendor exists
- */
-declare function hasVendor(vendorId: string): boolean;
-/**
- * Get all registered vendor IDs
- *
- * @returns Array of vendor IDs
- */
-declare function getRegisteredVendors(): string[];
-
-export { type JayConfig, type StartDevServerOptions, type Vendor, createEditorHandlers, getConfigWithDefaults, getRegisteredVendors, getVendor, hasVendor, loadConfig, startDevServer, updateConfig };
+export { type JayConfig, type StartDevServerOptions, getConfigWithDefaults, loadConfig, startDevServer, updateConfig };