@contractspec/lib.contracts 0.0.0-canary-20260113162409

package/dist/docs/tech/telemetry-ingest.docblock.js

@@ -0,0 +1,156 @@
+import { registerDocBlocks } from "../registry.js";
+
+//#region src/docs/tech/telemetry-ingest.docblock.ts
+const tech_telemetry_ingest_DocBlocks = [{
+	id: "docs.tech.telemetry.ingest",
+	title: "Telemetry Ingest Endpoint",
+	summary: "Server-side telemetry ingestion for ContractSpec clients (VS Code extension, CLI, etc.).",
+	kind: "reference",
+	visibility: "internal",
+	route: "/docs/tech/telemetry/ingest",
+	tags: [
+		"telemetry",
+		"api",
+		"posthog",
+		"analytics"
+	],
+	body: `# Telemetry Ingest Endpoint
+
+The ContractSpec API provides a telemetry ingest endpoint for clients to send product analytics events.
+
+## Endpoint
+
+\`\`\`
+POST /api/telemetry/ingest
+\`\`\`
+
+## Request
+
+\`\`\`json
+{
+  "event": "contractspec.vscode.command_run",
+  "distinct_id": "client-uuid",
+  "properties": {
+    "command": "validate"
+  },
+  "timestamp": "2024-01-15T10:30:00.000Z"
+}
+\`\`\`
+
+### Headers
+
+| Header | Description |
+|--------|-------------|
+| \`x-contractspec-client-id\` | Optional client identifier (used as fallback for distinct_id) |
+| \`Content-Type\` | Must be \`application/json\` |
+
+### Body
+
+| Field | Type | Required | Description |
+|-------|------|----------|-------------|
+| \`event\` | string | Yes | Event name (e.g., \`contractspec.vscode.activated\`) |
+| \`distinct_id\` | string | Yes | Anonymous client identifier |
+| \`properties\` | object | No | Event properties |
+| \`timestamp\` | string | No | ISO 8601 timestamp |
+
+## Response
+
+\`\`\`json
+{
+  "success": true
+}
+\`\`\`
+
+## Configuration
+
+The endpoint requires \`POSTHOG_PROJECT_KEY\` environment variable to be set. If not configured, events are accepted but not forwarded.
+
+| Environment Variable | Description | Default |
+|---------------------|-------------|---------|
+| \`POSTHOG_HOST\` | PostHog host URL | \`https://eu.posthog.com\` |
+| \`POSTHOG_PROJECT_KEY\` | PostHog project API key | (required) |
+
+## Privacy
+
+- No PII is collected or stored
+- \`distinct_id\` is an anonymous client-generated UUID
+- File paths and source code are never included in events
+- Respects VS Code telemetry settings on the client side
+
+## Events
+
+### Extension Events
+
+| Event | Description | Properties |
+|-------|-------------|------------|
+| \`contractspec.vscode.activated\` | Extension activated | \`version\` |
+| \`contractspec.vscode.command_run\` | Command executed | \`command\` |
+| \`contractspec.vscode.mcp_call\` | MCP call made | \`endpoint\`, \`tool\` |
+
+### API Events
+
+| Event | Description | Properties |
+|-------|-------------|------------|
+| \`contractspec.api.mcp_request\` | MCP request processed | \`endpoint\`, \`method\`, \`success\`, \`duration_ms\` |
+`
+}, {
+	id: "docs.tech.telemetry.hybrid",
+	title: "Hybrid Telemetry Model",
+	summary: "How ContractSpec clients choose between direct PostHog and API-routed telemetry.",
+	kind: "usage",
+	visibility: "internal",
+	route: "/docs/tech/telemetry/hybrid",
+	tags: [
+		"telemetry",
+		"architecture",
+		"posthog"
+	],
+	body: `# Hybrid Telemetry Model
+
+ContractSpec uses a hybrid telemetry model where clients can send events either directly to PostHog or via the API server.
+
+## Decision Flow
+
+\`\`\`
+Is contractspec.api.baseUrl configured?
+├── Yes → Send via /api/telemetry/ingest
+└── No → Is posthogProjectKey configured?
+    ├── Yes → Send directly to PostHog
+    └── No → Telemetry disabled
+\`\`\`
+
+## Benefits
+
+### Direct PostHog
+- No server dependency
+- Works offline (with batching)
+- Lower latency
+
+### Via API
+- Centralized key management (no client-side keys)
+- Server-side enrichment and validation
+- Rate limiting and abuse prevention
+- Easier migration to other providers
+
+## Recommendation
+
+- **Development**: Use direct PostHog with a dev project key
+- **Production**: Route via API for better governance
+
+## Future: OpenTelemetry
+
+The current PostHog implementation is behind a simple interface that can be swapped for OpenTelemetry:
+
+\`\`\`typescript
+interface TelemetryClient {
+  send(event: TelemetryEvent): Promise<void>;
+}
+\`\`\`
+
+This allows future migration without changing client code.
+`
+}];
+registerDocBlocks(tech_telemetry_ingest_DocBlocks);
+
+//#endregion
+export { tech_telemetry_ingest_DocBlocks };

