snow-flow 2.0.5 → 2.0.7

package/dist/coordination/types.d.ts

@@ -0,0 +1,152 @@
+import { SnowAgent, TaskStatus } from '../types/snow-flow.types';
+export interface CoordinationResult {
+    success: boolean;
+    results: Record<string, any>;
+    metrics: ExecutionMetrics;
+    errors: Error[];
+    warnings: string[];
+}
+export interface ExecutionMetrics {
+    totalTasks: number;
+    completedTasks: number;
+    failedTasks: number;
+    totalExecutionTime: number;
+    averageTaskTime: number;
+    concurrentTasks: number;
+}
+export interface TaskSpecification {
+    name: string;
+    description: string;
+    tasks: TaskDefinition[];
+    sharedContext: Record<string, any>;
+    qualityGates: QualityGateConfig[];
+    executionPattern?: 'sequential' | 'parallel' | 'hybrid';
+}
+export interface TaskDefinition {
+    id: string;
+    name: string;
+    description: string;
+    agentType: string;
+    requirements: TaskRequirements;
+    dependencies: string[];
+    outputs: string[];
+    priority: 'low' | 'medium' | 'high' | 'critical';
+    estimatedDuration?: number;
+    maxRetries?: number;
+}
+export interface TaskRequirements {
+    inputs: Record<string, any>;
+    outputs: string[];
+    capabilities: string[];
+    resources?: ResourceRequirement[];
+    constraints?: Constraint[];
+}
+export interface ResourceRequirement {
+    type: 'memory' | 'compute' | 'servicenow_access' | 'external_api';
+    amount?: number;
+    metadata?: Record<string, any>;
+}
+export interface Constraint {
+    type: 'time' | 'resource' | 'dependency' | 'quality';
+    value: any;
+    description: string;
+}
+export interface TaskNode {
+    id: string;
+    agent: SnowAgent;
+    requirements: TaskRequirements;
+    status: TaskStatus;
+    result: any;
+    error?: Error;
+    startTime?: Date;
+    endTime?: Date;
+    retryCount: number;
+    qualityGateResults?: QualityGateResult[];
+}
+export interface AgentSubscriber {
+    agent: SnowAgent;
+    callback: (key: string, value: any) => Promise<void>;
+}
+export interface QualityGateConfig {
+    name: string;
+    taskIds: string[];
+    gates: QualityGate[];
+}
+export interface QualityGate {
+    name: string;
+    blocking: boolean;
+    validate(result: any): Promise<ValidationResult>;
+}
+export interface ValidationResult {
+    passed: boolean;
+    score?: number;
+    error?: string;
+    warnings?: string[];
+    suggestions?: string[];
+    metadata?: Record<string, any>;
+}
+export interface QualityGateResult {
+    gateName: string;
+    passed: boolean;
+    blocking: boolean;
+    validations: ValidationResult[];
+    overallScore?: number;
+    executionTime: number;
+}
+export interface ProgressStatus {
+    total: number;
+    completed: number;
+    failed: number;
+    inProgress: number;
+    percentage: number;
+    estimated_completion?: Date;
+    currentPhase?: string;
+    bottlenecks?: string[];
+}
+export interface ProgressListener {
+    onProgress(event: string, data: any): void;
+}
+export interface ExecutionPlan {
+    phases: ExecutionPhase[];
+    totalEstimatedTime: number;
+    criticalPath: string[];
+    parallelizationOpportunities: ParallelGroup[];
+}
+export interface ExecutionPhase {
+    id: string;
+    type: 'sequential' | 'parallel';
+    tasks: string[];
+    estimatedDuration: number;
+    dependencies: string[];
+}
+export interface ParallelGroup {
+    tasks: string[];
+    estimatedSavings: number;
+    riskLevel: 'low' | 'medium' | 'high';
+}
+export interface BaseTeam {
+    agents: Map<string, SnowAgent>;
+    getAgent(id: string): SnowAgent | undefined;
+    addAgent(agent: SnowAgent): void;
+    removeAgent(id: string): void;
+    getAvailableAgents(): SnowAgent[];
+    getAgentsByType(type: string): SnowAgent[];
+}
+export interface MemoryValue {
+    value: any;
+    timestamp: number;
+    version: number;
+    metadata?: Record<string, any>;
+}
+export interface CoordinationConfig {
+    maxConcurrentTasks: number;
+    taskTimeout: number;
+    enableRetries: boolean;
+    maxRetries: number;
+    enableQualityGates: boolean;
+    enableProgressMonitoring: boolean;
+    executionPattern: 'sequential' | 'parallel' | 'hybrid' | 'auto';
+    memoryTtl: number;
+    errorRecoveryStrategy: 'abort' | 'continue' | 'retry';
+}
+//# sourceMappingURL=types.d.ts.map

