@jterrats/smart-deployment 1.0.3

package/lib/constants/deployment-order.js

@@ -0,0 +1,162 @@
+/**
+ * Salesforce Metadata Deployment Order
+ *
+ * Defines recommended deployment order for CORE Salesforce metadata types.
+ *
+ * **Important**: Salesforce has 100+ metadata types and adds new ones each release.
+ * This file defines priorities for the MOST COMMON types (~78).
+ * For unlisted types, the plugin uses a fallback priority (99) via getDeploymentPriority().
+ *
+ * **Extensibility Strategy**:
+ * - Add new types here as needed (e.g., new Einstein features)
+ * - Unknown types automatically get priority 99 (deploy last, safe default)
+ * - Plugin works with ANY metadata type, even if not listed here
+ *
+ * Lower numbers = deploy first
+ * Higher numbers = deploy later
+ *
+ * @see https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy.htm
+ * @see https://help.salesforce.com/s/articleView?id=000386798&type=1
+ */
+/**
+ * Deployment priority map for all Salesforce metadata types.
+ * Follows the principle: dependencies first, dependents later.
+ *
+ * Priority Groups:
+ * - 1-9: Core data model (objects, fields, record types)
+ * - 10-19: Code (Apex classes, pages, components)
+ * - 20-29: Automation (triggers, flows, process builders)
+ * - 30-39: UI & Experiences (layouts, pages, sites)
+ * - 40-49: Security & Access (profiles, permission sets, sharing)
+ * - 50-59: Integration & External (connected apps, named credentials)
+ * - 60-69: Content & Knowledge
+ * - 70-79: Analytics & Reporting
+ * - 80-89: Other metadata
+ * - 90-99: Post-deployment (translations, static resources)
+ */
+export const DEPLOYMENT_ORDER = Object.freeze({
+    // ========== Tier 0: Global Configuration (1-5) ==========
+    GlobalValueSet: 1, // Global value sets used by picklists
+    StandardValueSet: 2, // Standard value sets
+    CustomLabels: 3, // Custom labels
+    Translations: 4, // Translation files
+    StandardValueSetTranslation: 5, // Standard value set translations
+    // ========== Tier 1: Foundation - Objects & Fields (6-15) ==========
+    CustomObject: 6, // Core data model - must be early
+    CustomSetting: 7, // Custom settings (like custom objects)
+    DataCategoryGroup: 8, // Data category groups
+    CustomMetadata: 9, // Custom metadata types
+    CustomMetadataRecord: 10, // Custom metadata records
+    CustomField: 11, // Fields depend on objects
+    ObjectTranslation: 12, // Object translations
+    RecordType: 13, // Record types depend on objects/fields
+    BusinessProcess: 14, // Business processes depend on record types
+    ValidationRule: 15, // Validation rules depend on fields
+    WorkflowRule: 16, // Workflow rules
+    // ========== Tier 2: Security Foundation (17-23) ==========
+    OrgSettings: 17, // Org-wide settings
+    CorsWhitelistOrigin: 18, // CORS settings
+    CspTrustedSite: 19, // CSP trusted sites
+    Role: 20, // Role hierarchy
+    DelegateGroup: 21, // Delegate groups
+    Group: 22, // Public groups
+    CustomPermission: 23, // Custom permissions
+    ExternalCredential: 24, // External credentials
+    NamedCredential: 25, // Named credentials for callouts
+    DataSourceObject: 26, // Data source objects
+    // ========== Tier 3: Code & Resources (27-36) ==========
+    StaticResource: 27, // Static resources
+    Document: 28, // Documents
+    ContentAsset: 29, // Content assets
+    EmailTemplate: 30, // Email templates
+    ApexClass: 31, // Apex classes - deploy before triggers
+    VisualforceComponent: 32, // VF components
+    VisualforcePage: 33, // VF pages
+    LightningComponentBundle: 34, // LWC
+    AuraDefinitionBundle: 35, // Aura components
+    ApexTrigger: 36, // Triggers after classes
+    // ========== Tier 4: Service Cloud (37-42) ==========
+    ServicePresenceStatus: 37, // Service presence
+    PresenceUserConfig: 38, // Presence config
+    Queue: 39, // Queues
+    ServiceChannel: 40, // Service channels
+    QueueRoutingConfig: 41, // Queue routing
+    ChannelLayout: 42, // Channel layouts
+    // ========== Tier 5: Business Logic & AI (43-49) ==========
+    MilestoneType: 43, // Milestone types
+    EntitlementProcess: 44, // Entitlement processes
+    GenAiFunction: 45, // Einstein AI functions
+    GenAiPromptTemplate: 46, // Einstein prompts
+    GenAiPlannerBundle: 47, // Einstein planners
+    Flow: 48, // Flows (after Apex classes)
+    PathAssistant: 49, // Path assistant
+    // ========== Tier 6: UI Components (50-59) ==========
+    Layout: 50, // Page layouts
+    Bot: 51, // Einstein Bots
+    BotVersion: 52, // Bot versions
+    GenAiPlugin: 53, // Einstein plugins
+    FlexiPage: 54, // Lightning pages
+    QuickAction: 55, // Quick actions
+    CompactLayout: 56, // Compact layouts
+    ListView: 57, // List views
+    WebLink: 58, // Web links
+    LightningApp: 59, // Lightning apps
+    SearchCustomization: 60, // Search customizations
+    CustomNotificationType: 61, // Custom notifications
+    // ========== Tier 7: Experience Cloud (62-69) ==========
+    BrandingSet: 62, // Branding sets
+    DigitalExperienceConfig: 63, // Digital experience config
+    Site: 64, // Sites
+    DigitalExperience: 65, // Digital experiences
+    NetworkBranding: 66, // Network branding
+    Network: 67, // Networks (communities)
+    EmbeddedServiceConfig: 68, // Embedded service
+    MessagingChannel: 69, // Messaging channels
+    // ========== Tier 8: Advanced Configurations (70-74) ==========
+    OmniSupervisorConfig: 70, // Omni supervisor
+    // ========== Tier 9: Security & Access - LAST (75-79) ==========
+    SharingRules: 75, // Sharing rules after everything
+    PermissionSet: 76, // Permission sets
+    MutingPermissionSet: 77, // Muting permission sets
+    PermissionSetGroup: 78, // Permission set groups
+    Profile: 79, // Profiles LAST (reference everything)
+    // ========== Tier 10: Testing & Data Packages (80-82) ==========
+    ApexTestSuite: 80, // Test suites
+    DataPackageKitDefinition: 81, // Data package kits
+    DataPackageKitObject: 82, // Data package kit objects
+});
+/**
+ * Get deployment priority for a given metadata type.
+ *
+ * **Extensibility**: Returns 99 for unknown/new metadata types (safe fallback).
+ * This ensures the plugin works with future Salesforce metadata types without updates.
+ *
+ * @param metadataType - The Salesforce metadata type
+ * @returns Priority number (1-99), or 99 (lowest priority) if type is unknown
+ *
+ * @example
+ * ```typescript
+ * const priority = getDeploymentPriority('CustomObject'); // 6
+ * const priority2 = getDeploymentPriority('ApexClass'); // 31
+ * const unknown = getDeploymentPriority('UnknownNewType'); // 99 (safe fallback)
+ * ```
+ */
+export function getDeploymentPriority(metadataType) {
+    return DEPLOYMENT_ORDER[metadataType] ?? 99; // Fallback for unknown/future types
+}
+/**
+ * Sort metadata components by deployment priority.
+ *
+ * @param components - Array of metadata type names
+ * @returns Sorted array (lowest priority number first = deploy first)
+ *
+ * @example
+ * ```typescript
+ * const sorted = sortByDeploymentOrder(['ApexClass', 'CustomObject', 'Flow']);
+ * // Result: ['CustomObject', 'ApexClass', 'Flow']
+ * ```
+ */
+export function sortByDeploymentOrder(components) {
+    return [...components].sort((a, b) => getDeploymentPriority(a) - getDeploymentPriority(b));
+}
+//# sourceMappingURL=deployment-order.js.map