package/dist/docs/tech/vscode-extension.docblock.d.ts

@@ -0,0 +1,6 @@
+import { DocBlock } from "@contractspec/lib.contracts/docs";
+
+//#region src/docs/tech/vscode-extension.docblock.d.ts
+declare const tech_vscode_extension_DocBlocks: DocBlock[];
+//#endregion
+export { tech_vscode_extension_DocBlocks };

package/dist/docs/tech/vscode-extension.docblock.js

@@ -0,0 +1,102 @@
+import { registerDocBlocks } from "../registry.js";
+
+//#region src/docs/tech/vscode-extension.docblock.ts
+const tech_vscode_extension_DocBlocks = [{
+	id: "docs.tech.vscode.extension",
+	title: "ContractSpec VS Code Extension",
+	summary: "VS Code extension for spec-first development with validation, scaffolding, and MCP integration.",
+	kind: "reference",
+	visibility: "public",
+	route: "/docs/tech/vscode/extension",
+	tags: [
+		"vscode",
+		"extension",
+		"tooling",
+		"dx"
+	],
+	body: `# ContractSpec VS Code Extension
+
+The ContractSpec VS Code extension provides spec-first development tooling directly in your editor.
+
+## Features
+
+- **Real-time Validation**: Get instant feedback on spec errors and warnings as you save files
+- **Build/Scaffold**: Generate handler and component skeletons from specs (no AI required)
+- **Spec Explorer**: List and navigate all specs in your workspace
+- **Dependency Analysis**: Visualize spec dependencies and detect cycles
+- **MCP Integration**: Search ContractSpec documentation via Model Context Protocol
+- **Snippets**: Code snippets for common ContractSpec patterns
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| \`ContractSpec: Validate Current Spec\` | Validate the currently open spec file |
+| \`ContractSpec: Validate All Specs\` | Validate all spec files in the workspace |
+| \`ContractSpec: Build/Scaffold\` | Generate handler/component from the current spec |
+| \`ContractSpec: List All Specs\` | Show all specs in the workspace |
+| \`ContractSpec: Analyze Dependencies\` | Analyze and visualize spec dependencies |
+| \`ContractSpec: Search Docs (MCP)\` | Search documentation via MCP |
+
+## Configuration
+
+| Setting | Description | Default |
+|---------|-------------|---------|
+| \`contractspec.api.baseUrl\` | Base URL for ContractSpec API (enables MCP + remote telemetry) | \`""\` |
+| \`contractspec.telemetry.posthogHost\` | PostHog host URL for direct telemetry | \`"https://eu.posthog.com"\` |
+| \`contractspec.telemetry.posthogProjectKey\` | PostHog project key for direct telemetry | \`""\` |
+| \`contractspec.validation.onSave\` | Run validation on save | \`true\` |
+| \`contractspec.validation.onOpen\` | Run validation on open | \`true\` |
+
+## Architecture
+
+The extension uses:
+- \`@contractspec/module.workspace\` for pure analysis + templates
+- \`@contractspec/bundle.workspace\` for workspace services + adapters
+
+This allows the extension to work without requiring the CLI to be installed.
+
+## Telemetry
+
+The extension uses a hybrid telemetry approach:
+1. If \`contractspec.api.baseUrl\` is configured → send to API \`/api/telemetry/ingest\`
+2. Otherwise → send directly to PostHog (if project key configured)
+
+Telemetry respects VS Code's telemetry settings. No file paths, source code, or PII is collected.
+`
+}, {
+	id: "docs.tech.vscode.snippets",
+	title: "ContractSpec Snippets",
+	summary: "Code snippets for common ContractSpec patterns in VS Code.",
+	kind: "reference",
+	visibility: "public",
+	route: "/docs/tech/vscode/snippets",
+	tags: [
+		"vscode",
+		"snippets",
+		"dx"
+	],
+	body: `# ContractSpec Snippets
+
+The VS Code extension includes snippets for common ContractSpec patterns.
+
+## Available Snippets
+
+| Prefix | Description |
+|--------|-------------|
+| \`contractspec-command\` | Create a new command (write operation) |
+| \`contractspec-query\` | Create a new query (read-only operation) |
+| \`contractspec-event\` | Create a new event |
+| \`contractspec-docblock\` | Create a new DocBlock |
+| \`contractspec-telemetry\` | Create a new TelemetrySpec |
+| \`contractspec-presentation\` | Create a new Presentation |
+
+## Usage
+
+Type the prefix in a TypeScript file and press Tab to expand the snippet. Tab through the placeholders to fill in your values.
+`
+}];
+registerDocBlocks(tech_vscode_extension_DocBlocks);
+
+//#endregion
+export { tech_vscode_extension_DocBlocks };

