@contractspec/bundle.workspace 1.57.0 → 1.58.0

package/dist/ai/index.mjs

@@ -1,10 +0,0 @@
-import { getAIProvider } from "./providers.mjs";
-import { SimpleAgent } from "./agents/simple-agent.mjs";
-import { CursorAgent } from "./agents/cursor-agent.mjs";
-import { ClaudeCodeAgent } from "./agents/claude-code-agent.mjs";
-import { OpenAICodexAgent } from "./agents/openai-codex-agent.mjs";
-import { AgentOrchestrator } from "./agents/orchestrator.mjs";
-import "./agents/index.mjs";
-import { prompts_exports } from "./prompts/index.mjs";
-
-export {  };

package/dist/ai/prompts/code-generation.d.mts

@@ -1,26 +0,0 @@
-declare namespace code_generation_d_exports {
-  export { buildComponentPrompt, buildFormPrompt, buildHandlerPrompt, buildTestPrompt, getCodeGenSystemPrompt };
-}
-/**
- * Build prompt for generating handler implementation
- */
-declare function buildHandlerPrompt(specCode: string): string;
-/**
- * Build prompt for generating React component from presentation spec
- */
-declare function buildComponentPrompt(specCode: string): string;
-/**
- * Build prompt for generating form component
- */
-declare function buildFormPrompt(specCode: string): string;
-/**
- * Build prompt for generating tests
- */
-declare function buildTestPrompt(specCode: string, implementationCode: string, testType: 'handler' | 'component'): string;
-/**
- * System prompt for code generation
- */
-declare function getCodeGenSystemPrompt(): string;
-//#endregion
-export { code_generation_d_exports };
-//# sourceMappingURL=code-generation.d.mts.map

package/dist/ai/prompts/code-generation.d.mts.map

@@ -1 +0,0 @@
-{"version":3,"file":"code-generation.d.mts","names":[],"sources":["../../../src/ai/prompts/code-generation.ts"],"mappings":";;;;;;iBAGgB,kBAAA,CAAmB,QAAA;;;;iBA0BnB,oBAAA,CAAqB,QAAA;;;AA1BrC;iBAoDgB,eAAA,CAAgB,QAAA;;;;iBA2BhB,eAAA,CACd,QAAA,UACA,kBAAA,UACA,QAAA;;;;iBAwCc,sBAAA,CAAA"}

package/dist/ai/prompts/code-generation.mjs

@@ -1,143 +0,0 @@
-import { __exportAll } from "../../_virtual/_rolldown/runtime.mjs";
-
-//#region src/ai/prompts/code-generation.ts
-var code_generation_exports = /* @__PURE__ */ __exportAll({
-	buildComponentPrompt: () => buildComponentPrompt,
-	buildFormPrompt: () => buildFormPrompt,
-	buildHandlerPrompt: () => buildHandlerPrompt,
-	buildTestPrompt: () => buildTestPrompt,
-	getCodeGenSystemPrompt: () => getCodeGenSystemPrompt
-});
-/**
-* Build prompt for generating handler implementation
-*/
-function buildHandlerPrompt(specCode) {
-	return `You are a senior TypeScript developer implementing a handler for a contract specification.
-
-Here is the contract spec:
-
-\`\`\`typescript
-${specCode}
-\`\`\`
-
-Generate a complete handler implementation that:
-
-1. **Matches the spec signature**: Input/output types from the spec
-2. **Handles errors**: Implement error cases defined in spec.io.errors
-3. **Emits events**: Use the events declared in spec.sideEffects.emits
-4. **Validates input**: Use zod validation from the schema
-5. **Follows best practices**: Clean, type-safe TypeScript
-6. **Includes comments**: Explain business logic
-
-The handler should be production-ready with proper error handling, logging points, and clear structure.
-
-Return only the TypeScript code for the handler function.`;
-}
-/**
-* Build prompt for generating React component from presentation spec
-*/
-function buildComponentPrompt(specCode) {
-	return `You are a senior React developer creating a component for a presentation specification.
-
-Here is the presentation spec:
-
-\`\`\`typescript
-${specCode}
-\`\`\`
-
-Generate a complete React component that:
-
-1. **Props interface**: Typed props from the spec
-2. **Accessibility**: Proper ARIA labels, roles, keyboard navigation
-3. **Mobile-first**: Optimized for small screens and touch
-4. **Clean UI**: Simple, intuitive interface
-5. **Type-safe**: Full TypeScript with no 'any' types
-6. **Best practices**: React hooks, proper state management
-
-The component should follow Atomic Design principles and be reusable.
-
-Return only the TypeScript/TSX code for the component.`;
-}
-/**
-* Build prompt for generating form component
-*/
-function buildFormPrompt(specCode) {
-	return `You are a senior React developer creating a form component from a form specification.
-
-Here is the form spec:
-
-\`\`\`typescript
-${specCode}
-\`\`\`
-
-Generate a complete form component using react-hook-form that:
-
-1. **Form validation**: Use zod schema for validation
-2. **Field types**: Proper inputs for each field type
-3. **Conditional logic**: Support visibleWhen, enabledWhen, requiredWhen predicates
-4. **Error handling**: Clear, user-friendly error messages
-5. **Accessibility**: Labels, hints, ARIA attributes
-6. **Mobile-optimized**: Touch-friendly, appropriate input types
-7. **Type-safe**: Full TypeScript
-
-The form should provide excellent UX with real-time validation and helpful feedback.
-
-Return only the TypeScript/TSX code for the form component.`;
-}
-/**
-* Build prompt for generating tests
-*/
-function buildTestPrompt(specCode, implementationCode, testType) {
-	return `You are a senior developer writing comprehensive tests.
-
-Spec:
-\`\`\`typescript
-${specCode}
-\`\`\`
-
-Implementation:
-\`\`\`typescript
-${implementationCode}
-\`\`\`
-
-Generate complete test suite using Vitest that:
-${testType === "handler" ? `
-  - Test all acceptance scenarios from the spec
-  - Test error cases defined in spec.io.errors
-  - Verify events are emitted correctly
-  - Test input validation
-  - Test happy path and edge cases` : `
-  - Test rendering with various props
-  - Test user interactions
-  - Test accessibility (a11y)
-  - Test responsive behavior
-  - Test error states`}
-
-Use clear test descriptions and follow AAA pattern (Arrange, Act, Assert).
-
-Return only the TypeScript test code.`;
-}
-/**
-* System prompt for code generation
-*/
-function getCodeGenSystemPrompt() {
-	return `You are an expert TypeScript developer with deep knowledge of:
-- Type-safe API design
-- React and modern hooks
-- Test-driven development
-- Accessibility best practices
-- Clean code principles
-
-Generate production-ready code that is:
-- Fully typed (no 'any' or type assertions unless absolutely necessary)
-- Well-documented with TSDoc comments
-- Following project conventions
-- Defensive and error-safe
-- Easy to maintain and extend
-
-Always prioritize code quality, safety, and user experience.`;
-}
-
-//#endregion
-export { buildComponentPrompt, buildFormPrompt, buildHandlerPrompt, buildTestPrompt, code_generation_exports, getCodeGenSystemPrompt };
-//# sourceMappingURL=code-generation.mjs.map

