@contractspec/module.workspace 1.44.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Chaman Ventures, SASU
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,50 @@
+# @contractspec/module.workspace
+
+Website: https://contractspec.io/
+
+
+Pure, deterministic domain logic and static analysis utilities for ContractSpec workspace operations.
+
+## Purpose
+
+This module contains platform-agnostic logic used by ContractSpec tooling:
+
+- **Types**: Shared type definitions for specs, templates, and analysis results
+- **Analysis**: Static code analysis (spec scanning, dependency graphs, semantic diff)
+- **Templates**: Code generation templates for specs and handlers
+- **AI Prompts**: Prompt builders for AI-assisted spec creation and code generation
+
+## Design Principles
+
+- **No side effects**: All functions are pure and deterministic
+- **No CLI dependencies**: No `chalk`, `ora`, `commander`, or `inquirer`
+- **No filesystem access**: Operations take code/data as input, return results
+- **Reusable**: Can be used by CLI, web apps, VS Code extensions, etc.
+
+## Usage
+
+```typescript
+import {
+  scanSpecSource,
+  computeSemanticDiff,
+  buildDependencyGraph,
+  validateSpecStructure,
+  generateOperationSpec,
+} from '@contractspec/module.workspace';
+```
+
+## Exports
+
+- `analysis/` - Static analysis utilities
+- `templates/` - Code generation templates
+- `ai/` - AI prompt builders
+- `types/` - Shared type definitions
+
+
+
+
+
+
+
+
+

package/dist/ai/code-generation.d.ts

@@ -0,0 +1,28 @@
+//#region src/ai/code-generation.d.ts
+/**
+ * AI prompts for code generation.
+ * Extracted from cli-contractspec/src/ai/prompts/code-generation.ts
+ */
+/**
+ * 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 { buildComponentPrompt, buildFormPrompt, buildHandlerPrompt, buildTestPrompt, getCodeGenSystemPrompt };
+//# sourceMappingURL=code-generation.d.ts.map

package/dist/ai/code-generation.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"code-generation.d.ts","names":[],"sources":["../../src/ai/code-generation.ts"],"sourcesContent":[],"mappings":";;AAQA;AA0BA;AA0BA;AA2BA;AA2CA;;iBA1HgB,kBAAA;;;;iBA0BA,oBAAA;;;;iBA0BA,eAAA;;;;iBA2BA,eAAA;;;;iBA2CA,sBAAA,CAAA"}

package/dist/ai/code-generation.js

@@ -0,0 +1,138 @@
+//#region src/ai/code-generation.ts
+/**
+* AI prompts for code generation.
+* Extracted from cli-contractspec/src/ai/prompts/code-generation.ts
+*/
+/**
+* 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, getCodeGenSystemPrompt };
+//# sourceMappingURL=code-generation.js.map

package/dist/ai/code-generation.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"code-generation.js","names":[],"sources":["../../src/ai/code-generation.ts"],"sourcesContent":["/**\n * AI prompts for code generation.\n * Extracted from cli-contractspec/src/ai/prompts/code-generation.ts\n */\n\n/**\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":";;;;;;;;AAQA,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/spec-creation.d.ts

@@ -0,0 +1,27 @@
+import { OpKind, PresentationKind } from "../types/spec-types.js";
+
+//#region src/ai/spec-creation.d.ts
+
+/**
+ * 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 { addExampleContext, buildEventSpecPrompt, buildOperationSpecPrompt, buildPresentationSpecPrompt, getSystemPrompt };
+//# sourceMappingURL=spec-creation.d.ts.map

package/dist/ai/spec-creation.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"spec-creation.d.ts","names":[],"sources":["../../src/ai/spec-creation.ts"],"sourcesContent":[],"mappings":";;;;AA2DA;AAoCA;AAiBA;iBAtGgB,wBAAA,4BAER;;;;iBA0BQ,oBAAA;;;;iBAqBA,2BAAA,4BAER;;;;iBAkCQ,eAAA,CAAA;;;;iBAiBA,iBAAA"}

package/dist/ai/spec-creation.js

@@ -0,0 +1,102 @@
+//#region src/ai/spec-creation.ts
+/**
+* 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 { addExampleContext, buildEventSpecPrompt, buildOperationSpecPrompt, buildPresentationSpecPrompt, getSystemPrompt };
+//# sourceMappingURL=spec-creation.js.map

package/dist/ai/spec-creation.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"spec-creation.js","names":[],"sources":["../../src/ai/spec-creation.ts"],"sourcesContent":["/**\n * AI prompts for spec creation.\n * Extracted from cli-contractspec/src/ai/prompts/spec-creation.ts\n */\n\nimport type { OpKind, PresentationKind } from '../types/spec-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":";;;;AAUA,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/analysis/deps/graph.d.ts