package/dist/docs/tech-contracts.docs.d.ts

@@ -0,0 +1,6 @@
+import { DocBlock } from "./types.js";
+
+//#region src/docs/tech-contracts.docs.d.ts
+declare const techContractsDocs: DocBlock[];
+//#endregion
+export { techContractsDocs };

package/dist/docs/tech-contracts.docs.js

@@ -0,0 +1,96 @@
+import { registerDocBlocks } from "./registry.js";
+
+//#region src/docs/tech-contracts.docs.ts
+const techContractsDocs = [{
+	id: "docs.tech.contracts.presentations",
+	title: "Presentations — Unified Descriptor & Transform Engine",
+	summary: "How PresentationSpec and TransformEngine keep docs/renderers consistent.",
+	visibility: "public",
+	route: "/docs/tech/contracts/presentations",
+	kind: "reference",
+	tags: [
+		"presentations",
+		"docs",
+		"mcp"
+	],
+	body: `## Presentations V2 — Unified Descriptor & Transform Engine
+
+### Purpose
+
+Unify presentations into one descriptor (\`PresentationSpec\`) that declares a single source (React component key or BlockNote doc) and a list of output targets (react, markdown, application/json, application/xml). A pluggable \`TransformEngine\` renders any target and applies PII redaction.
+
+### Types
+
+\`\`\`ts
+type PresentationTarget =
+  | 'react'
+  | 'markdown'
+  | 'application/json'
+  | 'application/xml';
+
+type PresentationSource =
+  | {
+      type: 'component';
+      framework: 'react';
+      componentKey: string;
+      props?: AnySchemaModel;
+    }
+  | { type: 'blocknotejs'; docJson: unknown; blockConfig?: unknown };
+
+interface PresentationSpec {
+  meta: PresentationMeta; // includes partial OwnerShipMeta + description
+  policy?: { flags?: string[]; pii?: string[] };
+  source: PresentationSource;
+  targets: PresentationTarget[];
+}
+
+// Shared ownership schema (source of truth in @contractspec/lib.contracts/src/ownership.ts)
+interface OwnerShipMeta {
+  title: string;
+  description: string;
+  domain: string;
+  owners: Owner[];
+  tags: Tag[];
+  stability: Stability;
+}
+
+type Stability = 'experimental' | 'beta' | 'stable' | 'deprecated';
+type Owner = string; // curated list available in code (e.g., '@sigil-team', 'team-strit')
+type Tag = string; // curated list available in code (e.g., 'auth', 'spots')
+
+// For presentations, meta is a Partial<OwnerShipMeta> plus description, name, version
+interface PresentationMeta extends Partial<OwnerShipMeta> {
+  name: string;
+  version: string;
+  description?: string;
+}
+\`\`\`
+
+### Engine
+
+Use \`createDefaultTransformEngine()\` and register custom renderers as needed (e.g., high-fidelity BlockNote → Markdown). The default engine supports markdown/json/xml; a React renderer returns a serializable descriptor the host app renders via a \`componentMap\` or a BlockNote renderer. The canonical source type string is \`blocknotejs\` (not \`blocknote\`).
+
+PII paths (JSON-like) are redacted from rendered outputs.
+
+### MCP Integration
+
+\`createMcpServer\` accepts \`presentationsV2\`. Each descriptor is exposed under \`presentation://<name>/v<version>\` and negotiated variants (\`.md/.json/.xml\`) are rendered by the engine.
+
+### Migration
+
+- V1 \`PresentationSpec\` remains supported; a back-compat helper converts V1 → V2 when convenient.
+- Prefer V2 for new work.
+
+### Examples (Sigil)
+
+- \`sigil.auth.webauth_tabs_v2\`: component source (\`componentKey: 'sigil.webauth.tabs'\`), targets \`react/json/xml\`.
+- \`sigil.signup.guide_v2\`: BlockNote doc source, targets \`react/markdown/json/xml\`.
+
+### React Rendering
+
+Host apps use a \`componentMap\` (e.g., \`'sigil.webauth.tabs' → WebAuthTabs\`) and a BlockNote renderer to turn the React render descriptor into elements.`
+}];
+registerDocBlocks(techContractsDocs);
+
+//#endregion
+export { techContractsDocs };