package/dist/ai/prompts/code-generation.mjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"code-generation.mjs","names":[],"sources":["../../../src/ai/prompts/code-generation.ts"],"sourcesContent":["/**\n * Build prompt for generating handler implementation\n */\nexport function buildHandlerPrompt(specCode: string): string {\n  return `You are a senior TypeScript developer implementing a handler for a contract specification.\n\nHere is the contract spec:\n\n\\`\\`\\`typescript\n${specCode}\n\\`\\`\\`\n\nGenerate a complete handler implementation that:\n\n1. **Matches the spec signature**: Input/output types from the spec\n2. **Handles errors**: Implement error cases defined in spec.io.errors\n3. **Emits events**: Use the events declared in spec.sideEffects.emits\n4. **Validates input**: Use zod validation from the schema\n5. **Follows best practices**: Clean, type-safe TypeScript\n6. **Includes comments**: Explain business logic\n\nThe handler should be production-ready with proper error handling, logging points, and clear structure.\n\nReturn only the TypeScript code for the handler function.`;\n}\n\n/**\n * Build prompt for generating React component from presentation spec\n */\nexport function buildComponentPrompt(specCode: string): string {\n  return `You are a senior React developer creating a component for a presentation specification.\n\nHere is the presentation spec:\n\n\\`\\`\\`typescript\n${specCode}\n\\`\\`\\`\n\nGenerate a complete React component that:\n\n1. **Props interface**: Typed props from the spec\n2. **Accessibility**: Proper ARIA labels, roles, keyboard navigation\n3. **Mobile-first**: Optimized for small screens and touch\n4. **Clean UI**: Simple, intuitive interface\n5. **Type-safe**: Full TypeScript with no 'any' types\n6. **Best practices**: React hooks, proper state management\n\nThe component should follow Atomic Design principles and be reusable.\n\nReturn only the TypeScript/TSX code for the component.`;\n}\n\n/**\n * Build prompt for generating form component\n */\nexport function buildFormPrompt(specCode: string): string {\n  return `You are a senior React developer creating a form component from a form specification.\n\nHere is the form spec:\n\n\\`\\`\\`typescript\n${specCode}\n\\`\\`\\`\n\nGenerate a complete form component using react-hook-form that:\n\n1. **Form validation**: Use zod schema for validation\n2. **Field types**: Proper inputs for each field type\n3. **Conditional logic**: Support visibleWhen, enabledWhen, requiredWhen predicates\n4. **Error handling**: Clear, user-friendly error messages\n5. **Accessibility**: Labels, hints, ARIA attributes\n6. **Mobile-optimized**: Touch-friendly, appropriate input types\n7. **Type-safe**: Full TypeScript\n\nThe form should provide excellent UX with real-time validation and helpful feedback.\n\nReturn only the TypeScript/TSX code for the form component.`;\n}\n\n/**\n * Build prompt for generating tests\n */\nexport function buildTestPrompt(\n  specCode: string,\n  implementationCode: string,\n  testType: 'handler' | 'component'\n): string {\n  const testFocus =\n    testType === 'handler'\n      ? `\n  - Test all acceptance scenarios from the spec\n  - Test error cases defined in spec.io.errors\n  - Verify events are emitted correctly\n  - Test input validation\n  - Test happy path and edge cases`\n      : `\n  - Test rendering with various props\n  - Test user interactions\n  - Test accessibility (a11y)\n  - Test responsive behavior\n  - Test error states`;\n\n  return `You are a senior developer writing comprehensive tests.\n\nSpec:\n\\`\\`\\`typescript\n${specCode}\n\\`\\`\\`\n\nImplementation:\n\\`\\`\\`typescript\n${implementationCode}\n\\`\\`\\`\n\nGenerate complete test suite using Vitest that:\n${testFocus}\n\nUse clear test descriptions and follow AAA pattern (Arrange, Act, Assert).\n\nReturn only the TypeScript test code.`;\n}\n\n/**\n * System prompt for code generation\n */\nexport function getCodeGenSystemPrompt(): string {\n  return `You are an expert TypeScript developer with deep knowledge of:\n- Type-safe API design\n- React and modern hooks\n- Test-driven development\n- Accessibility best practices\n- Clean code principles\n\nGenerate production-ready code that is:\n- Fully typed (no 'any' or type assertions unless absolutely necessary)\n- Well-documented with TSDoc comments\n- Following project conventions\n- Defensive and error-safe\n- Easy to maintain and extend\n\nAlways prioritize code quality, safety, and user experience.`;\n}\n"],"mappings":";;;;;;;;;;;;;AAGA,SAAgB,mBAAmB,UAA0B;AAC3D,QAAO;;;;;EAKP,SAAS;;;;;;;;;;;;;;;;;;;AAoBX,SAAgB,qBAAqB,UAA0B;AAC7D,QAAO;;;;;EAKP,SAAS;;;;;;;;;;;;;;;;;;;AAoBX,SAAgB,gBAAgB,UAA0B;AACxD,QAAO;;;;;EAKP,SAAS;;;;;;;;;;;;;;;;;;;;AAqBX,SAAgB,gBACd,UACA,oBACA,UACQ;AAgBR,QAAO;;;;EAIP,SAAS;;;;;EAKT,mBAAmB;;;;EAvBjB,aAAa,YACT;;;;;sCAMA;;;;;uBAoBI;;;;;;;;;AAUZ,SAAgB,yBAAiC;AAC/C,QAAO"}