@@ -0,0 +1,34 @@
+import { ContractGraph, ContractNode } from "../../types/analysis-types.js";
+
+//#region src/analysis/deps/graph.d.ts
+
+/**
+ * Build reverse edges (dependents) for all nodes in the graph.
+ */
+declare function buildReverseEdges(graph: ContractGraph): void;
+/**
+ * Detect circular dependencies in the graph.
+ */
+declare function detectCycles(graph: ContractGraph): string[][];
+/**
+ * Find missing dependencies (referenced but not defined).
+ */
+declare function findMissingDependencies(graph: ContractGraph): {
+  contract: string;
+  missing: string[];
+}[];
+/**
+ * Generate DOT format output for visualization.
+ */
+declare function toDot(graph: ContractGraph): string;
+/**
+ * Create an empty contract graph.
+ */
+declare function createContractGraph(): ContractGraph;
+/**
+ * Add a node to the contract graph.
+ */
+declare function addContractNode(graph: ContractGraph, key: string, file: string, dependencies: string[]): void;
+//#endregion
+export { addContractNode, buildReverseEdges, createContractGraph, detectCycles, findMissingDependencies, toDot };
+//# sourceMappingURL=graph.d.ts.map

package/dist/analysis/deps/graph.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"graph.d.ts","names":[],"sources":["../../../src/analysis/deps/graph.ts"],"sourcesContent":[],"mappings":";;;;AAwFA;AAsBA;AAOA;iBAzGgB,iBAAA,QAAyB;;;;iBAsBzB,YAAA,QAAoB;;;;iBAoCpB,uBAAA,QACP;;;;;;;iBAiBO,KAAA,QAAa;;;;iBAsBb,mBAAA,CAAA,GAAuB;;;;iBAOvB,eAAA,QACP"}

package/dist/analysis/deps/graph.js

@@ -0,0 +1,85 @@
+//#region src/analysis/deps/graph.ts
+/**
+* Build reverse edges (dependents) for all nodes in the graph.
+*/
+function buildReverseEdges(graph) {
+	for (const node of graph.values()) node.dependents = [];
+	for (const [key, node] of graph) for (const dep of node.dependencies) {
+		const depNode = graph.get(dep);
+		if (depNode) depNode.dependents.push(key);
+	}
+	for (const node of graph.values()) node.dependents.sort((a, b) => a.localeCompare(b));
+}
+/**
+* Detect circular dependencies in the graph.
+*/
+function detectCycles(graph) {
+	const visited = /* @__PURE__ */ new Set();
+	const stack = /* @__PURE__ */ new Set();
+	const cycles = [];
+	function dfs(key, path) {
+		if (stack.has(key)) {
+			const start = path.indexOf(key);
+			if (start >= 0) cycles.push([...path.slice(start), key]);
+			return;
+		}
+		if (visited.has(key)) return;
+		visited.add(key);
+		stack.add(key);
+		const node = graph.get(key);
+		if (node) for (const dep of node.dependencies) dfs(dep, [...path, key]);
+		stack.delete(key);
+	}
+	for (const key of graph.keys()) if (!visited.has(key)) dfs(key, []);
+	return cycles;
+}
+/**
+* Find missing dependencies (referenced but not defined).
+*/
+function findMissingDependencies(graph) {
+	const missing = [];
+	for (const [key, node] of graph) {
+		const absent = node.dependencies.filter((dep) => !graph.has(dep));
+		if (absent.length > 0) missing.push({
+			contract: key,
+			missing: absent
+		});
+	}
+	return missing;
+}
+/**
+* Generate DOT format output for visualization.
+*/
+function toDot(graph) {
+	const lines = [];
+	lines.push("digraph ContractDependencies {");
+	lines.push("  rankdir=LR;");
+	lines.push("  node [shape=box];");
+	for (const [key, node] of graph) {
+		for (const dep of node.dependencies) lines.push(`  "${key}" -> "${dep}";`);
+		if (node.dependencies.length === 0) lines.push(`  "${key}";`);
+	}
+	lines.push("}");
+	return lines.join("\n");
+}
+/**
+* Create an empty contract graph.
+*/
+function createContractGraph() {
+	return /* @__PURE__ */ new Map();
+}
+/**
+* Add a node to the contract graph.
+*/
+function addContractNode(graph, key, file, dependencies) {
+	graph.set(key, {
+		key,
+		file,
+		dependencies,
+		dependents: []
+	});
+}
+
+//#endregion
+export { addContractNode, buildReverseEdges, createContractGraph, detectCycles, findMissingDependencies, toDot };
+//# sourceMappingURL=graph.js.map