package/dist/docs/types.d.ts

@@ -0,0 +1,41 @@
+import { Stability } from "../ownership.js";
+
+//#region src/docs/types.d.ts
+type DocVisibility = 'public' | 'internal' | 'mixed';
+interface DocBlockLink {
+  label: string;
+  href: string;
+}
+type DocKind = 'goal' | 'how' | 'usage' | 'reference' | 'faq' | 'changelog';
+interface DocBlock {
+  /** Globally unique identifier (prefer dotted paths like docs.ops.runbook). */
+  id: string;
+  /** Short, human-readable title. */
+  title: string;
+  /** Markdown body (LLM- and human-readable). */
+  body: string;
+  /** Optional one-line summary used for meta.description. */
+  summary?: string;
+  /** Explicit route (e.g., /docs/ops/anomaly-detection). Falls back to id-derived route. */
+  route?: string;
+  /** Optional semantic grouping for filtering. */
+  kind?: DocKind;
+  /** Visibility gate. Defaults to public. */
+  visibility?: DocVisibility;
+  /** Optional version to allow evolutions without breaking links. Defaults to 1. */
+  version?: string;
+  /** Tags to aid discovery and filtering. */
+  tags?: string[];
+  /** Owning teams or individuals. */
+  owners?: string[];
+  /** Related contract/presentation identifiers. */
+  relatedSpecs?: string[];
+  /** External references or supporting links. */
+  links?: DocBlockLink[];
+  /** Domain or bounded context marker. */
+  domain?: string;
+  /** Stability marker to mirror presentation ownership semantics. */
+  stability?: Stability;
+}
+//#endregion
+export { DocBlock, DocBlockLink, DocKind, DocVisibility };

package/dist/events.d.ts