package/dist/ai/prompts/index.d.mts

@@ -1,10 +0,0 @@
-import { code_generation_d_exports } from "./code-generation.mjs";
-import { spec_creation_d_exports } from "./spec-creation.mjs";
-
-//#region src/ai/prompts/index.d.ts
-declare namespace index_d_exports {
-  export { code_generation_d_exports as codeGeneration, spec_creation_d_exports as specCreation };
-}
-//#endregion
-export { index_d_exports };
-//# sourceMappingURL=index.d.mts.map

package/dist/ai/prompts/index.d.mts.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.d.mts","names":[],"sources":["../../../src/ai/prompts/index.ts"],"mappings":""}

package/dist/ai/prompts/index.mjs

@@ -1,13 +0,0 @@
-import { __exportAll } from "../../_virtual/_rolldown/runtime.mjs";
-import { code_generation_exports } from "./code-generation.mjs";
-import { spec_creation_exports } from "./spec-creation.mjs";
-
-//#region src/ai/prompts/index.ts
-var prompts_exports = /* @__PURE__ */ __exportAll({
-	codeGeneration: () => code_generation_exports,
-	specCreation: () => spec_creation_exports
-});
-
-//#endregion
-export { prompts_exports };
-//# sourceMappingURL=index.mjs.map

package/dist/ai/prompts/index.mjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.mjs","names":[],"sources":["../../../src/ai/prompts/index.ts"],"sourcesContent":["/**\n * AI prompts for ContractSpec.\n */\n\nexport * as codeGeneration from './code-generation';\nexport * as specCreation from './spec-creation';\n"],"mappings":""}

package/dist/ai/prompts/spec-creation.d.mts

@@ -1,29 +0,0 @@
-import { OpKind, PresentationKind } from "../../types.mjs";
-
-//#region src/ai/prompts/spec-creation.d.ts
-declare namespace spec_creation_d_exports {
-  export { addExampleContext, buildEventSpecPrompt, buildOperationSpecPrompt, buildPresentationSpecPrompt, getSystemPrompt };
-}
-/**
- * Build prompt for creating operation spec from description
- */
-declare function buildOperationSpecPrompt(description: string, kind: OpKind): string;
-/**
- * Build prompt for creating event spec from description
- */
-declare function buildEventSpecPrompt(description: string): string;
-/**
- * Build prompt for creating presentation spec from description
- */
-declare function buildPresentationSpecPrompt(description: string, kind: PresentationKind): string;
-/**
- * Build system prompt for all spec generation
- */
-declare function getSystemPrompt(): string;
-/**
- * Create example-based prompt for better results
- */
-declare function addExampleContext(basePrompt: string, examples: string[]): string;
-//#endregion
-export { spec_creation_d_exports };
-//# sourceMappingURL=spec-creation.d.mts.map