package/dist/analysis/deps/graph.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"graph.js","names":["cycles: string[][]","missing: { contract: string; missing: string[] }[]","lines: string[]"],"sources":["../../../src/analysis/deps/graph.ts"],"sourcesContent":["/**\n * Contract dependency graph utilities.\n * Extracted from cli-contractspec/src/commands/deps/graph.ts\n */\n\nimport type { ContractNode, ContractGraph } from '../../types/analysis-types';\n\nexport type { ContractNode, ContractGraph };\n\n/**\n * Build reverse edges (dependents) for all nodes in the graph.\n */\nexport function buildReverseEdges(graph: ContractGraph): void {\n  for (const node of graph.values()) {\n    node.dependents = [];\n  }\n\n  for (const [key, node] of graph) {\n    for (const dep of node.dependencies) {\n      const depNode = graph.get(dep);\n      if (depNode) {\n        depNode.dependents.push(key);\n      }\n    }\n  }\n\n  for (const node of graph.values()) {\n    node.dependents.sort((a, b) => a.localeCompare(b));\n  }\n}\n\n/**\n * Detect circular dependencies in the graph.\n */\nexport function detectCycles(graph: ContractGraph): string[][] {\n  const visited = new Set<string>();\n  const stack = new Set<string>();\n  const cycles: string[][] = [];\n\n  function dfs(key: string, path: string[]) {\n    if (stack.has(key)) {\n      const start = path.indexOf(key);\n      if (start >= 0) cycles.push([...path.slice(start), key]);\n      return;\n    }\n    if (visited.has(key)) return;\n\n    visited.add(key);\n    stack.add(key);\n\n    const node = graph.get(key);\n    if (node) {\n      for (const dep of node.dependencies) {\n        dfs(dep, [...path, key]);\n      }\n    }\n\n    stack.delete(key);\n  }\n\n  for (const key of graph.keys()) {\n    if (!visited.has(key)) dfs(key, []);\n  }\n\n  return cycles;\n}\n\n/**\n * Find missing dependencies (referenced but not defined).\n */\nexport function findMissingDependencies(\n  graph: ContractGraph\n): { contract: string; missing: string[] }[] {\n  const missing: { contract: string; missing: string[] }[] = [];\n\n  for (const [key, node] of graph) {\n    const absent = node.dependencies.filter((dep) => !graph.has(dep));\n    if (absent.length > 0) {\n      missing.push({ contract: key, missing: absent });\n    }\n  }\n\n  return missing;\n}\n\n/**\n * Generate DOT format output for visualization.\n */\nexport function toDot(graph: ContractGraph): string {\n  const lines: string[] = [];\n  lines.push('digraph ContractDependencies {');\n  lines.push('  rankdir=LR;');\n  lines.push('  node [shape=box];');\n\n  for (const [key, node] of graph) {\n    for (const dep of node.dependencies) {\n      lines.push(`  \"${key}\" -> \"${dep}\";`);\n    }\n    if (node.dependencies.length === 0) {\n      lines.push(`  \"${key}\";`);\n    }\n  }\n\n  lines.push('}');\n  return lines.join('\\n');\n}\n\n/**\n * Create an empty contract graph.\n */\nexport function createContractGraph(): ContractGraph {\n  return new Map();\n}\n\n/**\n * Add a node to the contract graph.\n */\nexport function addContractNode(\n  graph: ContractGraph,\n  key: string,\n  file: string,\n  dependencies: string[]\n): void {\n  graph.set(key, {\n    key,\n    file,\n    dependencies,\n    dependents: [],\n  });\n}\n"],"mappings":";;;;AAYA,SAAgB,kBAAkB,OAA4B;AAC5D,MAAK,MAAM,QAAQ,MAAM,QAAQ,CAC/B,MAAK,aAAa,EAAE;AAGtB,MAAK,MAAM,CAAC,KAAK,SAAS,MACxB,MAAK,MAAM,OAAO,KAAK,cAAc;EACnC,MAAM,UAAU,MAAM,IAAI,IAAI;AAC9B,MAAI,QACF,SAAQ,WAAW,KAAK,IAAI;;AAKlC,MAAK,MAAM,QAAQ,MAAM,QAAQ,CAC/B,MAAK,WAAW,MAAM,GAAG,MAAM,EAAE,cAAc,EAAE,CAAC;;;;;AAOtD,SAAgB,aAAa,OAAkC;CAC7D,MAAM,0BAAU,IAAI,KAAa;CACjC,MAAM,wBAAQ,IAAI,KAAa;CAC/B,MAAMA,SAAqB,EAAE;CAE7B,SAAS,IAAI,KAAa,MAAgB;AACxC,MAAI,MAAM,IAAI,IAAI,EAAE;GAClB,MAAM,QAAQ,KAAK,QAAQ,IAAI;AAC/B,OAAI,SAAS,EAAG,QAAO,KAAK,CAAC,GAAG,KAAK,MAAM,MAAM,EAAE,IAAI,CAAC;AACxD;;AAEF,MAAI,QAAQ,IAAI,IAAI,CAAE;AAEtB,UAAQ,IAAI,IAAI;AAChB,QAAM,IAAI,IAAI;EAEd,MAAM,OAAO,MAAM,IAAI,IAAI;AAC3B,MAAI,KACF,MAAK,MAAM,OAAO,KAAK,aACrB,KAAI,KAAK,CAAC,GAAG,MAAM,IAAI,CAAC;AAI5B,QAAM,OAAO,IAAI;;AAGnB,MAAK,MAAM,OAAO,MAAM,MAAM,CAC5B,KAAI,CAAC,QAAQ,IAAI,IAAI,CAAE,KAAI,KAAK,EAAE,CAAC;AAGrC,QAAO;;;;;AAMT,SAAgB,wBACd,OAC2C;CAC3C,MAAMC,UAAqD,EAAE;AAE7D,MAAK,MAAM,CAAC,KAAK,SAAS,OAAO;EAC/B,MAAM,SAAS,KAAK,aAAa,QAAQ,QAAQ,CAAC,MAAM,IAAI,IAAI,CAAC;AACjE,MAAI,OAAO,SAAS,EAClB,SAAQ,KAAK;GAAE,UAAU;GAAK,SAAS;GAAQ,CAAC;;AAIpD,QAAO;;;;;AAMT,SAAgB,MAAM,OAA8B;CAClD,MAAMC,QAAkB,EAAE;AAC1B,OAAM,KAAK,iCAAiC;AAC5C,OAAM,KAAK,gBAAgB;AAC3B,OAAM,KAAK,sBAAsB;AAEjC,MAAK,MAAM,CAAC,KAAK,SAAS,OAAO;AAC/B,OAAK,MAAM,OAAO,KAAK,aACrB,OAAM,KAAK,MAAM,IAAI,QAAQ,IAAI,IAAI;AAEvC,MAAI,KAAK,aAAa,WAAW,EAC/B,OAAM,KAAK,MAAM,IAAI,IAAI;;AAI7B,OAAM,KAAK,IAAI;AACf,QAAO,MAAM,KAAK,KAAK;;;;;AAMzB,SAAgB,sBAAqC;AACnD,wBAAO,IAAI,KAAK;;;;;AAMlB,SAAgB,gBACd,OACA,KACA,MACA,cACM;AACN,OAAM,IAAI,KAAK;EACb;EACA;EACA;EACA,YAAY,EAAE;EACf,CAAC"}