@@ -0,0 +1,47 @@
+import { DocId } from "./docs/registry.js";
+import { OwnerShipMeta } from "./ownership.js";
+import { SpecContractRegistry } from "./registry.js";
+import { AnySchemaModel } from "@contractspec/lib.schema";
+
+//#region src/events.d.ts
+interface EventSpecMeta extends Omit<OwnerShipMeta, 'docId'> {
+  /** Doc block(s) for this operation. */
+  docId?: DocId[];
+}
+/**
+ * Typed event specification. Declare once, validate payloads at publish time,
+ * and guard emissions via the contracts runtime.
+ */
+interface EventSpec<T extends AnySchemaModel> {
+  meta: EventSpecMeta;
+  /** JSON-like paths to redact from logs/exports. */
+  pii?: string[];
+  /** Event payload schema from @contractspec/lib.schema. */
+  payload: T;
+}
+type AnyEventSpec<T extends AnySchemaModel = AnySchemaModel> = EventSpec<T>;
+/** Identity function to keep type inference when declaring events. */
+declare function defineEvent<T extends AnySchemaModel>(e: EventSpec<T>): EventSpec<T>;
+interface EventEnvelope<T> {
+  /** Unique identifier for the published event (UUID recommended). */
+  id: string;
+  /** ISO timestamp when the event occurred. */
+  occurredAt: string;
+  /** Optional trace identifier for correlating across services. */
+  traceId?: string;
+  /** Event name as published (should match spec.name). */
+  key: string;
+  /** Event version as published (should match spec.version). */
+  version: string;
+  /** Validated payload. */
+  payload: T;
+}
+type EventKey = `${string}.v${string}`;
+/** Build a stable string key for an event name/version pair. */
+declare const eventKey: (key: string, version: string) => EventKey;
+/** In-memory registry for EventSpec. */
+declare class EventRegistry extends SpecContractRegistry<'event', AnyEventSpec> {
+  constructor(items?: AnyEventSpec[]);
+}
+//#endregion
+export { AnyEventSpec, EventEnvelope, EventKey, EventRegistry, EventSpec, EventSpecMeta, defineEvent, eventKey };

package/dist/events.js

@@ -0,0 +1,19 @@
+import { SpecContractRegistry } from "./registry.js";
+import "@contractspec/lib.schema";
+
+//#region src/events.ts
+/** Identity function to keep type inference when declaring events. */
+function defineEvent(e) {
+	return e;
+}
+/** Build a stable string key for an event name/version pair. */
+const eventKey = (key, version) => `${key}.v${version}`;
+/** In-memory registry for EventSpec. */
+var EventRegistry = class extends SpecContractRegistry {
+	constructor(items) {
+		super("event", items);
+	}
+};
+
+//#endregion
+export { EventRegistry, defineEvent, eventKey };

package/dist/examples/docs/examples.docblock.d.ts

@@ -0,0 +1,6 @@
+import { DocBlock } from "@contractspec/lib.contracts/docs";
+
+//#region src/examples/docs/examples.docblock.d.ts
+declare const tech_contracts_examples_DocBlocks: DocBlock[];
+//#endregion
+export { tech_contracts_examples_DocBlocks };

package/dist/examples/docs/examples.docblock.js