package/dist/ai/prompts/spec-creation.d.mts.map

@@ -1 +0,0 @@
-{"version":3,"file":"spec-creation.d.mts","names":[],"sources":["../../../src/ai/prompts/spec-creation.ts"],"mappings":";;;;;;;;;iBAKgB,wBAAA,CACd,WAAA,UACA,IAAA,EAAM,MAAA;;;;iBA0BQ,oBAAA,CAAqB,WAAA;;;AA5BrC;iBAiDgB,2BAAA,CACd,WAAA,UACA,IAAA,EAAM,gBAAA;;;;iBAkCQ,eAAA,CAAA;;;;iBAiBA,iBAAA,CACd,UAAA,UACA,QAAA"}

package/dist/ai/prompts/spec-creation.mjs

@@ -1,111 +0,0 @@
-import { __exportAll } from "../../_virtual/_rolldown/runtime.mjs";
-
-//#region src/ai/prompts/spec-creation.ts
-var spec_creation_exports = /* @__PURE__ */ __exportAll({
-	addExampleContext: () => addExampleContext,
-	buildEventSpecPrompt: () => buildEventSpecPrompt,
-	buildOperationSpecPrompt: () => buildOperationSpecPrompt,
-	buildPresentationSpecPrompt: () => buildPresentationSpecPrompt,
-	getSystemPrompt: () => getSystemPrompt
-});
-/**
-* Build prompt for creating operation spec from description
-*/
-function buildOperationSpecPrompt(description, kind) {
-	return `You are a senior software architect creating a contract specification for an operation.
-
-The operation is a ${kind} (${kind === "command" ? "changes state, has side effects" : "read-only, idempotent"}).
-
-User description: ${description}
-
-Create a complete contract specification following these guidelines:
-
-1. **Name**: Use dot notation like "domain.operationName" (e.g., "user.signup", "payment.charge")
-2. **Version**: Start at 1
-3. **Description**: Clear, concise summary (1-2 sentences)
-4. **Goal**: Business purpose - why this operation exists
-5. **Context**: Background, constraints, scope (what it does and doesn't do)
-6. **Input/Output**: Describe the shape (we'll create schemas separately)
-7. **Auth**: Who can call this - anonymous, user, or admin
-8. **Feature Flags**: Any flags that gate this operation
-9. **Side Effects**: What events might be emitted, analytics to track
-
-Respond with a structured spec.`;
-}
-/**
-* Build prompt for creating event spec from description
-*/
-function buildEventSpecPrompt(description) {
-	return `You are a senior software architect creating an event specification.
-
-User description: ${description}
-
-Create a complete event specification following these guidelines:
-
-1. **Name**: Use dot notation like "domain.event_name" (e.g., "user.signup_completed", "payment.charged")
-2. **Version**: Start at 1
-3. **Description**: Clear description of when this event is emitted
-4. **Payload**: Describe what data the event carries
-5. **PII Fields**: List any personally identifiable information fields (e.g., ["email", "name"])
-
-Events represent things that have already happened and should use past tense.
-
-Respond with a structured spec.`;
-}
-/**
-* Build prompt for creating presentation spec from description
-*/
-function buildPresentationSpecPrompt(description, kind) {
-	return `You are a senior software architect creating a presentation specification.
-
-This is a ${kind} presentation - ${{
-		web_component: "a React component with props schema",
-		markdown: "markdown/MDX documentation or guide",
-		data: "structured data export (JSON/XML)"
-	}[kind]}.
-
-User description: ${description}
-
-Create a complete presentation specification following these guidelines:
-
-1. **Name**: Use dot notation like "domain.presentation_name" (e.g., "user.profile_card", "docs.api_guide")
-2. **Version**: Start at 1
-3. **Description**: What this presentation shows/provides
-4. **Kind-specific details**:
-   ${kind === "web_component" ? "- Component key (symbolic, resolved by host app)\n   - Props structure\n   - Analytics events to track" : kind === "markdown" ? "- Content or resource URI\n   - Target audience" : "- MIME type (e.g., application/json)\n   - Data structure description"}
-
-Respond with a structured spec.`;
-}
-/**
-* Build system prompt for all spec generation
-*/
-function getSystemPrompt() {
-	return `You are an expert software architect specializing in API design and contract-driven development.
-
-You create clear, well-documented specifications that serve as the single source of truth for operations, events, and presentations.
-
-Your specs are:
-- Precise and unambiguous
-- Following TypeScript conventions
-- Business-oriented (capturing the "why" not just "what")
-- Designed for both humans and AI agents to understand
-
-Always use proper dot notation for names and ensure all metadata is meaningful and accurate.`;
-}
-/**
-* Create example-based prompt for better results
-*/
-function addExampleContext(basePrompt, examples) {
-	if (examples.length === 0) return basePrompt;
-	return `${basePrompt}
-
-Here are some good examples for reference:
-
-${examples.join("\n\n")}
-
-Follow this structure and quality level.`;
-}
-
-//#endregion
-export { spec_creation_exports };
-//# sourceMappingURL=spec-creation.mjs.map