package/dist/analysis/deps/parse-imports.d.ts

@@ -0,0 +1,17 @@
+//#region src/analysis/deps/parse-imports.d.ts
+/**
+ * Import parsing utilities for dependency analysis.
+ * Extracted from cli-contractspec/src/commands/deps/parse-imports.ts
+ */
+/**
+ * Parse spec imports from source code.
+ * Returns the names of imported specs based on file naming conventions.
+ *
+ * @param sourceCode - The source code to parse
+ * @param fromFilePath - The path of the file being parsed (for relative resolution)
+ * @returns Array of imported spec names
+ */
+declare function parseImportedSpecNames(sourceCode: string, _fromFilePath: string): string[];
+//#endregion
+export { parseImportedSpecNames };
+//# sourceMappingURL=parse-imports.d.ts.map

package/dist/analysis/deps/parse-imports.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"parse-imports.d.ts","names":[],"sources":["../../../src/analysis/deps/parse-imports.ts"],"sourcesContent":[],"mappings":";;AAaA;;;;;;;;;;;iBAAgB,sBAAA"}

package/dist/analysis/deps/parse-imports.js

@@ -0,0 +1,31 @@
+//#region src/analysis/deps/parse-imports.ts
+/**
+* Import parsing utilities for dependency analysis.
+* Extracted from cli-contractspec/src/commands/deps/parse-imports.ts
+*/
+/**
+* Parse spec imports from source code.
+* Returns the names of imported specs based on file naming conventions.
+*
+* @param sourceCode - The source code to parse
+* @param fromFilePath - The path of the file being parsed (for relative resolution)
+* @returns Array of imported spec names
+*/
+function parseImportedSpecNames(sourceCode, _fromFilePath) {
+	const imports = [];
+	const importRegex = /import\s+.*?\s+from\s+['"]([^'"]+\.(?:contracts|contract|operation|operations|event|presentation|workflow|data-view|migration|telemetry|experiment|app-config|integration|knowledge)(?:\.[jt]s)?)['"]/g;
+	let match;
+	while ((match = importRegex.exec(sourceCode)) !== null) {
+		const importPath = match[1];
+		if (!importPath) continue;
+		if (!importPath.startsWith(".") && !importPath.startsWith("/")) continue;
+		const pathParts = importPath.split("/");
+		const name = (pathParts[pathParts.length - 1] ?? "").replace(/\.(ts|js)$/, "").replace(/\.(contracts|contract|operation|operations|event|presentation|workflow|data-view|migration|telemetry|experiment|app-config|integration|knowledge)$/, "");
+		if (name.length > 0) imports.push(name);
+	}
+	return Array.from(new Set(imports)).sort((a, b) => a.localeCompare(b));
+}
+
+//#endregion
+export { parseImportedSpecNames };
+//# sourceMappingURL=parse-imports.js.map