package/lib/constants/deployment-order.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"deployment-order.js","sourceRoot":"","sources":["../../src/constants/deployment-order.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAIH;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAA2C,MAAM,CAAC,MAAM,CAAC;IACpF,2DAA2D;IAC3D,cAAc,EAAE,CAAC,EAAE,sCAAsC;IACzD,gBAAgB,EAAE,CAAC,EAAE,sBAAsB;IAC3C,YAAY,EAAE,CAAC,EAAE,gBAAgB;IACjC,YAAY,EAAE,CAAC,EAAE,oBAAoB;IACrC,2BAA2B,EAAE,CAAC,EAAE,kCAAkC;IAElE,qEAAqE;IACrE,YAAY,EAAE,CAAC,EAAE,kCAAkC;IACnD,aAAa,EAAE,CAAC,EAAE,wCAAwC;IAC1D,iBAAiB,EAAE,CAAC,EAAE,uBAAuB;IAC7C,cAAc,EAAE,CAAC,EAAE,wBAAwB;IAC3C,oBAAoB,EAAE,EAAE,EAAE,0BAA0B;IACpD,WAAW,EAAE,EAAE,EAAE,2BAA2B;IAC5C,iBAAiB,EAAE,EAAE,EAAE,sBAAsB;IAC7C,UAAU,EAAE,EAAE,EAAE,wCAAwC;IACxD,eAAe,EAAE,EAAE,EAAE,4CAA4C;IACjE,cAAc,EAAE,EAAE,EAAE,oCAAoC;IACxD,YAAY,EAAE,EAAE,EAAE,iBAAiB;IAEnC,4DAA4D;IAC5D,WAAW,EAAE,EAAE,EAAE,oBAAoB;IACrC,mBAAmB,EAAE,EAAE,EAAE,gBAAgB;IACzC,cAAc,EAAE,EAAE,EAAE,oBAAoB;IACxC,IAAI,EAAE,EAAE,EAAE,iBAAiB;IAC3B,aAAa,EAAE,EAAE,EAAE,kBAAkB;IACrC,KAAK,EAAE,EAAE,EAAE,gBAAgB;IAC3B,gBAAgB,EAAE,EAAE,EAAE,qBAAqB;IAC3C,kBAAkB,EAAE,EAAE,EAAE,uBAAuB;IAC/C,eAAe,EAAE,EAAE,EAAE,iCAAiC;IACtD,gBAAgB,EAAE,EAAE,EAAE,sBAAsB;IAE5C,yDAAyD;IACzD,cAAc,EAAE,EAAE,EAAE,mBAAmB;IACvC,QAAQ,EAAE,EAAE,EAAE,YAAY;IAC1B,YAAY,EAAE,EAAE,EAAE,iBAAiB;IACnC,aAAa,EAAE,EAAE,EAAE,kBAAkB;IACrC,SAAS,EAAE,EAAE,EAAE,wCAAwC;IACvD,oBAAoB,EAAE,EAAE,EAAE,gBAAgB;IAC1C,eAAe,EAAE,EAAE,EAAE,WAAW;IAChC,wBAAwB,EAAE,EAAE,EAAE,MAAM;IACpC,oBAAoB,EAAE,EAAE,EAAE,kBAAkB;IAC5C,WAAW,EAAE,EAAE,EAAE,yBAAyB;IAE1C,sDAAsD;IACtD,qBAAqB,EAAE,EAAE,EAAE,mBAAmB;IAC9C,kBAAkB,EAAE,EAAE,EAAE,kBAAkB;IAC1C,KAAK,EAAE,EAAE,EAAE,SAAS;IACpB,cAAc,EAAE,EAAE,EAAE,mBAAmB;IACvC,kBAAkB,EAAE,EAAE,EAAE,gBAAgB;IACxC,aAAa,EAAE,EAAE,EAAE,kBAAkB;IAErC,4DAA4D;IAC5D,aAAa,EAAE,EAAE,EAAE,kBAAkB;IACrC,kBAAkB,EAAE,EAAE,EAAE,wBAAwB;IAChD,aAAa,EAAE,EAAE,EAAE,wBAAwB;IAC3C,mBAAmB,EAAE,EAAE,EAAE,mBAAmB;IAC5C,kBAAkB,EAAE,EAAE,EAAE,oBAAoB;IAC5C,IAAI,EAAE,EAAE,EAAE,6BAA6B;IACvC,aAAa,EAAE,EAAE,EAAE,iBAAiB;IAEpC,sDAAsD;IACtD,MAAM,EAAE,EAAE,EAAE,eAAe;IAC3B,GAAG,EAAE,EAAE,EAAE,gBAAgB;IACzB,UAAU,EAAE,EAAE,EAAE,eAAe;IAC/B,WAAW,EAAE,EAAE,EAAE,mBAAmB;IACpC,SAAS,EAAE,EAAE,EAAE,kBAAkB;IACjC,WAAW,EAAE,EAAE,EAAE,gBAAgB;IACjC,aAAa,EAAE,EAAE,EAAE,kBAAkB;IACrC,QAAQ,EAAE,EAAE,EAAE,aAAa;IAC3B,OAAO,EAAE,EAAE,EAAE,YAAY;IACzB,YAAY,EAAE,EAAE,EAAE,iBAAiB;IACnC,mBAAmB,EAAE,EAAE,EAAE,wBAAwB;IACjD,sBAAsB,EAAE,EAAE,EAAE,uBAAuB;IAEnD,yDAAyD;IACzD,WAAW,EAAE,EAAE,EAAE,gBAAgB;IACjC,uBAAuB,EAAE,EAAE,EAAE,4BAA4B;IACzD,IAAI,EAAE,EAAE,EAAE,QAAQ;IAClB,iBAAiB,EAAE,EAAE,EAAE,sBAAsB;IAC7C,eAAe,EAAE,EAAE,EAAE,mBAAmB;IACxC,OAAO,EAAE,EAAE,EAAE,yBAAyB;IACtC,qBAAqB,EAAE,EAAE,EAAE,mBAAmB;IAC9C,gBAAgB,EAAE,EAAE,EAAE,qBAAqB;IAE3C,gEAAgE;IAChE,oBAAoB,EAAE,EAAE,EAAE,kBAAkB;IAE5C,iEAAiE;IACjE,YAAY,EAAE,EAAE,EAAE,iCAAiC;IACnD,aAAa,EAAE,EAAE,EAAE,kBAAkB;IACrC,mBAAmB,EAAE,EAAE,EAAE,yBAAyB;IAClD,kBAAkB,EAAE,EAAE,EAAE,wBAAwB;IAChD,OAAO,EAAE,EAAE,EAAE,uCAAuC;IAEpD,iEAAiE;IACjE,aAAa,EAAE,EAAE,EAAE,cAAc;IACjC,wBAAwB,EAAE,EAAE,EAAE,oBAAoB;IAClD,oBAAoB,EAAE,EAAE,EAAE,2BAA2B;CACtD,CAAC,CAAC;AAEH;;;;;;;;;;;;;;;GAeG;AACH,MAAM,UAAU,qBAAqB,CAAC,YAA0B;IAC9D,OAAO,gBAAgB,CAAC,YAAY,CAAC,IAAI,EAAE,CAAC,CAAC,oCAAoC;AACnF,CAAC;AAED;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,qBAAqB,CAAC,UAA0B;IAC9D,OAAO,CAAC,GAAG,UAAU,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,qBAAqB,CAAC,CAAC,CAAC,GAAG,qBAAqB,CAAC,CAAC,CAAC,CAAC,CAAC;AAC7F,CAAC"}