package/dist/coordination/types.js

@@ -0,0 +1,3 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+//# sourceMappingURL=types.js.map

package/dist/memory/memory-system.d.ts

@@ -139,6 +139,7 @@ export declare class MemorySystem extends EventEmitter {
      * Private helper methods
      */
     private createCoreTables;
+    private runCriticalMigrations;
     private runMigrations;
     private startCleanupTimer;
     private cleanup;

package/dist/memory/memory-system.js

@@ -172,7 +172,9 @@ class MemorySystem extends events_1.EventEmitter {
         this.db.pragma('synchronous = NORMAL');
         // Create core tables
         await this.createCoreTables();
-        // Run migrations if needed
+        // Always run critical migrations (like missing metadata column)
+        await this.runCriticalMigrations();
+        // Run optional migrations if needed
         if (this.options.schema?.autoMigrate) {
             await this.runMigrations();
         }
@@ -362,7 +364,8 @@ class MemorySystem extends events_1.EventEmitter {
         ttl INTEGER,
         expires_at INTEGER,
         created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
-        updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
+        updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+        metadata TEXT DEFAULT '{}'
       );
       
       CREATE INDEX IF NOT EXISTS idx_memory_expires ON memory_store(expires_at);
@@ -483,6 +486,22 @@ class MemorySystem extends events_1.EventEmitter {
       CREATE INDEX IF NOT EXISTS idx_perf_success_time ON performance_metrics(success, created_at);
     `);
     }
+    async runCriticalMigrations() {
+        // Critical migrations that must always run
+        try {
+            // Fix for missing metadata column
+            const tableInfo = this.db.prepare("PRAGMA table_info(memory_store)").all();
+            const hasMetadataColumn = tableInfo.some((col) => col.name === 'metadata');
+            if (!hasMetadataColumn) {
+                this.logger.info('Running critical migration: Adding metadata column to memory_store table...');
+                this.db.exec("ALTER TABLE memory_store ADD COLUMN metadata TEXT DEFAULT '{}'");
+                this.logger.info('Critical migration completed: Metadata column added successfully');
+            }
+        }
+        catch (error) {
+            this.logger.warn('Could not complete critical migrations:', error);
+        }
+    }
     async runMigrations() {
         // Implement schema migrations if needed
         this.logger.info('Running database migrations...');

package/memory/claude-flow-data.json

@@ -0,0 +1,5 @@
+{
+  "agents": [],
+  "tasks": [],
+  "lastUpdated": 1754038214952
+}

package/memory/servicenow_artifacts/000d9224c895221055906c7518aa2d3d.json

@@ -0,0 +1,30 @@
+{
+  "meta": {
+    "sys_id": "000d9224c895221055906c7518aa2d3d",
+    "name": "open_nlu_predict_log0001",
+    "type": "sys_db_object",
+    "last_updated": "2025-05-01 00:51:23"
+  },
+  "structure": {
+    "type": "unknown",
+    "components": []
+  },
+  "context": {
+    "usage": "Context analysis would determine usage patterns",
+    "dependencies": "Related artifacts would be identified here",
+    "impact": "Impact analysis would be performed here"
+  },
+  "relationships": {
+    "relatedArtifacts": [],
+    "dependencies": [],
+    "usage": []
+  },
+  "claudeSummary": "open_nlu_predict_log0001 is a sys_db_object in ServiceNow. It can be modified using natural language instructions through Snow-Flow.",
+  "modificationPoints": [
+    {
+      "location": "main_configuration",
+      "type": "modify_settings",
+      "description": "Main configuration can be modified"
+    }
+  ]
+}

package/memory/servicenow_artifacts/0196b66173303010e46b4a2214f6a7a2.json

@@ -0,0 +1,36 @@
+{
+  "meta": {
+    "sys_id": "0196b66173303010e46b4a2214f6a7a2",
+    "name": "Flow Template Subflow",
+    "type": "sys_hub_flow",
+    "last_updated": "2021-09-29 04:49:06"
+  },
+  "structure": {
+    "type": "flow",
+    "components": {
+      "name": "Flow Template Subflow",
+      "description": "",
+      "active": "false",
+      "trigger": "Unknown trigger",
+      "steps": "Flow definition analysis would go here"
+    }
+  },
+  "context": {
+    "usage": "Context analysis would determine usage patterns",
+    "dependencies": "Related artifacts would be identified here",
+    "impact": "Impact analysis would be performed here"
+  },
+  "relationships": {
+    "relatedArtifacts": [],
+    "dependencies": [],
+    "usage": []
+  },
+  "claudeSummary": "Flow Template Subflow is a sys_hub_flow in ServiceNow. It can be modified using natural language instructions through Snow-Flow.",
+  "modificationPoints": [
+    {
+      "location": "main_configuration",
+      "type": "modify_settings",
+      "description": "Main configuration can be modified"
+    }
+  ]
+}

package/memory/servicenow_artifacts/125e5d1d837e2a102a7ea130ceaad397.json

@@ -0,0 +1,30 @@
+{
+  "meta": {
+    "sys_id": "125e5d1d837e2a102a7ea130ceaad397",
+    "name": "iPhone 6 Request Approval Flow",
+    "type": "wf_workflow",
+    "last_updated": "2025-07-16 17:47:17"
+  },
+  "structure": {
+    "type": "unknown",
+    "components": []
+  },
+  "context": {
+    "usage": "Context analysis would determine usage patterns",
+    "dependencies": "Related artifacts would be identified here",
+    "impact": "Impact analysis would be performed here"
+  },
+  "relationships": {
+    "relatedArtifacts": [],
+    "dependencies": [],
+    "usage": []
+  },
+  "claudeSummary": "iPhone 6 Request Approval Flow is a wf_workflow in ServiceNow. It can be modified using natural language instructions through Snow-Flow.",
+  "modificationPoints": [
+    {
+      "location": "main_configuration",
+      "type": "modify_settings",
+      "description": "Main configuration can be modified"
+    }
+  ]
+}

package/memory/servicenow_artifacts/7637c1f2b7112210a5e5911cde11a972.json

@@ -0,0 +1,30 @@
+{
+  "meta": {
+    "sys_id": "7637c1f2b7112210a5e5911cde11a972",
+    "name": "Prevent invalid language code",
+    "type": "sys_script",
+    "last_updated": "2025-05-18 23:10:10"
+  },
+  "structure": {
+    "type": "unknown",
+    "components": []
+  },
+  "context": {
+    "usage": "Context analysis would determine usage patterns",
+    "dependencies": "Related artifacts would be identified here",
+    "impact": "Impact analysis would be performed here"
+  },
+  "relationships": {
+    "relatedArtifacts": [],
+    "dependencies": [],
+    "usage": []
+  },
+  "claudeSummary": "Prevent invalid language code is a sys_script in ServiceNow. It can be modified using natural language instructions through Snow-Flow.",
+  "modificationPoints": [
+    {
+      "location": "main_configuration",
+      "type": "modify_settings",
+      "description": "Main configuration can be modified"
+    }
+  ]
+}

package/memory/servicenow_artifacts/default_documentation_tables_1754056582292.json

@@ -0,0 +1,55 @@
+{
+  "key": "default:documentation_tables_1754056582292",
+  "data": {
+    "generation_metadata": {
+      "timestamp": "2025-08-01T13:56:22.292Z",
+      "execution_time_ms": 14,
+      "scope": [
+        "tables"
+      ],
+      "format": "markdown",
+      "audience_level": "mixed",
+      "objects_documented": 1,
+      "auto_update_enabled": false
+    },
+    "discovered_objects": [
+      {
+        "type": "table",
+        "name": "incident",
+        "label": "Incident",
+        "description": "Incident management table",
+        "sys_id": "incident_table_id"
+      }
+    ],
+    "documentation_content": {
+      "format": "markdown",
+      "content": "# ServiceNow tables Documentation\n\n*Generated on: 8/1/2025*\n*Objects documented: 1*\n\n## Table of Contents\n\n- [Executive Summary](#executive-summary)\n- [Architecture Overview](#architecture-overview)\n- [table: incident](#table:-incident)\n- [Best Practices and Recommendations](#best-practices-and-recommendations)\n\n\n## Executive Summary\n\nThis documentation covers 1 ServiceNow objects across multiple categories: 1 table.\n\n### Scope:\n- **Documentation Type**: undefined level\n- **Format**: markdown\n- **Coverage**: tables\n- **Generated**: 8/1/2025\n\n### Key Highlights:\n- Comprehensive coverage of core system components\n- Detailed technical specifications and usage guidelines\n- Best practices and recommendations for optimal implementation\n- Architecture diagrams and relationship mappings\n- API documentation not included\n\n### Audience:\nThis documentation is designed for both technical and business stakeholders.\n    \n\n\n## incident\n\n**Type**: table\n**Description**: Incident management table\n\n**System ID**: incident_table_id\n\n### Overview\nIncident management table\n\n### Table Structure\n\n## Incident\n\n**Table Name:** incident\n**Description:** Incident management table\n**Type:** Core ServiceNow Table\n\n### Key Characteristics:\n- Primary table for incident records\n- Extends: task (if applicable)\n- Access controlled by ACLs\n- Supports workflows and business rules\n    \n\n### Field Definitions\n\n### Core Fields:\n- **sys_id**: Unique identifier (32-character GUID)\n- **number**: Auto-generated record number\n- **state**: Current state of the record\n- **priority**: Priority level (1-5)\n- **assigned_to**: User assigned to handle the record\n- **short_description**: Brief description of the issue/request\n- **description**: Detailed description\n\n### Custom Fields:\n_(Document any custom fields added to this table)_\n    \n\n### Relationships\n\n### Parent-Child Relationships:\n- Extends: task table (inherits all task fields)\n- Child tables: None\n\n### Reference Relationships:\n- assigned_to → sys_user\n- caller_id → sys_user (if applicable)\n- cmdb_ci → cmdb_ci (if applicable)\n\n### Related Lists:\n- Approvals\n- Activities (work notes, comments)\n- Attachments\n    \n\n### Dependencies\n- **sys_user** (table): references\n- **task** (table): extends\n- **approval_workflow** (workflow): triggers\n\n### Usage Patterns\n**High Volume Usage**: This object is accessed frequently during business hours\n*Recommendation: Consider performance optimization for peak times*\n\n**Integration Dependency**: Relies on external system integration\n*Recommendation: Ensure proper error handling for integration failures*\n\n### Best Practices\n- Always validate required fields before saving\n- Use proper ACLs to control access\n- Consider performance impact of large datasets\n- Document any custom fields and their purpose\n\n\n\n\n## Best Practices and Recommendations\n\n### General Guidelines:\n- Follow ServiceNow best practices for development and configuration\n- Use proper naming conventions for all objects\n- Document all customizations and configurations\n- Test thoroughly in development before deploying to production\n- Implement proper error handling and logging\n\n### Performance Considerations:\n- Optimize database queries and avoid N+1 query patterns\n- Use appropriate indexes for frequently queried fields\n- Consider caching for frequently accessed data\n- Monitor system performance and resource usage\n\n### Security Best Practices:\n- Implement proper access controls using ACLs\n- Follow principle of least privilege for user permissions\n- Validate all user inputs to prevent security vulnerabilities\n- Regularly review and audit security configurations\n\n### Maintenance and Support:\n- Keep documentation up to date with system changes\n- Implement proper version control for customizations\n- Plan for regular maintenance windows and updates\n- Establish monitoring and alerting for critical processes\n\n### Integration Guidelines:\n- Use standard ServiceNow APIs where possible\n- Implement proper error handling for external integrations\n- Document all integration points and data flows\n- Test integrations thoroughly including failure scenarios\n    \n\n",
+      "filename": "ServiceNow_tables_Documentation.md"
+    },
+    "diagrams": null,
+    "api_documentation": null,
+    "auto_update_config": null,
+    "statistics": {
+      "total_objects": 1,
+      "content_sections": 3,
+      "diagrams_generated": 0,
+      "api_endpoints_documented": 0,
+      "total_words": 538,
+      "estimated_reading_time_minutes": 3
+    },
+    "quality_metrics": {
+      "completeness_score": 60,
+      "accuracy_score": 100,
+      "readability_score": 25,
+      "coverage_percentage": 100
+    }
+  },
+  "timestamp": 1754056582292,
+  "ttl": 604800000,
+  "tags": [],
+  "metadata": {
+    "creator": "ServiceNowAdvancedFeaturesMCP",
+    "version": "1.0.0",
+    "description": "Cached data for key: documentation_tables_1754056582292"
+  }
+}

package/memory/servicenow_artifacts/default_documentation_tables_1754057477189.json

@@ -0,0 +1,55 @@
+{
+  "key": "default:documentation_tables_1754057477189",
+  "data": {
+    "generation_metadata": {
+      "timestamp": "2025-08-01T14:11:17.189Z",
+      "execution_time_ms": 14,
+      "scope": [
+        "tables"
+      ],
+      "format": "markdown",
+      "audience_level": "mixed",
+      "objects_documented": 1,
+      "auto_update_enabled": false
+    },
+    "discovered_objects": [
+      {
+        "type": "table",
+        "name": "incident",
+        "label": "Incident",
+        "description": "Incident management table",
+        "sys_id": "incident_table_id"
+      }
+    ],
+    "documentation_content": {
+      "format": "markdown",
+      "content": "# ServiceNow tables Documentation\n\n*Generated on: 8/1/2025*\n*Objects documented: 1*\n\n## Table of Contents\n\n- [Executive Summary](#executive-summary)\n- [Architecture Overview](#architecture-overview)\n- [table: incident](#table:-incident)\n- [Best Practices and Recommendations](#best-practices-and-recommendations)\n\n\n## Executive Summary\n\nThis documentation covers 1 ServiceNow objects across multiple categories: 1 table.\n\n### Scope:\n- **Documentation Type**: undefined level\n- **Format**: markdown\n- **Coverage**: tables\n- **Generated**: 8/1/2025\n\n### Key Highlights:\n- Comprehensive coverage of core system components\n- Detailed technical specifications and usage guidelines\n- Best practices and recommendations for optimal implementation\n- Architecture diagrams and relationship mappings\n- API documentation not included\n\n### Audience:\nThis documentation is designed for both technical and business stakeholders.\n    \n\n\n## incident\n\n**Type**: table\n**Description**: Incident management table\n\n**System ID**: incident_table_id\n\n### Overview\nIncident management table\n\n### Table Structure\n\n## Incident\n\n**Table Name:** incident\n**Description:** Incident management table\n**Type:** Core ServiceNow Table\n\n### Key Characteristics:\n- Primary table for incident records\n- Extends: task (if applicable)\n- Access controlled by ACLs\n- Supports workflows and business rules\n    \n\n### Field Definitions\n\n### Core Fields:\n- **sys_id**: Unique identifier (32-character GUID)\n- **number**: Auto-generated record number\n- **state**: Current state of the record\n- **priority**: Priority level (1-5)\n- **assigned_to**: User assigned to handle the record\n- **short_description**: Brief description of the issue/request\n- **description**: Detailed description\n\n### Custom Fields:\n_(Document any custom fields added to this table)_\n    \n\n### Relationships\n\n### Parent-Child Relationships:\n- Extends: task table (inherits all task fields)\n- Child tables: None\n\n### Reference Relationships:\n- assigned_to → sys_user\n- caller_id → sys_user (if applicable)\n- cmdb_ci → cmdb_ci (if applicable)\n\n### Related Lists:\n- Approvals\n- Activities (work notes, comments)\n- Attachments\n    \n\n### Dependencies\n- **sys_user** (table): references\n- **task** (table): extends\n- **approval_workflow** (workflow): triggers\n\n### Usage Patterns\n**High Volume Usage**: This object is accessed frequently during business hours\n*Recommendation: Consider performance optimization for peak times*\n\n**Integration Dependency**: Relies on external system integration\n*Recommendation: Ensure proper error handling for integration failures*\n\n### Best Practices\n- Always validate required fields before saving\n- Use proper ACLs to control access\n- Consider performance impact of large datasets\n- Document any custom fields and their purpose\n\n\n\n\n## Best Practices and Recommendations\n\n### General Guidelines:\n- Follow ServiceNow best practices for development and configuration\n- Use proper naming conventions for all objects\n- Document all customizations and configurations\n- Test thoroughly in development before deploying to production\n- Implement proper error handling and logging\n\n### Performance Considerations:\n- Optimize database queries and avoid N+1 query patterns\n- Use appropriate indexes for frequently queried fields\n- Consider caching for frequently accessed data\n- Monitor system performance and resource usage\n\n### Security Best Practices:\n- Implement proper access controls using ACLs\n- Follow principle of least privilege for user permissions\n- Validate all user inputs to prevent security vulnerabilities\n- Regularly review and audit security configurations\n\n### Maintenance and Support:\n- Keep documentation up to date with system changes\n- Implement proper version control for customizations\n- Plan for regular maintenance windows and updates\n- Establish monitoring and alerting for critical processes\n\n### Integration Guidelines:\n- Use standard ServiceNow APIs where possible\n- Implement proper error handling for external integrations\n- Document all integration points and data flows\n- Test integrations thoroughly including failure scenarios\n    \n\n",
+      "filename": "ServiceNow_tables_Documentation.md"
+    },
+    "diagrams": null,
+    "api_documentation": null,
+    "auto_update_config": null,
+    "statistics": {
+      "total_objects": 1,
+      "content_sections": 3,
+      "diagrams_generated": 0,
+      "api_endpoints_documented": 0,
+      "total_words": 538,
+      "estimated_reading_time_minutes": 3
+    },
+    "quality_metrics": {
+      "completeness_score": 60,
+      "accuracy_score": 100,
+      "readability_score": 25,
+      "coverage_percentage": 100
+    }
+  },
+  "timestamp": 1754057477189,
+  "ttl": 604800000,
+  "tags": [],
+  "metadata": {
+    "creator": "ServiceNowAdvancedFeaturesMCP",
+    "version": "1.0.0",
+    "description": "Cached data for key: documentation_tables_1754057477189"
+  }
+}

package/memory/sessions/README.md

@@ -0,0 +1,32 @@
+# Session Memory Storage
+
+## Purpose
+This directory stores session-based memory data, conversation history, and contextual information for development sessions using the Claude-Flow orchestration system.
+
+## Structure
+Sessions are organized by date and session ID for easy retrieval:
+
+```
+memory/sessions/
+├── 2024-01-10/
+│   ├── session_001/
+│   │   ├── metadata.json        # Session metadata and configuration
+│   │   ├── conversation.md      # Full conversation history
+│   │   ├── decisions.md         # Key decisions and rationale
+│   │   ├── artifacts/           # Generated files and outputs
+│   │   └── coordination_state/  # Coordination system snapshots
+│   └── ...
+└── shared/
+    ├── patterns.md              # Common session patterns
+    └── templates/               # Session template files
+```
+
+## Usage Guidelines
+1. **Session Isolation**: Each session gets its own directory
+2. **Metadata Completeness**: Always fill out session metadata
+3. **Conversation Logging**: Document all significant interactions
+4. **Artifact Organization**: Structure generated files clearly
+5. **State Preservation**: Snapshot coordination state regularly
+
+## Last Updated
+2025-08-01T08:50:14.952Z

package/memory/update-set-sessions/01f82af583faea102a7ea130ceaad3d4.json

@@ -0,0 +1,9 @@
+{
+  "update_set_id": "01f82af583faea102a7ea130ceaad3d4",
+  "name": "iPhone 6 Approval Flow",
+  "description": "Flow to check if request is for iPhone 6 and require admin approval for such requests",
+  "user_story": "FLOW-001",
+  "created_at": "2025-07-18T12:30:12.807Z",
+  "state": "in_progress",
+  "artifacts": []
+}

package/memory/update-set-sessions/27718fb983faea102a7ea130ceaad34b.json

@@ -0,0 +1,9 @@
+{
+  "update_set_id": "27718fb983faea102a7ea130ceaad34b",
+  "name": "iPhone 6 Approval Flow",
+  "description": "Flow to require admin approval for iPhone 6 requests. Includes condition checking, approval routing, and notifications for approval/rejection.",
+  "user_story": "FLOW-001",
+  "created_at": "2025-07-18T14:17:25.143Z",
+  "state": "in_progress",
+  "artifacts": []
+}

package/memory/update-set-sessions/412e9bf6833e22502a7ea130ceaad30a.json

@@ -0,0 +1,8 @@
+{
+  "update_set_id": "412e9bf6833e22502a7ea130ceaad30a",
+  "name": "Auto-HTTP request tracking development (2025-07-21 18:56)",
+  "description": "Automatically created Update Set for HTTP request tracking development",
+  "created_at": "2025-07-21 18:56:29",
+  "state": "in progress",
+  "artifacts": []
+}

package/memory/update-set-sessions/66fc5a79837aea102a7ea130ceaad3ab.json

@@ -0,0 +1,9 @@
+{
+  "update_set_id": "66fc5a79837aea102a7ea130ceaad3ab",
+  "name": "iPhone 6 Admin Approval Flow",
+  "description": "Flow to check if a request is for iPhone 6 and route to admin approval if true. Includes flow designer workflow, approval configurations, and notification templates.",
+  "user_story": "REQ-001",
+  "created_at": "2025-07-18T11:37:52.906Z",
+  "state": "in_progress",
+  "artifacts": []
+}

package/memory/update-set-sessions/71a30ff5837eea102a7ea130ceaad37f.json

@@ -0,0 +1,9 @@
+{
+  "update_set_id": "71a30ff5837eea102a7ea130ceaad37f",
+  "name": "iPhone 6 Approval Flow",
+  "description": "Flow to check for iPhone 6 requests and require admin approval. Includes flow design, approval routing, and notifications.",
+  "user_story": "TASK-001",
+  "created_at": "2025-07-18T14:26:50.683Z",
+  "state": "in_progress",
+  "artifacts": []
+}

package/memory/update-set-sessions/74fba27983faea102a7ea130ceaad3bd.json

@@ -0,0 +1,9 @@
+{
+  "update_set_id": "74fba27983faea102a7ea130ceaad3bd",
+  "name": "iPhone 6 Approval Flow",
+  "description": "Implementation of approval flow for iPhone 6 requests. When a request is for an iPhone 6, it requires admin approval before proceeding.",
+  "user_story": "FLOW-001",
+  "created_at": "2025-07-18T12:43:17.671Z",
+  "state": "in_progress",
+  "artifacts": []
+}

package/memory/update-set-sessions/a0b147b5837eea102a7ea130ceaad344.json

@@ -0,0 +1,58 @@
+{
+  "update_set_id": "a0b147b5837eea102a7ea130ceaad344",
+  "name": "iPhone 6 Testing - Flow Validation",
+  "description": "Testing and validation of iPhone 6 approval flow functionality including detection logic, approval routing, notifications, and edge cases",
+  "user_story": "TEST-001",
+  "created_at": "2025-07-18T14:18:18.118Z",
+  "state": "complete",
+  "artifacts": [
+    {
+      "type": "business_rule",
+      "sys_id": "07e18bb5837eea102a7ea130ceaad330",
+      "name": "iPhone 6 Test Request Creator",
+      "created_at": "2025-07-18T14:19:22.675Z"
+    },
+    {
+      "type": "script_include",
+      "sys_id": "89128fb5837eea102a7ea130ceaad312",
+      "name": "iPhone6ApprovalFlowTester",
+      "created_at": "2025-07-18T14:20:04.704Z"
+    },
+    {
+      "type": "ui_action",
+      "sys_id": "6b228fb5837eea102a7ea130ceaad31a",
+      "name": "Run iPhone 6 Flow Tests",
+      "created_at": "2025-07-18T14:20:27.725Z"
+    },
+    {
+      "type": "business_rule",
+      "sys_id": "ba3243f5837eea102a7ea130ceaad39d",
+      "name": "iPhone 6 Approval Routing Test",
+      "created_at": "2025-07-18T14:20:58.345Z"
+    },
+    {
+      "type": "notification",
+      "sys_id": "c94243f5837eea102a7ea130ceaad3a5",
+      "name": "iPhone 6 Approval Required",
+      "created_at": "2025-07-18T14:21:02.112Z"
+    },
+    {
+      "type": "notification",
+      "sys_id": "3a4283f5837eea102a7ea130ceaad342",
+      "name": "iPhone 6 Request Submitted",
+      "created_at": "2025-07-18T14:21:06.169Z"
+    },
+    {
+      "type": "script_include",
+      "sys_id": "117247b5837eea102a7ea130ceaad3a6",
+      "name": "iPhone6EdgeCaseTester",
+      "created_at": "2025-07-18T14:22:54.361Z"
+    },
+    {
+      "type": "script_include",
+      "sys_id": "86b283f5837eea102a7ea130ceaad33a",
+      "name": "iPhone6TestReportGenerator",
+      "created_at": "2025-07-18T14:22:57.448Z"
+    }
+  ]
+}

package/memory/update-set-sessions/b13f5eb983baea102a7ea130ceaad33e.json

@@ -0,0 +1,9 @@
+{
+  "update_set_id": "b13f5eb983baea102a7ea130ceaad33e",
+  "name": "iPhone 6 Admin Approval Flow",
+  "description": "Implements a flow that checks if a service catalog request is for an iPhone 6. If it is, the request requires admin approval before proceeding.",
+  "user_story": "REQ-001",
+  "created_at": "2025-07-18T11:47:39.398Z",
+  "state": "in_progress",
+  "artifacts": []
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "snow-flow",
-  "version": "2.0.5",
+  "version": "2.0.7",
   "description": "Snow-Flow: ServiceNow Advanced Intelligence Platform - 100+ real MCP tools with AI-powered swarm orchestration. Zero Mock Data, 100% Real API Integration. Natural language interface for ServiceNow operations.",
   "main": "dist/index.js",
   "type": "commonjs",

package/reports/swarm-auto-centralized-1752649029776.json

@@ -0,0 +1,13 @@
+{
+  "objective": "create a multi agent implementation of claude-flow for a servicenow instance. As in the way that we do exactly the same as what claude-flow already does, multi agent orchestration of claude-code, but then for SerivceNow, for example I want that this cmd: [snow-flow swarm 'create a widget for X'] a multi agent orchestration spawns with multiple agents that would create a widget in servicenow, or anything ofcourse. We should look at claude-flows github and should duplicate as best as we could to get this product: https://github.com/ruvnet/claude-flow - this would be called snow-flow as a reference to servicenow that everyone calls snow wrongly and flow as in claude-flow. Just like claude-flow this snow-flow would live in the cli, orchestrating claude-code how to build, but then it would be always pointed towards servicenow. The user should give their OAuth or basic authentication and should be able to, kist like claude-flow, use their claude-code subscription to save on token costs. Claude-flow only orchestrates, claude-code creates so its important that we keep that aspect of the tool",
+  "strategy": "auto",
+  "mode": "centralized",
+  "maxAgents": 5,
+  "timeout": 60,
+  "parallel": false,
+  "monitor": false,
+  "output": "json",
+  "outputDir": "./reports",
+  "timestamp": "2025-07-16T06:57:09.774Z",
+  "id": "swarm-auto-centralized-1752649029776"
+}