package/dist/ai/prompts/spec-creation.mjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"spec-creation.mjs","names":[],"sources":["../../../src/ai/prompts/spec-creation.ts"],"sourcesContent":["import type { OpKind, PresentationKind } from '../../types';\n\n/**\n * Build prompt for creating operation spec from description\n */\nexport function buildOperationSpecPrompt(\n  description: string,\n  kind: OpKind\n): string {\n  return `You are a senior software architect creating a contract specification for an operation.\n\nThe operation is a ${kind} (${kind === 'command' ? 'changes state, has side effects' : 'read-only, idempotent'}).\n\nUser description: ${description}\n\nCreate a complete contract specification following these guidelines:\n\n1. **Name**: Use dot notation like \"domain.operationName\" (e.g., \"user.signup\", \"payment.charge\")\n2. **Version**: Start at 1\n3. **Description**: Clear, concise summary (1-2 sentences)\n4. **Goal**: Business purpose - why this operation exists\n5. **Context**: Background, constraints, scope (what it does and doesn't do)\n6. **Input/Output**: Describe the shape (we'll create schemas separately)\n7. **Auth**: Who can call this - anonymous, user, or admin\n8. **Feature Flags**: Any flags that gate this operation\n9. **Side Effects**: What events might be emitted, analytics to track\n\nRespond with a structured spec.`;\n}\n\n/**\n * Build prompt for creating event spec from description\n */\nexport function buildEventSpecPrompt(description: string): string {\n  return `You are a senior software architect creating an event specification.\n\nUser description: ${description}\n\nCreate a complete event specification following these guidelines:\n\n1. **Name**: Use dot notation like \"domain.event_name\" (e.g., \"user.signup_completed\", \"payment.charged\")\n2. **Version**: Start at 1\n3. **Description**: Clear description of when this event is emitted\n4. **Payload**: Describe what data the event carries\n5. **PII Fields**: List any personally identifiable information fields (e.g., [\"email\", \"name\"])\n\nEvents represent things that have already happened and should use past tense.\n\nRespond with a structured spec.`;\n}\n\n/**\n * Build prompt for creating presentation spec from description\n */\nexport function buildPresentationSpecPrompt(\n  description: string,\n  kind: PresentationKind\n): string {\n  const kindDescriptions = {\n    web_component: 'a React component with props schema',\n    markdown: 'markdown/MDX documentation or guide',\n    data: 'structured data export (JSON/XML)',\n  };\n\n  return `You are a senior software architect creating a presentation specification.\n\nThis is a ${kind} presentation - ${kindDescriptions[kind]}.\n\nUser description: ${description}\n\nCreate a complete presentation specification following these guidelines:\n\n1. **Name**: Use dot notation like \"domain.presentation_name\" (e.g., \"user.profile_card\", \"docs.api_guide\")\n2. **Version**: Start at 1\n3. **Description**: What this presentation shows/provides\n4. **Kind-specific details**:\n   ${\n     kind === 'web_component'\n       ? '- Component key (symbolic, resolved by host app)\\n   - Props structure\\n   - Analytics events to track'\n       : kind === 'markdown'\n         ? '- Content or resource URI\\n   - Target audience'\n         : '- MIME type (e.g., application/json)\\n   - Data structure description'\n   }\n\nRespond with a structured spec.`;\n}\n\n/**\n * Build system prompt for all spec generation\n */\nexport function getSystemPrompt(): string {\n  return `You are an expert software architect specializing in API design and contract-driven development.\n\nYou create clear, well-documented specifications that serve as the single source of truth for operations, events, and presentations.\n\nYour specs are:\n- Precise and unambiguous\n- Following TypeScript conventions\n- Business-oriented (capturing the \"why\" not just \"what\")\n- Designed for both humans and AI agents to understand\n\nAlways use proper dot notation for names and ensure all metadata is meaningful and accurate.`;\n}\n\n/**\n * Create example-based prompt for better results\n */\nexport function addExampleContext(\n  basePrompt: string,\n  examples: string[]\n): string {\n  if (examples.length === 0) return basePrompt;\n\n  return `${basePrompt}\n\nHere are some good examples for reference:\n\n${examples.join('\\n\\n')}\n\nFollow this structure and quality level.`;\n}\n"],"mappings":";;;;;;;;;;;;;AAKA,SAAgB,yBACd,aACA,MACQ;AACR,QAAO;;qBAEY,KAAK,IAAI,SAAS,YAAY,oCAAoC,wBAAwB;;oBAE3F,YAAY;;;;;;;;;;;;;;;;;;;AAoBhC,SAAgB,qBAAqB,aAA6B;AAChE,QAAO;;oBAEW,YAAY;;;;;;;;;;;;;;;;;AAkBhC,SAAgB,4BACd,aACA,MACQ;AAOR,QAAO;;YAEG,KAAK,kBARU;EACvB,eAAe;EACf,UAAU;EACV,MAAM;EACP,CAIiD,MAAM;;oBAEtC,YAAY;;;;;;;;KAS3B,SAAS,kBACL,2GACA,SAAS,aACP,oDACA,wEACP;;;;;;;AAQJ,SAAgB,kBAA0B;AACxC,QAAO;;;;;;;;;;;;;;;AAgBT,SAAgB,kBACd,YACA,UACQ;AACR,KAAI,SAAS,WAAW,EAAG,QAAO;AAElC,QAAO,GAAG,WAAW;;;;EAIrB,SAAS,KAAK,OAAO,CAAC"}