package/lib/constants/salesforce-limits.d.ts

@@ -0,0 +1,107 @@
+/**
+ * Salesforce API and Deployment Limits
+ *
+ * These are **hardcoded technical limits** from Salesforce that should NOT be configurable by users.
+ * These limits are based on official Salesforce Metadata API documentation and real-world production constraints.
+ *
+ * @see https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy.htm
+ * @see https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_size.htm
+ */
+/**
+ * Maximum number of components per deployment wave.
+ *
+ * **Real-World Limit: 300 components**
+ * - Official Salesforce API limit is 10,000 files, but UNKNOWN_EXCEPTION occurs at ~300-500 components
+ * - This is a proven safe limit based on production deployments
+ * - Exceeding this causes UNKNOWN_EXCEPTION (not API rejection)
+ * - This limit is per wave, not per deployment
+ *
+ * **Why not 10,000?**
+ * - Salesforce has undocumented transactional limits that cause UNKNOWN_EXCEPTION
+ * - Large deployments (>300 components) hit internal timeout/memory limits
+ * - 300 is the safe upper bound for reliable deployments
+ *
+ * @constant
+ * @type {number}
+ */
+export declare const MAX_COMPONENTS_PER_WAVE = 300;
+/**
+ * Maximum number of files per deployment operation.
+ *
+ * **Real-World Limit: 400-500 files**
+ * - Official Salesforce API limit is higher, but practical limit is ~400-500 files
+ * - Exceeding this causes UNKNOWN_EXCEPTION
+ * - This includes all metadata XML files and source files (Apex, LWC, static resources, etc.)
+ *
+ * @constant
+ * @type {number}
+ */
+export declare const MAX_FILES_PER_DEPLOYMENT = 500;
+/**
+ * Maximum compressed size of deployment package (ZIP).
+ *
+ * **Official Salesforce Limit: 39 MB compressed**
+ * - Applies to the ZIP file sent to Salesforce Metadata API
+ * - Exceeding this causes API rejection before deployment starts
+ * - Use this to estimate if a wave needs to be split based on size
+ *
+ * @constant
+ * @type {number}
+ */
+export declare const MAX_DEPLOYMENT_SIZE_COMPRESSED_MB = 39;
+/**
+ * Maximum uncompressed size of deployment package.
+ *
+ * **Official Salesforce Limit: 600 MB uncompressed**
+ * - Applies to the total size of all files in the deployment
+ * - Useful for pre-validation before compression
+ * - Exceeding this causes deployment failures
+ *
+ * @constant
+ * @type {number}
+ */
+export declare const MAX_DEPLOYMENT_SIZE_UNCOMPRESSED_MB = 600;
+/**
+ * Maximum number of Custom Metadata Records per deployment wave.
+ *
+ * **Why 200?**
+ * - CustomMetadataType records have a **lower transactional limit** than general metadata
+ * - Salesforce enforces ~200-250 records per transaction due to row locking
+ * - 200 is a proven safe limit in production deployments with heavy CMT usage
+ * - Exceeding this causes "UNABLE_TO_LOCK_ROW" errors, not UNKNOWN_EXCEPTION
+ *
+ * @constant
+ * @type {number}
+ */
+export declare const MAX_CMT_RECORDS_PER_WAVE = 200;
+/**
+ * Timeout for Salesforce API calls in milliseconds.
+ *
+ * **Why 10 minutes?**
+ * - Salesforce API calls can be long-running, especially for large deployments
+ * - Prevents premature timeouts for legitimate long-running operations
+ * - Aligns with common CI/CD timeout practices
+ *
+ * @constant
+ * @type {number}
+ */
+export declare const API_TIMEOUT_MS = 600000;
+/**
+ * Consolidated Salesforce Limits Object (for backward compatibility)
+ *
+ * @deprecated Use individual named exports instead (e.g., MAX_FILES_PER_DEPLOYMENT)
+ * @constant
+ * @readonly
+ */
+export declare const SALESFORCE_LIMITS: Readonly<{
+    readonly MAX_COMPONENTS_PER_WAVE: 300;
+    readonly MAX_FILES_PER_DEPLOYMENT: 500;
+    readonly MAX_DEPLOYMENT_SIZE_COMPRESSED_MB: 39;
+    readonly MAX_DEPLOYMENT_SIZE_UNCOMPRESSED_MB: 600;
+    readonly MAX_CMT_RECORDS_PER_WAVE: 200;
+    readonly API_TIMEOUT_MS: 600000;
+}>;
+/**
+ * Type helper for Salesforce Limits
+ */
+export type SalesforceLimits = typeof SALESFORCE_LIMITS;