package/dist/analysis/deps/parse-imports.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"parse-imports.js","names":["imports: string[]","match: RegExpExecArray | null"],"sources":["../../../src/analysis/deps/parse-imports.ts"],"sourcesContent":["/**\n * Import parsing utilities for dependency analysis.\n * Extracted from cli-contractspec/src/commands/deps/parse-imports.ts\n */\n\n/**\n * Parse spec imports from source code.\n * Returns the names of imported specs based on file naming conventions.\n *\n * @param sourceCode - The source code to parse\n * @param fromFilePath - The path of the file being parsed (for relative resolution)\n * @returns Array of imported spec names\n */\nexport function parseImportedSpecNames(\n  sourceCode: string,\n  _fromFilePath: string\n): string[] {\n  const imports: string[] = [];\n\n  // Capture relative imports that reference spec-ish files.\n  // Examples:\n  // import x from './foo.contracts'\n  // import { y } from '../bar.event.ts'\n  const importRegex =\n    /import\\s+.*?\\s+from\\s+['\"]([^'\"]+\\.(?:contracts|contract|operation|operations|event|presentation|workflow|data-view|migration|telemetry|experiment|app-config|integration|knowledge)(?:\\.[jt]s)?)['\"]/g;\n\n  let match: RegExpExecArray | null;\n  while ((match = importRegex.exec(sourceCode)) !== null) {\n    const importPath = match[1];\n    if (!importPath) continue;\n    if (!importPath.startsWith('.') && !importPath.startsWith('/')) continue;\n\n    // Extract base name from the import path\n    const pathParts = importPath.split('/');\n    const base = pathParts[pathParts.length - 1] ?? '';\n\n    const name = base\n      .replace(/\\.(ts|js)$/, '')\n      .replace(\n        /\\.(contracts|contract|operation|operations|event|presentation|workflow|data-view|migration|telemetry|experiment|app-config|integration|knowledge)$/,\n        ''\n      );\n\n    if (name.length > 0) {\n      imports.push(name);\n    }\n  }\n\n  return Array.from(new Set(imports)).sort((a, b) => a.localeCompare(b));\n}\n"],"mappings":";;;;;;;;;;;;;AAaA,SAAgB,uBACd,YACA,eACU;CACV,MAAMA,UAAoB,EAAE;CAM5B,MAAM,cACJ;CAEF,IAAIC;AACJ,SAAQ,QAAQ,YAAY,KAAK,WAAW,MAAM,MAAM;EACtD,MAAM,aAAa,MAAM;AACzB,MAAI,CAAC,WAAY;AACjB,MAAI,CAAC,WAAW,WAAW,IAAI,IAAI,CAAC,WAAW,WAAW,IAAI,CAAE;EAGhE,MAAM,YAAY,WAAW,MAAM,IAAI;EAGvC,MAAM,QAFO,UAAU,UAAU,SAAS,MAAM,IAG7C,QAAQ,cAAc,GAAG,CACzB,QACC,sJACA,GACD;AAEH,MAAI,KAAK,SAAS,EAChB,SAAQ,KAAK,KAAK;;AAItB,QAAO,MAAM,KAAK,IAAI,IAAI,QAAQ,CAAC,CAAC,MAAM,GAAG,MAAM,EAAE,cAAc,EAAE,CAAC"}