package/dist/ai/providers.d.mts

@@ -1,13 +0,0 @@
-import { LanguageModel } from "ai";
-import { ResolvedContractsrcConfig } from "@contractspec/lib.contracts";
-
-//#region src/ai/providers.d.ts
-/**
- * Initialize AI provider based on configuration
- *
- * @deprecated Use createProvider() from @contractspec/lib.ai-providers instead
- */
-declare function getAIProvider(config: ResolvedContractsrcConfig): LanguageModel;
-//#endregion
-export { getAIProvider };
-//# sourceMappingURL=providers.d.mts.map

package/dist/ai/providers.d.mts.map

@@ -1 +0,0 @@
-{"version":3,"file":"providers.d.mts","names":[],"sources":["../../src/ai/providers.ts"],"mappings":";;;;;;;;;iBAiBgB,aAAA,CACd,MAAA,EAAQ,yBAAA,GACP,aAAA"}

package/dist/ai/providers.mjs

@@ -1,19 +0,0 @@
-import { getAIProvider } from "@contractspec/lib.ai-providers";
-
-//#region src/ai/providers.ts
-/**
-* Initialize AI provider based on configuration
-*
-* @deprecated Use createProvider() from @contractspec/lib.ai-providers instead
-*/
-function getAIProvider$1(config) {
-	return getAIProvider({
-		aiProvider: config.aiProvider,
-		aiModel: config.aiModel || void 0,
-		customEndpoint: config.customEndpoint || void 0
-	});
-}
-
-//#endregion
-export { getAIProvider$1 as getAIProvider };
-//# sourceMappingURL=providers.mjs.map

package/dist/ai/providers.mjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"providers.mjs","names":["getAIProvider","getProviderFromLib"],"sources":["../../src/ai/providers.ts"],"sourcesContent":["/**\n * AI Provider utilities for ContractSpec workspace.\n *\n * Re-exports from @contractspec/lib.ai-providers with workspace-specific additions.\n */\nimport type { LanguageModel } from 'ai';\nimport {\n  getAIProvider as getProviderFromLib,\n  type LegacyConfig,\n} from '@contractspec/lib.ai-providers';\nimport type { ResolvedContractsrcConfig } from '@contractspec/lib.contracts';\n\n/**\n * Initialize AI provider based on configuration\n *\n * @deprecated Use createProvider() from @contractspec/lib.ai-providers instead\n */\nexport function getAIProvider(\n  config: ResolvedContractsrcConfig\n): LanguageModel {\n  const legacyConfig: LegacyConfig = {\n    aiProvider: config.aiProvider,\n    aiModel: config.aiModel || undefined,\n    customEndpoint: config.customEndpoint || undefined,\n  };\n  return getProviderFromLib(legacyConfig);\n}\n"],"mappings":";;;;;;;;AAiBA,SAAgBA,gBACd,QACe;AAMf,QAAOC,cAL4B;EACjC,YAAY,OAAO;EACnB,SAAS,OAAO,WAAW;EAC3B,gBAAgB,OAAO,kBAAkB;EAC1C,CACsC"}

package/dist/formatters/index.d.mts

@@ -1,11 +0,0 @@
-import { SarifFormatOptions, SarifOutput, formatAsSarif, sarifToJson } from "./sarif.mjs";
-import { BaseJsonOutput, CiCheckJson, CiJsonOutput, JsonFormatOptions, formatAsJson } from "./json.mjs";
-import { TextFormatOptions, TextLine, formatAsText, formatAsTextLines } from "./text.mjs";
-
-//#region src/formatters/index.d.ts
-declare namespace index_d_exports {
-  export { BaseJsonOutput, CiCheckJson, CiJsonOutput, JsonFormatOptions, SarifFormatOptions, SarifOutput, TextFormatOptions, TextLine, formatAsJson, formatAsSarif, formatAsText, formatAsTextLines, sarifToJson };
-}
-//#endregion
-export { index_d_exports };
-//# sourceMappingURL=index.d.mts.map