package/lib/constants/salesforce-limits.js

@@ -0,0 +1,104 @@
+/**
+ * Salesforce API and Deployment Limits
+ *
+ * These are **hardcoded technical limits** from Salesforce that should NOT be configurable by users.
+ * These limits are based on official Salesforce Metadata API documentation and real-world production constraints.
+ *
+ * @see https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy.htm
+ * @see https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_size.htm
+ */
+/**
+ * Maximum number of components per deployment wave.
+ *
+ * **Real-World Limit: 300 components**
+ * - Official Salesforce API limit is 10,000 files, but UNKNOWN_EXCEPTION occurs at ~300-500 components
+ * - This is a proven safe limit based on production deployments
+ * - Exceeding this causes UNKNOWN_EXCEPTION (not API rejection)
+ * - This limit is per wave, not per deployment
+ *
+ * **Why not 10,000?**
+ * - Salesforce has undocumented transactional limits that cause UNKNOWN_EXCEPTION
+ * - Large deployments (>300 components) hit internal timeout/memory limits
+ * - 300 is the safe upper bound for reliable deployments
+ *
+ * @constant
+ * @type {number}
+ */
+export const MAX_COMPONENTS_PER_WAVE = 300;
+/**
+ * Maximum number of files per deployment operation.
+ *
+ * **Real-World Limit: 400-500 files**
+ * - Official Salesforce API limit is higher, but practical limit is ~400-500 files
+ * - Exceeding this causes UNKNOWN_EXCEPTION
+ * - This includes all metadata XML files and source files (Apex, LWC, static resources, etc.)
+ *
+ * @constant
+ * @type {number}
+ */
+export const MAX_FILES_PER_DEPLOYMENT = 500;
+/**
+ * Maximum compressed size of deployment package (ZIP).
+ *
+ * **Official Salesforce Limit: 39 MB compressed**
+ * - Applies to the ZIP file sent to Salesforce Metadata API
+ * - Exceeding this causes API rejection before deployment starts
+ * - Use this to estimate if a wave needs to be split based on size
+ *
+ * @constant
+ * @type {number}
+ */
+export const MAX_DEPLOYMENT_SIZE_COMPRESSED_MB = 39;
+/**
+ * Maximum uncompressed size of deployment package.
+ *
+ * **Official Salesforce Limit: 600 MB uncompressed**
+ * - Applies to the total size of all files in the deployment
+ * - Useful for pre-validation before compression
+ * - Exceeding this causes deployment failures
+ *
+ * @constant
+ * @type {number}
+ */
+export const MAX_DEPLOYMENT_SIZE_UNCOMPRESSED_MB = 600;
+/**
+ * Maximum number of Custom Metadata Records per deployment wave.
+ *
+ * **Why 200?**
+ * - CustomMetadataType records have a **lower transactional limit** than general metadata
+ * - Salesforce enforces ~200-250 records per transaction due to row locking
+ * - 200 is a proven safe limit in production deployments with heavy CMT usage
+ * - Exceeding this causes "UNABLE_TO_LOCK_ROW" errors, not UNKNOWN_EXCEPTION
+ *
+ * @constant
+ * @type {number}
+ */
+export const MAX_CMT_RECORDS_PER_WAVE = 200;
+/**
+ * Timeout for Salesforce API calls in milliseconds.
+ *
+ * **Why 10 minutes?**
+ * - Salesforce API calls can be long-running, especially for large deployments
+ * - Prevents premature timeouts for legitimate long-running operations
+ * - Aligns with common CI/CD timeout practices
+ *
+ * @constant
+ * @type {number}
+ */
+export const API_TIMEOUT_MS = 600_000; // 10 minutes
+/**
+ * Consolidated Salesforce Limits Object (for backward compatibility)
+ *
+ * @deprecated Use individual named exports instead (e.g., MAX_FILES_PER_DEPLOYMENT)
+ * @constant
+ * @readonly
+ */
+export const SALESFORCE_LIMITS = Object.freeze({
+    MAX_COMPONENTS_PER_WAVE,
+    MAX_FILES_PER_DEPLOYMENT,
+    MAX_DEPLOYMENT_SIZE_COMPRESSED_MB,
+    MAX_DEPLOYMENT_SIZE_UNCOMPRESSED_MB,
+    MAX_CMT_RECORDS_PER_WAVE,
+    API_TIMEOUT_MS,
+});
+//# sourceMappingURL=salesforce-limits.js.map