package/dist/analysis/diff/deep-diff.d.ts

@@ -0,0 +1,33 @@
+import { SemanticDiffItem } from "../../types/analysis-types.js";
+import { FieldSnapshot, IoSnapshot } from "../snapshot/types.js";
+
+//#region src/analysis/diff/deep-diff.d.ts
+
+/**
+ * Deep diff options.
+ */
+interface DeepDiffOptions {
+  /** Only report breaking changes */
+  breakingOnly?: boolean;
+  /** Path prefix for nested diffs */
+  pathPrefix?: string;
+}
+/**
+ * Compute deep differences between two IO schemas.
+ */
+declare function computeIoDiff(base: IoSnapshot, head: IoSnapshot, options?: DeepDiffOptions): SemanticDiffItem[];
+/**
+ * Compute differences between two field maps.
+ */
+declare function computeFieldsDiff(baseFields: Record<string, FieldSnapshot>, headFields: Record<string, FieldSnapshot>, pathPrefix: string, options?: DeepDiffOptions): SemanticDiffItem[];
+/**
+ * Compute differences between two field definitions.
+ */
+declare function computeFieldDiff(base: FieldSnapshot, head: FieldSnapshot, path: string, _options?: DeepDiffOptions): SemanticDiffItem[];
+/**
+ * Classify a diff as breaking based on context.
+ */
+declare function isBreakingChange(diff: SemanticDiffItem, context: 'input' | 'output'): boolean;
+//#endregion
+export { DeepDiffOptions, computeFieldDiff, computeFieldsDiff, computeIoDiff, isBreakingChange };
+//# sourceMappingURL=deep-diff.d.ts.map

package/dist/analysis/diff/deep-diff.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"deep-diff.d.ts","names":[],"sources":["../../../src/analysis/diff/deep-diff.ts"],"sourcesContent":[],"mappings":";;;;;;;;AA8CgB,UAjCC,eAAA,CAiCgB;EACJ;EAAf,YAAA,CAAA,EAAA,OAAA;EACe;EAAf,UAAA,CAAA,EAAA,MAAA;;;;AA+Dd;AACQ,iBAzFQ,aAAA,CAyFR,IAAA,EAxFA,UAwFA,EAAA,IAAA,EAvFA,UAuFA,EAAA,OAAA,CAAA,EAtFG,eAsFH,CAAA,EArFL,gBAqFK,EAAA;;;;AAIW,iBAtEH,iBAAA,CAsEG,UAAA,EArEL,MAqEK,CAAA,MAAA,EArEU,aAqEV,CAAA,EAAA,UAAA,EApEL,MAoEK,CAAA,MAAA,EApEU,aAoEV,CAAA,EAAA,UAAA,EAAA,MAAA,EAAA,OAAA,CAAA,EAlER,eAkEQ,CAAA,EAjEhB,gBAiEgB,EAAA;AAwGnB;;;iBA7GgB,gBAAA,OACR,qBACA,wCAEI,kBACT;;;;iBAwGa,gBAAA,OACR"}