package/dist/formatters/index.d.mts.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.d.mts","names":[],"sources":["../../src/formatters/index.ts"],"mappings":""}

package/dist/formatters/index.mjs

@@ -1,17 +0,0 @@
-import { __exportAll } from "../_virtual/_rolldown/runtime.mjs";
-import { formatAsSarif, sarifToJson } from "./sarif.mjs";
-import { formatAsJson } from "./json.mjs";
-import { formatAsText, formatAsTextLines } from "./text.mjs";
-
-//#region src/formatters/index.ts
-var formatters_exports = /* @__PURE__ */ __exportAll({
-	formatAsJson: () => formatAsJson,
-	formatAsSarif: () => formatAsSarif,
-	formatAsText: () => formatAsText,
-	formatAsTextLines: () => formatAsTextLines,
-	sarifToJson: () => sarifToJson
-});
-
-//#endregion
-export { formatters_exports };
-//# sourceMappingURL=index.mjs.map

package/dist/formatters/index.mjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.mjs","names":[],"sources":["../../src/formatters/index.ts"],"sourcesContent":["/**\n * Output formatters for CI check results.\n */\n\nexport * from './sarif';\nexport * from './json';\nexport * from './text';\n"],"mappings":""}

package/dist/formatters/json.d.mts

@@ -1,55 +0,0 @@
-import { CICheckResult } from "../services/ci-check/types.mjs";
-
-//#region src/formatters/json.d.ts
-/**
- * Base interface for all standardized JSON outputs.
- */
-interface BaseJsonOutput {
-  /** Schema version for output stability (e.g., "1.0"). */
-  schemaVersion: string;
-}
-/**
- * Options for JSON formatting.
- */
-interface JsonFormatOptions {
-  /** Pretty print with indentation. */
-  pretty?: boolean;
-}
-/**
- * CI JSON output structure (v1.0).
- */
-interface CiJsonOutput extends BaseJsonOutput {
-  checks: CiCheckJson[];
-  drift: {
-    status: 'none' | 'detected';
-    files: string[];
-  };
-  summary: {
-    pass: number;
-    fail: number;
-    warn: number;
-    total: number;
-    durationMs: number;
-    timestamp: string;
-  };
-  details?: {
-    commit?: string;
-    branch?: string;
-  };
-}
-interface CiCheckJson {
-  name: string;
-  status: 'pass' | 'fail' | 'warn';
-  category: string;
-  message: string;
-  file?: string;
-  line?: number;
-  details?: Record<string, unknown>;
-}
-/**
- * Format CI check results as standard JSON (v1.0).
- */
-declare function formatAsJson(result: CICheckResult, options?: JsonFormatOptions): string;
-//#endregion
-export { BaseJsonOutput, CiCheckJson, CiJsonOutput, JsonFormatOptions, formatAsJson };
-//# sourceMappingURL=json.d.mts.map

package/dist/formatters/json.d.mts.map

@@ -1 +0,0 @@
-{"version":3,"file":"json.d.mts","names":[],"sources":["../../src/formatters/json.ts"],"mappings":";;;;AAoBA;;UARiB,cAAA;EAUf;EARA,aAAA;AAAA;;;;UAMe,iBAAA;EASf;EAPA,MAAA;AAAA;;;;UAMe,YAAA,SAAqB,cAAA;EACpC,MAAA,EAAQ,WAAA;EACR,KAAA;IACE,MAAA;IACA,KAAA;EAAA;EAEF,OAAA;IACE,IAAA;IACA,IAAA;IACA,IAAA;IACA,KAAA;IACA,UAAA;IACA,SAAA;EAAA;EAEF,OAAA;IACE,MAAA;IACA,MAAA;EAAA;AAAA;AAAA,UAIa,WAAA;EACf,IAAA;EACA,MAAA;EACA,QAAA;EACA,OAAA;EACA,IAAA;EACA,IAAA;EACA,OAAA,GAAU,MAAA;AAAA;;;;iBAMI,YAAA,CACd,MAAA,EAAQ,aAAA,EACR,OAAA,GAAS,iBAAA"}

package/dist/formatters/json.mjs

@@ -1,43 +0,0 @@
-//#region src/formatters/json.ts
-/**
-* Format CI check results as standard JSON (v1.0).
-*/
-function formatAsJson(result, options = {}) {
-	const { pretty = true } = options;
-	const checks = result.issues.map((issue) => ({
-		name: issue.ruleId,
-		status: issue.severity === "error" ? "fail" : issue.severity === "warning" ? "warn" : "pass",
-		category: issue.category,
-		message: issue.message,
-		file: issue.file,
-		line: issue.line,
-		details: issue.context
-	}));
-	const fail = result.totalErrors;
-	const warn = result.totalWarnings;
-	const output = {
-		schemaVersion: "1.0",
-		checks,
-		drift: {
-			status: "none",
-			files: []
-		},
-		summary: {
-			pass: 0,
-			fail,
-			warn,
-			total: fail + warn,
-			durationMs: result.durationMs,
-			timestamp: result.timestamp
-		},
-		details: {
-			commit: result.commitSha,
-			branch: result.branch
-		}
-	};
-	return pretty ? JSON.stringify(output, null, 2) : JSON.stringify(output);
-}
-
-//#endregion
-export { formatAsJson };
-//# sourceMappingURL=json.mjs.map