package/lib/constants/salesforce-limits.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"salesforce-limits.js","sourceRoot":"","sources":["../../src/constants/salesforce-limits.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,CAAC,MAAM,uBAAuB,GAAG,GAAG,CAAC;AAE3C;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,wBAAwB,GAAG,GAAG,CAAC;AAE5C;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,iCAAiC,GAAG,EAAE,CAAC;AAEpD;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,mCAAmC,GAAG,GAAG,CAAC;AAEvD;;;;;;;;;;;GAWG;AACH,MAAM,CAAC,MAAM,wBAAwB,GAAG,GAAG,CAAC;AAE5C;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,OAAO,CAAC,CAAC,aAAa;AAEpD;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,iBAAiB,GAAG,MAAM,CAAC,MAAM,CAAC;IAC7C,uBAAuB;IACvB,wBAAwB;IACxB,iCAAiC;IACjC,mCAAmC;IACnC,wBAAwB;IACxB,cAAc;CACN,CAAC,CAAC"}

package/lib/dependencies/circular-dependency-detector.d.ts

@@ -0,0 +1,137 @@
+/**
+ * Circular Dependency Detector
+ * Detects and reports circular dependencies in the dependency graph
+ *
+ * @ac US-030-AC-1: Detect simple cycles (A→B→A)
+ * @ac US-030-AC-2: Detect complex cycles (A→B→C→A)
+ * @ac US-030-AC-3: Report all nodes in cycle
+ * @ac US-030-AC-4: Suggest where to break cycle
+ * @ac US-030-AC-5: Support user-defined cycle breaks
+ * @ac US-030-AC-6: Handle multiple separate cycles
+ *
+ * @issue #30
+ */
+import type { NodeId, DependencyGraph, CircularDependency } from '../types/dependency.js';
+/**
+ * Cycle break suggestion
+ */
+export type CycleBreakSuggestion = {
+    from: NodeId;
+    to: NodeId;
+    reason: string;
+    priority: number;
+};
+/**
+ * Detected cycle with break suggestions
+ */
+export type DetectedCycle = CircularDependency & {
+    id: string;
+    breakSuggestions: CycleBreakSuggestion[];
+};
+/**
+ * Options for cycle detection
+ */
+export type CycleDetectionOptions = {
+    /** Maximum depth to search for cycles */
+    maxDepth?: number;
+    /** User-defined edges to ignore (cycle breaks) */
+    ignoreEdges?: Array<{
+        from: NodeId;
+        to: NodeId;
+    }>;
+    /** Generate break suggestions */
+    generateSuggestions?: boolean;
+};
+/**
+ * Circular Dependency Detector
+ *
+ * Uses depth-first search (DFS) to detect cycles in the dependency graph.
+ * Supports both simple (A→B→A) and complex (A→B→C→A) cycles.
+ *
+ * Performance: O(V + E) where V = vertices, E = edges
+ *
+ * @example
+ * const detector = new CircularDependencyDetector(graph);
+ * const cycles = detector.detectCycles();
+ * if (cycles.length > 0) {
+ *   console.log(`Found ${cycles.length} circular dependencies`);
+ *   console.log('Suggestion:', cycles[0].breakSuggestions[0]);
+ * }
+ */
+export declare class CircularDependencyDetector {
+    private graph;
+    private options;
+    private ignoredEdges;
+    constructor(graph: DependencyGraph, options?: CycleDetectionOptions);
+    /**
+     * Calculate priority for breaking an edge
+     * Higher = better candidate to break
+     */
+    private static calculateBreakPriority;
+    /**
+     * Get human-readable reason for break suggestion
+     */
+    private static getBreakReason;
+    /**
+     * Check if a class is a utility/helper class
+     */
+    private static isUtilityClass;
+    /**
+     * Check if a class is core domain logic
+     */
+    private static isCoreDomainClass;
+    /**
+     * Generate a unique ID for a cycle (order-independent)
+     */
+    private static generateCycleId;
+    /**
+     * Check if a cycle is a duplicate of already found cycles
+     */
+    private static isDuplicateCycle;
+    /**
+     * Detect all circular dependencies in the graph
+     *
+     * @ac US-030-AC-1: Detect simple cycles (A→B→A)
+     * @ac US-030-AC-2: Detect complex cycles (A→B→C→A)
+     * @ac US-030-AC-6: Handle multiple separate cycles
+     */
+    detectCycles(): DetectedCycle[];
+    /**
+     * Detect cycles starting from a specific node
+     */
+    detectCyclesFromNode(startNode: NodeId): DetectedCycle[];
+    /**
+     * Check if a specific path creates a cycle
+     */
+    wouldCreateCycle(from: NodeId, to: NodeId): boolean;
+    /**
+     * @ac US-030-AC-3: Report all nodes in cycle
+     *
+     * Create a detected cycle with full information
+     */
+    private createDetectedCycle;
+    /**
+     * @ac US-030-AC-4: Suggest where to break cycle
+     *
+     * Generate suggestions for breaking the cycle
+     * Priority based on:
+     * - Test classes (high priority to break)
+     * - Utility classes (medium priority)
+     * - Core business logic (low priority)
+     */
+    private static generateBreakSuggestions;
+    /**
+     * @ac US-030-AC-5: Support user-defined cycle breaks
+     *
+     * Check if an edge is in the ignore list
+     */
+    private isEdgeIgnored;
+    /**
+     * Get summary statistics
+     */
+    getStats(): {
+        totalNodes: number;
+        totalEdges: number;
+        ignoredEdges: number;
+    };
+}