@@ -0,0 +1,165 @@
+import { registerDocBlocks } from "../../docs/registry.js";
+
+//#region src/examples/docs/examples.docblock.ts
+const tech_contracts_examples_DocBlocks = [{
+	id: "docs.tech.contracts.examples",
+	title: "Example Specifications",
+	summary: "ExampleSpec defines complete, demonstrable ContractSpec applications.",
+	kind: "reference",
+	visibility: "public",
+	route: "/docs/tech/contracts/examples",
+	tags: [
+		"tech",
+		"contracts",
+		"examples",
+		"templates"
+	],
+	body: `## Example Specifications
+
+ExampleSpec is a contract for defining complete, demonstrable ContractSpec applications. Examples integrate with AppBlueprintSpec and FeatureModuleSpec to provide a full application specification.
+
+### Overview
+
+An \`ExampleSpec\` captures:
+- **Metadata** (via \`ExampleMeta\` extending \`OwnerShipMeta\`): key, version, title, description, ownership, tags, stability
+- **Example-specific fields**: kind, visibility, summary
+- **Surfaces**: where the example can be used (templates, sandbox, studio, MCP)
+- **Entrypoints**: package exports mapping
+- **Blueprint**: optional AppBlueprintSpec or reference
+- **Features**: optional FeatureModuleSpec array or references
+
+### Usage
+
+\`\`\`typescript
+import type { ExampleSpec } from '@contractspec/lib.contracts';
+import { ExampleRegistry, validateExample } from '@contractspec/lib.contracts';
+
+const example: ExampleSpec = {
+  meta: {
+    key: 'saas-boilerplate',
+    version: '1.0.0',
+    title: 'SaaS Boilerplate',
+    description: 'Multi-tenant SaaS foundation with billing and RBAC.',
+    kind: 'template',
+    visibility: 'public',
+    stability: 'experimental',
+    owners: ['@saas-team'],
+    tags: ['saas', 'multi-tenant', 'billing'],
+    summary: 'Complete SaaS starter.',
+  },
+  surfaces: {
+    templates: true,
+    sandbox: { enabled: true, modes: ['playground', 'specs', 'builder'] },
+    studio: { enabled: true, installable: true },
+    mcp: { enabled: true },
+  },
+  entrypoints: {
+    packageName: '@contractspec/example.saas-boilerplate',
+    feature: './saas-boilerplate.feature',
+    contracts: './contracts',
+  },
+  features: [SaasBoilerplateFeature],
+};
+\`\`\`
+
+### ExampleRegistry
+
+Use \`ExampleRegistry\` to manage examples:
+
+\`\`\`typescript
+const registry = new ExampleRegistry();
+registry.register(example);
+
+// Query examples
+registry.listByKind('template');
+registry.listByVisibility('public');
+registry.listBySurface('studio');
+registry.listInstallable();
+registry.search('billing');
+\`\`\`
+
+### ExampleMeta
+
+\`ExampleMeta\` extends \`OwnerShipMeta\` with example-specific fields:
+
+| Field | Type | Description |
+|-------|------|-------------|
+| key | string | Unique identifier |
+| version | number | Spec version |
+| title | string? | Human-readable title |
+| description | string | Technical description |
+| kind | ExampleKind | template, workflow, integration, etc. |
+| visibility | ExampleVisibility | public, internal, experimental |
+| stability | Stability | idea, experimental, beta, stable, deprecated |
+| owners | string[] | Owner identifiers |
+| tags | string[] | Discovery tags |
+| summary | string? | Marketing summary |
+
+### ExampleKind
+
+| Kind | Use Case |
+|------|----------|
+| template | Full application template |
+| workflow | Workflow automation example |
+| integration | Integration showcase |
+| knowledge | Knowledge base example |
+| blueprint | App blueprint example |
+| ui | UI component showcase |
+| script | CLI/script example |
+| library | Library/SDK example |
+
+### Surfaces
+
+| Surface | Purpose |
+|---------|---------|
+| templates | Available as new project template |
+| sandbox | Interactive playground support |
+| studio | ContractSpec Studio support |
+| mcp | Model Context Protocol support |
+
+### Validation
+
+\`\`\`typescript
+import { validateExample, validateExamples } from '@contractspec/lib.contracts';
+
+const result = validateExample(example);
+if (!result.valid) {
+  console.error(result.errors);
+}
+
+// Batch validation with duplicate detection
+const batchResult = validateExamples([example1, example2]);
+\`\`\`
+
+### Integration with Blueprints and Features
+
+Examples can reference or embed blueprints and features:
+
+\`\`\`typescript
+const example: ExampleSpec = {
+  // ... meta, surfaces, entrypoints
+  
+  // Inline blueprint
+  blueprint: myAppBlueprint,
+  
+  // Or reference by pointer
+  blueprint: { key: 'core.app', version: '1.0.0' },
+  
+  // Inline features
+  features: [MyFeature],
+  
+  // Or reference
+  features: [{ key: 'my-feature' }],
+};
+\`\`\`
+
+### Related
+
+- [App Configuration](file:///docs/tech/contracts/app-config) - AppBlueprintSpec
+- [Features](file:///docs/tech/contracts/features) - FeatureModuleSpec
+`
+}];
+registerDocBlocks(tech_contracts_examples_DocBlocks);
+
+//#endregion
+export { tech_contracts_examples_DocBlocks };

package/dist/examples/index.d.ts

