snow-flow 3.0.9 → 3.0.10

package/memory/servicenow_artifacts/default_documentation_tables_1754056582292.json

@@ -1,55 +0,0 @@
-{
-  "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

@@ -1,55 +0,0 @@
-{
-  "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/update-set-sessions/01f82af583faea102a7ea130ceaad3d4.json

@@ -1,9 +0,0 @@
-{
-  "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

@@ -1,9 +0,0 @@
-{
-  "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

@@ -1,8 +0,0 @@
-{
-  "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

@@ -1,9 +0,0 @@
-{
-  "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

@@ -1,9 +0,0 @@
-{
-  "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

@@ -1,9 +0,0 @@
-{
-  "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

@@ -1,58 +0,0 @@
-{
-  "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

@@ -1,9 +0,0 @@
-{
-  "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/reports/swarm-auto-centralized-1752649029776.json

@@ -1,13 +0,0 @@
-{
-  "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"
-}

package/src/memory/README.md

@@ -1,240 +0,0 @@
-# Snow-Flow Memory System
-
-The Snow-Flow memory system provides SQLite-based persistent storage for agent coordination, artifact tracking, and performance monitoring. It's designed to meet the requirements specified in MCP_ARCHITECTURE.md with fast queries (<100ms), thread-safe operations, and automatic schema migration.
-
-## Architecture
-
-The memory system consists of three main components:
-
-### 1. SwarmMemory (`swarm-memory.ts`)
-- Core SQLite database management
-- Schema creation and migration
-- Performance optimization
-- Thread-safe operations with WAL mode
-
-### 2. MemoryOperations (`memory-operations.ts`)
-- High-level operations for data storage/retrieval
-- Agent coordination management
-- Artifact tracking
-- Performance monitoring
-- Message passing between agents
-
-### 3. MemoryClient (`memory-client.ts`)
-- Simple API for agents
-- Automatic session tracking
-- Performance tracking helpers
-- Simplified context storage
-
-## Database Schema
-
-The system implements all tables specified in MCP_ARCHITECTURE.md:
-
-- **agent_coordination**: Track agent status and progress
-- **servicenow_artifacts**: Store created artifacts
-- **agent_messages**: Inter-agent communication
-- **shared_context**: Session-wide shared data
-- **deployment_history**: Track deployments
-- **agent_dependencies**: Manage agent dependencies
-- **performance_metrics**: Performance monitoring
-
-## Usage
-
-### Basic Agent Usage
-
-```typescript
-import { MemoryClient } from './memory/index.js';
-
-// Create a memory client for an agent
-const memory = MemoryClient.forAgent(
-  'widget_creator_001',  // agent ID
-  'widget-creator',      // agent type
-  'session_123'          // session ID
-);
-
-// Register the agent
-await memory.register(['create_dashboard_widget']);
-
-// Update progress
-await memory.updateProgress(50, 'creating_template');
-
-// Store shared data
-await memory.store({
-  key: 'widget_config',
-  value: {
-    name: 'incident_dashboard',
-    features: ['charts', 'filters']
-  }
-});
-
-// Retrieve shared data
-const config = await memory.retrieve({ key: 'widget_config' });
-
-// Track performance
-const tracker = memory.trackOperation('widget_creation');
-// ... do work ...
-await tracker.complete(true);
-
-// Mark as completed
-await memory.complete();
-```
-
-### Artifact Management
-
-```typescript
-// Store artifact information
-await memory.storeArtifact({
-  sys_id: 'widget_12345',
-  type: 'widget',
-  name: 'Incident Dashboard',
-  status: 'created',
-  metadata: { version: '1.0' }
-});
-
-// Update artifact status
-await memory.updateArtifactStatus('widget_12345', 'deployed');
-
-// Find artifacts
-const widgets = await memory.findSessionArtifacts('widget');
-```
-
-### Agent Communication
-
-```typescript
-// Send handoff to another agent
-await memory.handoff({
-  to_agent: 'ui_specialist_001',
-  artifact_reference: 'widget_12345',
-  data: {
-    template_ready: true,
-    next_steps: ['add_styling', 'test_responsiveness']
-  }
-});
-
-// Check for incoming handoffs
-const handoffs = await memory.checkHandoffs();
-for (const handoff of handoffs) {
-  console.log(`Received from ${handoff.from}:`, handoff.data);
-}
-
-// Report dependency ready
-await memory.reportDependencyReady('test_agent_001', 'widget_12345');
-```
-
-### Performance Monitoring
-
-```typescript
-// Track operation performance
-const tracker = memory.trackOperation('api_call');
-try {
-  // ... perform operation ...
-  await tracker.complete(true, undefined, { 
-    response_time: 150,
-    records_processed: 100 
-  });
-} catch (error) {
-  await tracker.complete(false, error.message);
-}
-
-// Get performance statistics
-const stats = await memory.getPerformanceStats('api_call');
-console.log(`Average duration: ${stats.avgDuration}ms`);
-console.log(`Success rate: ${stats.successRate * 100}%`);
-```
-
-### Session Management
-
-```typescript
-// Get complete session state
-const state = await memory.getSessionState();
-console.log('Active agents:', state.agents);
-console.log('Created artifacts:', state.artifacts);
-console.log('Performance summary:', state.performanceSummary);
-
-// Clean up session when done
-await memory.cleanup();
-```
-
-## Advanced Usage
-
-### Direct Database Access
-
-For custom queries, you can access the underlying database:
-
-```typescript
-const db = memory.getDatabase();
-const results = db.all(`
-  SELECT * FROM servicenow_artifacts 
-  WHERE deployment_status = 'failed'
-  ORDER BY updated_at DESC
-`);
-```
-
-### Custom Operations
-
-Access the operations layer for advanced functionality:
-
-```typescript
-const ops = memory.getOperations();
-
-// Search messages with custom criteria
-const messages = await ops.searchMessages({
-  message_type: 'error',
-  processed: false,
-  limit: 10
-});
-
-// Get deployment history
-const history = await ops.getDeploymentHistory('artifact_123');
-```
-
-## Performance Optimization
-
-The memory system is optimized for performance:
-
-1. **WAL Mode**: Enables concurrent reads
-2. **Indexes**: Fast queries on common fields
-3. **Prepared Statements**: Reusable query plans
-4. **Connection Pooling**: Single shared instance
-5. **Batch Operations**: Transaction support
-
-## Best Practices
-
-1. **Always register agents** before performing operations
-2. **Use transactions** for multiple related operations
-3. **Clean up sessions** when work is complete
-4. **Track performance** for critical operations
-5. **Store minimal data** in shared context
-6. **Use appropriate expiration** for temporary data
-7. **Handle errors gracefully** with try-catch blocks
-
-## Testing
-
-Run the test suite to verify functionality:
-
-```bash
-npm run test:memory
-# or
-node dist/memory/memory-test.js
-```
-
-## Monitoring
-
-Check memory statistics:
-
-```typescript
-const stats = memory.getStats();
-console.log('Database statistics:', stats);
-
-// Run cleanup for old data
-await memory.runCleanup();
-```
-
-## Shutdown
-
-Always shutdown the memory system when done:
-
-```typescript
-MemoryClient.shutdown();
-```
-
-This ensures all connections are properly closed and data is flushed to disk.