package/dist/formatters/json.mjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"json.mjs","names":[],"sources":["../../src/formatters/json.ts"],"sourcesContent":["/**\n * JSON output formatter.\n *\n * Formats CI check results as machine-readable JSON\n * for parsing in CI/CD scripts and integrations.\n */\n\nimport type { CICheckResult } from '../services/ci-check/types';\n\n/**\n * Base interface for all standardized JSON outputs.\n */\nexport interface BaseJsonOutput {\n  /** Schema version for output stability (e.g., \"1.0\"). */\n  schemaVersion: string;\n}\n\n/**\n * Options for JSON formatting.\n */\nexport interface JsonFormatOptions {\n  /** Pretty print with indentation. */\n  pretty?: boolean;\n}\n\n/**\n * CI JSON output structure (v1.0).\n */\nexport interface CiJsonOutput extends BaseJsonOutput {\n  checks: CiCheckJson[];\n  drift: {\n    status: 'none' | 'detected';\n    files: string[];\n  };\n  summary: {\n    pass: number;\n    fail: number;\n    warn: number;\n    total: number;\n    durationMs: number;\n    timestamp: string;\n  };\n  details?: {\n    commit?: string;\n    branch?: string;\n  };\n}\n\nexport interface CiCheckJson {\n  name: string;\n  status: 'pass' | 'fail' | 'warn';\n  category: string;\n  message: string;\n  file?: string;\n  line?: number;\n  details?: Record<string, unknown>;\n}\n\n/**\n * Format CI check results as standard JSON (v1.0).\n */\nexport function formatAsJson(\n  result: CICheckResult,\n  options: JsonFormatOptions = {}\n): string {\n  const { pretty = true } = options;\n\n  // Map issues to checks\n  const checks: CiCheckJson[] = result.issues.map((issue) => ({\n    name: issue.ruleId,\n    status:\n      issue.severity === 'error'\n        ? 'fail'\n        : issue.severity === 'warning'\n          ? 'warn'\n          : 'pass',\n    category: issue.category,\n    message: issue.message,\n    file: issue.file,\n    line: issue.line,\n    details: issue.context as Record<string, unknown>,\n  }));\n\n  // Add passing categories as passing checks (summary level) if needed\n  // Or purely rely on issues. The previous implementation had categories.\n  // For v1.0 schema, we focus on list of checks.\n\n  // Count stats\n  const fail = result.totalErrors;\n  const warn = result.totalWarnings;\n  // Note: \"pass\" count is harder to derive solely from issues (which are usually negative).\n  // But we can use category results to infer passing checks if we had granular per-check results.\n  // For now, we'll use the issues list. If issues is empty, it's all pass?\n  // Actually, let's map the categories too if they represent high-level checks.\n\n  const output: CiJsonOutput = {\n    schemaVersion: '1.0',\n    checks,\n    drift: {\n      status: 'none', // TODO: Implement drift detection\n      files: [],\n    },\n    summary: {\n      pass: 0, // Placeholder, calculated properly if we have tracking of passed assertions\n      fail,\n      warn,\n      total: fail + warn,\n      durationMs: result.durationMs,\n      timestamp: result.timestamp,\n    },\n    details: {\n      commit: result.commitSha,\n      branch: result.branch,\n    },\n  };\n\n  return pretty ? JSON.stringify(output, null, 2) : JSON.stringify(output);\n}\n"],"mappings":";;;;AA6DA,SAAgB,aACd,QACA,UAA6B,EAAE,EACvB;CACR,MAAM,EAAE,SAAS,SAAS;CAG1B,MAAM,SAAwB,OAAO,OAAO,KAAK,WAAW;EAC1D,MAAM,MAAM;EACZ,QACE,MAAM,aAAa,UACf,SACA,MAAM,aAAa,YACjB,SACA;EACR,UAAU,MAAM;EAChB,SAAS,MAAM;EACf,MAAM,MAAM;EACZ,MAAM,MAAM;EACZ,SAAS,MAAM;EAChB,EAAE;CAOH,MAAM,OAAO,OAAO;CACpB,MAAM,OAAO,OAAO;CAMpB,MAAM,SAAuB;EAC3B,eAAe;EACf;EACA,OAAO;GACL,QAAQ;GACR,OAAO,EAAE;GACV;EACD,SAAS;GACP,MAAM;GACN;GACA;GACA,OAAO,OAAO;GACd,YAAY,OAAO;GACnB,WAAW,OAAO;GACnB;EACD,SAAS;GACP,QAAQ,OAAO;GACf,QAAQ,OAAO;GAChB;EACF;AAED,QAAO,SAAS,KAAK,UAAU,QAAQ,MAAM,EAAE,GAAG,KAAK,UAAU,OAAO"}