@@ -0,0 +1,13 @@
+import { ExampleDocumentation, ExampleEntrypoints, ExampleKind, ExampleKindEnum, ExampleMcpSupport, ExampleMeta, ExampleSandboxMode, ExampleSandboxModeEnum, ExampleSandboxSupport, ExampleSpec, ExampleStudioSupport, ExampleSurfaces, ExampleVisibility, ExampleVisibilityEnum, isExampleKind, isExampleVisibility, isFeatureRef, isSpecPointer } from "./types.js";
+import { ExampleDocumentationSchema, ExampleEntrypointsSchema, ExampleKindSchema, ExampleMetaSchema, ExampleSandboxModeSchema, ExampleSpecSchema, ExampleSurfacesSchema, ExampleVisibilitySchema, parseExampleDocumentation, parseExampleEntrypoints, parseExampleMeta, parseExampleSpec, parseExampleSurfaces, safeParseExampleSpec } from "./schema.js";
+import { ExampleRegistry } from "./registry.js";
+import { CrossValidationContext, ExampleValidationError, ExampleValidationWarning, ValidateExampleResult, ValidateExamplesResult, validateExample, validateExampleReferences, validateExamples } from "./validation.js";
+
+//#region src/examples/index.d.ts
+
+/**
+ * Helper to define an Example.
+ */
+declare const defineExample: (spec: ExampleSpec) => ExampleSpec;
+//#endregion
+export { type CrossValidationContext, type ExampleDocumentation, ExampleDocumentationSchema, type ExampleEntrypoints, ExampleEntrypointsSchema, type ExampleKind, ExampleKindEnum, ExampleKindSchema, type ExampleMcpSupport, type ExampleMeta, ExampleMetaSchema, ExampleRegistry, type ExampleSandboxMode, ExampleSandboxModeEnum, ExampleSandboxModeSchema, type ExampleSandboxSupport, type ExampleSpec, ExampleSpecSchema, type ExampleStudioSupport, type ExampleSurfaces, ExampleSurfacesSchema, type ExampleValidationError, type ExampleValidationWarning, type ExampleVisibility, ExampleVisibilityEnum, ExampleVisibilitySchema, type ValidateExampleResult, type ValidateExamplesResult, defineExample, isExampleKind, isExampleVisibility, isFeatureRef, isSpecPointer, parseExampleDocumentation, parseExampleEntrypoints, parseExampleMeta, parseExampleSpec, parseExampleSurfaces, safeParseExampleSpec, validateExample, validateExampleReferences, validateExamples };

package/dist/examples/index.js

@@ -0,0 +1,13 @@
+import { ExampleKindEnum, ExampleSandboxModeEnum, ExampleVisibilityEnum, isExampleKind, isExampleVisibility, isFeatureRef, isSpecPointer } from "./types.js";
+import { ExampleDocumentationSchema, ExampleEntrypointsSchema, ExampleKindSchema, ExampleMetaSchema, ExampleSandboxModeSchema, ExampleSpecSchema, ExampleSurfacesSchema, ExampleVisibilitySchema, parseExampleDocumentation, parseExampleEntrypoints, parseExampleMeta, parseExampleSpec, parseExampleSurfaces, safeParseExampleSpec } from "./schema.js";
+import { ExampleRegistry } from "./registry.js";
+import { validateExample, validateExampleReferences, validateExamples } from "./validation.js";
+
+//#region src/examples/index.ts
+/**
+* Helper to define an Example.
+*/
+const defineExample = (spec) => spec;
+
+//#endregion
+export { ExampleDocumentationSchema, ExampleEntrypointsSchema, ExampleKindEnum, ExampleKindSchema, ExampleMetaSchema, ExampleRegistry, ExampleSandboxModeEnum, ExampleSandboxModeSchema, ExampleSpecSchema, ExampleSurfacesSchema, ExampleVisibilityEnum, ExampleVisibilitySchema, defineExample, isExampleKind, isExampleVisibility, isFeatureRef, isSpecPointer, parseExampleDocumentation, parseExampleEntrypoints, parseExampleMeta, parseExampleSpec, parseExampleSurfaces, safeParseExampleSpec, validateExample, validateExampleReferences, validateExamples };