snow-flow 3.4.35 → 3.4.39

package/dist/services/widget-deployment-service.d.ts

@@ -8,7 +8,7 @@ export interface WidgetConfig {
     title: string;
     template: string;
     css?: string;
-    server_script?: string;
+    script?: string;
     client_script?: string;
     demo_data?: string;
     option_schema?: string;

package/dist/services/widget-deployment-service.js

@@ -109,7 +109,7 @@ class WidgetDeploymentService {
             title: config.title,
             template: config.template || '<div>Widget Template</div>',
             css: config.css || '',
-            server_script: config.server_script || '',
+            script: config.script || '', // ServiceNow uses 'script' field
             client_controller: config.client_script || '',
             demo_data: config.demo_data || '{}',
             option_schema: config.option_schema || '[]',

package/dist/templates/claude-md-template.d.ts

@@ -1,2 +1,2 @@
-export declare const CLAUDE_MD_TEMPLATE = "# Snow-Flow Configuration & Best Practices\n\nThis document provides comprehensive instructions for Snow-Flow, an advanced ServiceNow development and orchestration framework powered by Claude AI.\n\n## Table of Contents\n1. [Core Philosophy](#core-philosophy)\n2. [Fundamental Rules](#fundamental-rules)\n3. [ServiceNow Development Standards](#servicenow-development-standards)\n4. [MCP Server Capabilities](#mcp-server-capabilities)\n5. [Debugging Best Practices](#debugging-best-practices)\n6. [Command Reference](#command-reference)\n7. [Workflow Guidelines](#workflow-guidelines)\n\n## Core Philosophy\n\n### The Prime Directive: Verify, Don't Assume\n\nSnow-Flow operates on evidence-based development. Never make assumptions about what exists or doesn't exist in a ServiceNow environment. Every environment is unique with custom tables, fields, integrations, and configurations that you cannot predict.\n\n**Cardinal Rules:**\n1. If code references something, it probably exists\n2. Test before declaring something broken\n3. Verify before modifying\n4. Fix only what's confirmed broken\n5. Respect existing configurations\n\n### The Verification-First Approach\n\n```javascript\n// Before claiming anything doesn't work or exist:\n// Step 1: Test the actual implementation\nconst verify = await snow_execute_script_with_output({\n  script: `/* Test the exact code or resource */`\n});\n\n// Step 2: Check if resources exist\nconst tableCheck = await snow_discover_table_fields({\n  table_name: 'potentially_custom_table'\n});\n\n// Step 3: Validate configurations\nconst propertyCheck = await snow_property_manager({\n  action: 'get',\n  name: 'system.property'\n});\n\n// Step 4: Only then make informed decisions\n```\n\n## Fundamental Rules\n\n### Rule 1: \uD83D\uDEA8 ES5 JavaScript ONLY in ServiceNow - NO EXCEPTIONS!\n\n**\u26A0\uFE0F CRITICAL WARNING: ServiceNow uses Rhino engine - ES6/ES7/ES8+ WILL FAIL!**\n\nServiceNow's server-side JavaScript runs on Mozilla Rhino which **ONLY supports ES5 (2009)**. Any modern JavaScript syntax will cause **RUNTIME ERRORS**.\n\n**\u274C THESE WILL CRASH SERVICENOW (DO NOT USE):**\n```javascript\n// \u274C ES6+ features that BREAK ServiceNow:\nconst data = [];           // SyntaxError: missing ; after for-loop initializer\nlet items = [];            // SyntaxError: missing ; after for-loop initializer  \nconst fn = () => {};       // SyntaxError: syntax error\nvar msg = `Hello ${name}`; // SyntaxError: syntax error\nfor (let item of items){}  // SyntaxError: missing ; after for-loop initializer\nvar {name, id} = user;     // SyntaxError: destructuring declaration not supported\narray.forEach(x => {});    // SyntaxError: syntax error  \narray.map(x => x.id);      // SyntaxError: syntax error\nfunction test(param = 'default') {} // SyntaxError: syntax error\nclass MyClass {}           // SyntaxError: missing ; after for-loop initializer\n```\n\n**\u2705 ONLY USE ES5 SYNTAX (THIS WORKS):**\n```javascript\n// \u2705 ES5 compatible code that WORKS in ServiceNow:\nvar data = [];\nvar items = [];\nfunction fn() { return 'result'; }\nvar msg = 'Hello ' + name;\nfor (var i = 0; i < items.length; i++) {\n  var item = items[i];\n}\nvar name = user.name;\nvar id = user.id;\nfor (var j = 0; j < array.length; j++) {\n  // Process array[j]\n}\nfunction test(param) {\n  if (typeof param === 'undefined') param = 'default';\n}\n```\n\n**\uD83D\uDD25 COMMON MISTAKES THAT BREAK SERVICENOW:**\n1. **Arrow Functions**: `() => {}` \u2192 Use `function() {}`\n2. **Template Literals**: `` `${var}` `` \u2192 Use `'text ' + var`\n3. **Let/Const**: `let x` \u2192 Use `var x`\n4. **Destructuring**: `{a, b} = obj` \u2192 Use `obj.a`, `obj.b`\n5. **For...of**: `for (x of arr)` \u2192 Use `for (var i=0; i<arr.length; i++)`\n6. **Default Parameters**: `fn(x='default')` \u2192 Use `typeof x === 'undefined'`\n7. **Array Methods with Arrows**: `.map(x => x)` \u2192 Use `.map(function(x) { return x; })`\n\n### Rule 2: Background Scripts for Verification Only (Not Widget Updates!)\n\n**CRITICAL DISTINCTION:**\n- \u2705 Use background scripts for TESTING and VERIFICATION  \n- \u274C Do NOT use background scripts to UPDATE widget fields\n- \u2705 Use `snow_update` to directly modify widget records\n- \u274C Do NOT try to import server scripts into client scripts via background scripts\n\n**\uD83D\uDEA8 ES5 ENFORCEMENT FOR BACKGROUND SCRIPTS:**\nBackground scripts run on ServiceNow's server-side Rhino engine. **EVERY background script MUST be ES5-only or it will fail.**\n\n**Quick ES5 Validation Checklist:**\n- [ ] No `const` or `let` (only `var`)\n- [ ] No arrow functions `() => {}` (only `function() {}`)\n- [ ] No template literals `` `${var}` `` (only string concatenation)\n- [ ] No destructuring `{a, b} = obj` (only explicit `obj.a`)\n- [ ] No `for...of` loops (only traditional `for` loops)\n- [ ] No default parameters (use `typeof` checks)\n- [ ] No modern array methods with arrows (use traditional functions)\n\nBackground scripts are excellent for verification and debugging, but widget updates must go through proper MCP tools.\n\n**NEW: Auto-Confirm Mode for Background Scripts (v3.4.10+)**\nYou can now skip the human-in-the-loop confirmation for trusted scripts:\n\n```javascript\n// Standard mode - requires user confirmation (ES5 ONLY!)\nsnow_execute_background_script({\n  script: \"var gr = new GlideRecord('incident'); gr.query();\", // \u2705 ES5 syntax\n  description: \"Query incidents\",\n  allowDataModification: false\n});\n\n// Auto-confirm mode - executes immediately \u26A0\uFE0F USE WITH CAUTION!\nsnow_execute_background_script({\n  script: \"var gr = new GlideRecord('incident'); gr.query();\", // \u2705 ES5 syntax\n  description: \"Query incidents\",\n  allowDataModification: false,\n  autoConfirm: true  // \u26A0\uFE0F Bypasses user confirmation!\n});\n\n// \u274C WRONG - This will FAIL in ServiceNow:\n// script: \"const gr = new GlideRecord('incident'); gr.query();\", // SyntaxError!\n// script: \"incidents.forEach(i => console.log(i.number));\",      // SyntaxError!\n```\n\n**\uD83D\uDEA8 ES5 Validation Required:**\nBefore using any background script tool, validate your script is ES5-only:\n- No `const`/`let` (use `var`)\n- No arrow functions (use `function()`)\n- No template literals (use string concatenation)\n- No destructuring (use explicit property access)\n\n**\u26A0\uFE0F Security Warning:**\n- Only use `autoConfirm: true` for verified, safe scripts\n- High-risk operations will still be logged\n- All auto-executions are tracked with audit IDs\n- Default behavior (without autoConfirm) remains unchanged\n\n## \uD83D\uDEA8 CRITICAL: Common ES5 Mistakes That Break ServiceNow\n\nServiceNow developers frequently use modern JavaScript that fails on the Rhino engine. Here are the most common mistakes:\n\n### \uD83D\uDD25 Top ES5 Violations (Fix These Immediately!)\n\n**1. Arrow Functions with Array Methods**\n```javascript\n// \u274C BREAKS ServiceNow:\nvar activeIncidents = incidents.filter(inc => inc.active);\nvar numbers = activeIncidents.map(inc => inc.number);\n\n// \u2705 WORKS in ServiceNow:\nvar activeIncidents = [];\nfor (var i = 0; i < incidents.length; i++) {\n  if (incidents[i].active) {\n    activeIncidents.push(incidents[i]);\n  }\n}\nvar numbers = [];\nfor (var j = 0; j < activeIncidents.length; j++) {\n  numbers.push(activeIncidents[j].number);\n}\n```\n\n**2. Template Literals for String Building**\n```javascript\n// \u274C BREAKS ServiceNow:\nvar message = `Incident ${incident.number} assigned to ${user.name}`;\n\n// \u2705 WORKS in ServiceNow:\nvar message = 'Incident ' + incident.number + ' assigned to ' + user.name;\n```\n\n**3. Const/Let Variable Declarations**\n```javascript\n// \u274C BREAKS ServiceNow:\nconst MAX_RETRIES = 3;\nlet currentUser = gs.getUser();\n\n// \u2705 WORKS in ServiceNow:\nvar MAX_RETRIES = 3;\nvar currentUser = gs.getUser();\n```\n\n**4. Object Destructuring**\n```javascript\n// \u274C BREAKS ServiceNow:\nvar {name, email, department} = user;\nvar {sys_id: id, short_description: desc} = incident;\n\n// \u2705 WORKS in ServiceNow:\nvar name = user.name;\nvar email = user.email;\nvar department = user.department;\nvar id = incident.sys_id;\nvar desc = incident.short_description;\n```\n\n**5. For...of Loops**\n```javascript\n// \u274C BREAKS ServiceNow:\nfor (let incident of incidents) {\n  gs.info('Processing: ' + incident.number);\n}\n\n// \u2705 WORKS in ServiceNow:\nfor (var i = 0; i < incidents.length; i++) {\n  gs.info('Processing: ' + incidents[i].number);\n}\n```\n\n**6. Default Function Parameters**\n```javascript\n// \u274C BREAKS ServiceNow:\nfunction processIncident(incident, priority = 3, assignee = 'unassigned') {\n  // Process incident\n}\n\n// \u2705 WORKS in ServiceNow:\nfunction processIncident(incident, priority, assignee) {\n  if (typeof priority === 'undefined') priority = 3;\n  if (typeof assignee === 'undefined') assignee = 'unassigned';\n  // Process incident\n}\n```\n\n### \uD83C\uDFAF Quick ES5 Conversion Guide\n| Modern (ES6+) | ES5 Equivalent |\n|---------------|----------------|\n| `const x = 5;` | `var x = 5;` |\n| `let items = [];` | `var items = [];` |\n| `() => {}` | `function() {}` |\n| `` `Hello ${name}` `` | `'Hello ' + name` |\n| `{a, b} = obj` | `var a = obj.a; var b = obj.b;` |\n| `for (item of items)` | `for (var i = 0; i < items.length; i++)` |\n| `func(x = 'default')` | `if (typeof x === 'undefined') x = 'default';` |\n| `arr.map(x => x.id)` | `arr.map(function(x) { return x.id; })` |\n\n```javascript\n// Universal verification pattern\nconst verify = await snow_execute_script_with_output({\n  script: `\n    gs.info('=== VERIFICATION TEST ===');\n    \n    // Test table existence\n    var table = new GlideRecord('table_name');\n    gs.info('Table valid: ' + table.isValid());\n    \n    // Test property existence\n    var prop = gs.getProperty('property.name');\n    gs.info('Property: ' + (prop || 'NOT SET'));\n    \n    // Test actual code\n    try {\n      // User's code here\n      gs.info('SUCCESS');\n    } catch(e) {\n      gs.error('ERROR: ' + e.message);\n    }\n  `\n});\n```\n\n### Rule 3: Widget Coherence - Critical Client-Server Communication\n\nServiceNow widgets MUST have perfect communication between client and server scripts. This is not optional - widgets fail when these components don't talk to each other correctly.\n\n**The Three-Way Contract:**\n\n**Server Script Must:**\n- Initialize all `data` properties that HTML will reference\n- Handle every `input.action` that client sends\n- Return data in the format client expects\n\n**Client Script Must:**\n- Implement every method that HTML calls via `ng-click`\n- Use `c.server.get({action: 'name'})` for server communication\n- Update `c.data` when server responds\n\n**HTML Template Must:**\n- Only reference `data` properties that server provides\n- Only call methods that client implements\n- Use correct Angular directives and bindings\n\n**Critical Communication Points:**\n\n1. **Server \u2192 Client Data Flow**\n   - Server sets `data.property`\n   - Client receives via `c.data.property`\n   - HTML displays with `{{data.property}}`\n\n2. **Client \u2192 Server Requests**\n   - Client sends `c.server.get({action: 'name'})`\n   - Server receives via `input.action`\n   - Server processes and returns updated `data`\n\n3. **HTML \u2192 Client Method Calls**\n   - HTML has `ng-click=\"methodName()\"`\n   - Client must have `$scope.methodName = function()`\n   - Method typically calls server with `c.server.get()`\n\n**Common Failures to Avoid:**\n- Action name mismatches between client and server\n- Method name mismatches between HTML and client  \n- Property name mismatches between server and HTML\n- Missing handlers for client requests\n- Orphaned data properties or methods\n\n**Coherence Validation Checklist:**\n- [ ] Every `data.property` in server is used in HTML/client\n- [ ] Every `ng-click` in HTML has matching `$scope.method` in client\n- [ ] Every `c.server.get({action})` in client has matching `if(input.action)` in server\n- [ ] Data flows correctly: Server \u2192 HTML \u2192 Client \u2192 Server\n- [ ] No orphaned methods or unused data properties\n\n### Rule 4: Evidence-Based Debugging\n\nFollow this systematic approach for all debugging:\n\n1. **Reproduce** - Run the exact failing code\n2. **Inventory** - List all dependencies\n3. **Verify** - Test each dependency exists\n4. **Fix** - Correct only confirmed issues\n\n**Fix only:**\n- \u2705 Confirmed syntax errors\n- \u2705 Verified null references\n- \u2705 Missing dependencies (after verification)\n- \u2705 Real type mismatches\n\n**Never change:**\n- \u274C Unverified resources\n- \u274C Configurations that \"seem wrong\"\n- \u274C APIs you haven't tested\n- \u274C Working code that could be \"better\"\n\n## ServiceNow Development Standards\n\n### Table Operations\n- Always verify table existence before operations\n- Use proper field types and references\n- Check for ACLs and permissions\n- Handle large datasets with pagination\n\n### Script Development\n- Use Script Includes for reusable code\n- Implement proper error handling\n- Add meaningful logging with gs.info/warn/error\n- Test in scoped applications when applicable\n- **NEVER use background scripts to update widget fields - use `snow_update` instead**\n\n### Widget Development\n\n**CRITICAL: Direct Widget Updates (Not Background Scripts!)**\n- Use `snow_update({ type: 'widget', identifier: 'widget_name', config: { /* fields to update */ }})` \n- Updates widget fields DIRECTLY on the widget record\n- Do NOT use background scripts to update widget fields\n- Do NOT try to import server scripts into client scripts\n\n**Widget Coherence Requirements:**\n- Ensure HTML/Client/Server scripts communicate properly\n- Use Angular providers correctly  \n- Implement proper data binding\n- Test across different themes and portals\n\n**Creating New Widgets:**\n```javascript\nsnow_deploy({\n  type: 'widget',\n  config: {\n    name: 'my_widget',\n    title: 'My Widget',  // Required for display\n    template: '<div>{{data.message}}</div>',  // Required HTML\n    server_script: 'data.message = \"Hello\";',\n    client_script: 'function($scope) { var c = this; }'\n  }\n})\n```\n\n**Updating Existing Widgets:**\n```javascript\nsnow_update({\n  type: 'widget',\n  identifier: 'my_widget',  // Name or sys_id\n  config: {\n    template: '<div>Updated HTML</div>',  // Only update what changes\n    server_script: 'data.updated = true;'\n  }\n})\n```\n\n### Flow Development\n- Use proper trigger conditions\n- Implement error handling paths\n- Add appropriate logging actions\n- Test with various data scenarios\n\n## MCP Server Capabilities\n\nSnow-Flow includes 16+ specialized MCP servers with over 200 tools for comprehensive ServiceNow integration:\n\n### 1. ServiceNow Deployment Server\n**Purpose:** Widget and artifact deployment with coherence validation\n\n**Key Tools:**\n- `snow_deploy` - Create NEW artifacts (widgets, pages, etc.) - use with `type: 'widget'`\n- `snow_update` - UPDATE existing artifacts - use for widget field updates\n- `snow_validate_deployment` - Validate deployed artifacts\n- `snow_rollback_deployment` - Rollback failed deployments\n- `snow_preview_widget` - Preview widget before deployment\n- `snow_widget_test` - Test widget functionality\n\n**Special Features:**\n- Automatic widget coherence validation\n- Data flow contract verification\n- Method implementation checking\n- CSS class validation\n\n### 2. ServiceNow Operations Server\n**Purpose:** Core ServiceNow operations and queries\n\n**Key Tools:**\n- `snow_query_table` - Universal table querying with pagination\n- `snow_query_incidents` - Query and analyze incidents\n- `snow_cmdb_search` - Search Configuration Management Database\n- `snow_user_lookup` - Find and manage users\n- `snow_operational_metrics` - Get operational metrics\n- `snow_knowledge_search` - Search knowledge base\n\n**Features:**\n- Full CRUD operations on any table\n- Advanced query capabilities\n- Field discovery and validation\n- Relationship navigation\n\n### 3. ServiceNow Automation Server\n**Purpose:** Script execution and automation\n\n**\uD83D\uDEA8 CRITICAL: ALL SCRIPTS MUST BE ES5 ONLY!**\nServiceNow runs on Rhino engine - ES6+ syntax will cause SyntaxError and script failure.\n\n**Key Tools:**\n- `snow_execute_background_script` - Execute background scripts (**ES5 ONLY!** with optional autoConfirm)\n- `snow_confirm_script_execution` - Confirm script execution after user approval\n- `snow_execute_script_with_output` - Execute scripts with output capture (**ES5 ONLY!**)\n- `snow_get_script_output` - Retrieve script execution history\n- `snow_execute_script_sync` - Synchronous script execution (**ES5 ONLY!**)\n- `snow_get_logs` - Access system logs\n- `snow_test_rest_connection` - Test REST integrations\n- `snow_trace_execution` - Trace script execution (**ES5 ONLY!**)\n- `snow_schedule_job` - Create scheduled jobs\n- `snow_create_event` - Trigger system events\n\n**Remember:** Use `var`, `function(){}`, string concatenation, traditional for loops only!\n\n**Features:**\n- Full output capture (gs.print/info/warn/error)\n- Execution history tracking\n- System log access\n- REST message testing\n- Performance tracing\n\n### 4. ServiceNow Platform Development Server\n**Purpose:** Platform development artifacts\n\n**Key Tools:**\n- `snow_create_ui_page` - Create UI pages\n- `snow_create_script_include` - Create reusable scripts\n- `snow_create_business_rule` - Create business rules\n- `snow_create_client_script` - Create client-side scripts\n- `snow_create_ui_policy` - Create UI policies\n- `snow_create_ui_action` - Create UI actions\n\n**Features:**\n- Full artifact creation\n- Proper scoping support\n- Condition builder integration\n- Script validation\n\n### 5. ServiceNow Integration Server\n**Purpose:** Integration and data management\n\n**Key Tools:**\n- `snow_create_rest_message` - Create REST integrations\n- `snow_create_transform_map` - Create data transformation maps\n- `snow_create_import_set` - Manage import sets\n- `snow_test_web_service` - Test web services\n- `snow_configure_email` - Configure email settings\n\n**Features:**\n- REST/SOAP integration\n- Data transformation\n- Import/Export capabilities\n- Email configuration\n\n### 6. ServiceNow System Properties Server\n**Purpose:** System property management\n\n**Key Tools:**\n- `snow_property_get` - Retrieve property values\n- `snow_property_set` - Set property values\n- `snow_property_list` - List properties by pattern\n- `snow_property_delete` - Remove properties\n- `snow_property_bulk_update` - Bulk operations\n- `snow_property_export` - Export to JSON\n- `snow_property_import` - Import from JSON\n\n**Features:**\n- Full CRUD on sys_properties\n- Bulk operations\n- Import/Export capabilities\n- Property validation\n\n### 7. ServiceNow Update Set Server\n**Purpose:** Change management and deployment\n\n**Key Tools:**\n- `snow_update_set_create` - Create new update sets\n- `snow_update_set_switch` - Switch active update set\n- `snow_update_set_current` - Get current update set\n- `snow_update_set_complete` - Mark as complete\n- `snow_update_set_export` - Export as XML\n- `snow_ensure_active_update_set` - Ensure update set is active\n\n**Features:**\n- Full update set lifecycle\n- Change tracking\n- XML export/import\n- Conflict detection\n\n### 8. ServiceNow Development Assistant Server\n**Purpose:** Intelligent artifact search, editing and development assistance\n\n**Key Tools:**\n- `snow_find_artifact` - Find any ServiceNow artifact by name/type\n- `snow_edit_artifact` - Edit existing artifacts intelligently\n- `snow_get_by_sysid` - Get artifact by sys_id\n- `snow_analyze_artifact` - Analyze artifact structure and dependencies\n- `snow_comprehensive_search` - Deep search across all tables\n- `snow_analyze_requirements` - Analyze development requirements\n\n**Features:**\n- Pattern-based code generation\n- Best practice enforcement\n- Performance optimization\n- Security review\n\n### 9. ServiceNow Security & Compliance Server\n**Purpose:** Security and compliance management\n\n**Key Tools:**\n- `snow_create_security_policy` - Create security policies\n- `snow_audit_compliance` - Compliance auditing\n- `snow_scan_vulnerabilities` - Vulnerability scanning\n- `snow_assess_risk` - Risk assessment\n- `snow_review_access_control` - ACL review\n\n**Features:**\n- SOX/GDPR/HIPAA compliance\n- Security policy management\n- Vulnerability assessment\n- Access control validation\n\n### 10. ServiceNow Reporting & Analytics Server\n**Purpose:** Reporting and data visualization\n\n**Key Tools:**\n- `snow_create_report` - Create reports\n- `snow_create_dashboard` - Create dashboards\n- `snow_define_kpi` - Define KPIs\n- `snow_schedule_report` - Schedule report delivery\n- `snow_analyze_data_quality` - Data quality analysis\n\n**Features:**\n- Advanced reporting\n- Dashboard creation\n- KPI management\n- Scheduled delivery\n\n### 11. ServiceNow Machine Learning Server\n**Purpose:** AI/ML capabilities with TensorFlow.js and native ML integration\n\n**Key Tools:**\n- `ml_train_incident_classifier` - Train incident classifier with LSTM neural networks\n- `ml_predict_change_risk` - Predict change risks\n- `ml_detect_anomalies` - Anomaly detection\n- `ml_forecast_incidents` - Incident forecasting with time series\n- `ml_performance_analytics` - Native Performance Analytics ML\n- `ml_hybrid_recommendation` - Hybrid ML recommendations\n\n**Features:**\n- Predictive analytics\n- Pattern recognition\n- Anomaly detection\n- Process optimization\n\n### 12. Snow-Flow Orchestration Server\n**Purpose:** Multi-agent coordination and task management\n\n**Key Tools:**\n- `swarm_init` - Initialize agent swarms\n- `agent_spawn` - Create specialized agents\n- `task_orchestrate` - Orchestrate complex tasks\n- `memory_search` - Search persistent memory\n- `neural_train` - Train neural networks with TensorFlow.js\n- `performance_report` - Generate performance reports\n\n### Additional Servers:\n\n**ServiceNow CMDB/Event/HR/CSM/DevOps Server** - CI management, event correlation, HR processes, customer service, DevOps pipelines\n\n**ServiceNow Knowledge & Catalog Server** - Knowledge articles, service catalog items, catalog variables and policies\n\n**ServiceNow Change/Virtual Agent/PA Server** - Change management, virtual agent NLU, predictive analytics\n\n**ServiceNow Flow/Workspace/Mobile Server** - Flow Designer, workspace configuration, mobile app management\n\n**Features:**\n- Multi-agent coordination\n- Task orchestration\n- Neural network training (TensorFlow.js)\n- Memory management\n- Performance monitoring\n\n## Debugging Best Practices\n\n### Systematic Debugging Protocol\n\n1. **Reproduce the Issue**\n   ```javascript\n   // Always use ES5 and test exact code\n   const result = await snow_execute_script_with_output({\n     script: `/* Exact failing code in ES5 */`\n   });\n   ```\n\n2. **Verify Dependencies**\n   - Check all referenced tables exist\n   - Verify all properties are set\n   - Confirm all fields are present\n   - Test all integrations work\n\n3. **Test in Context**\n   - Use same scope and variables\n   - Include same imports\n   - Test with same data\n\n4. **Apply Evidence-Based Fixes**\n   - Fix only confirmed issues\n   - Document why changes were made\n   - Test fixes thoroughly\n\n### Common Verification Patterns\n\n**Table Verification:**\n```javascript\nvar table = new GlideRecord('table_name');\ngs.info('Table exists: ' + table.isValid());\n```\n\n**Property Verification:**\n```javascript\nvar prop = gs.getProperty('property.name');\ngs.info('Property value: ' + (prop || 'NOT SET'));\n```\n\n**Field Verification:**\n```javascript\nvar gr = new GlideRecord('table');\nvar element = gr.getElement('field_name');\ngs.info('Field exists: ' + (element ? 'Yes' : 'No'));\n```\n\n## Command Reference\n\n### Core Commands\n- `./snow-flow start` - Start orchestration system\n- `./snow-flow status` - System status\n- `./snow-flow monitor` - Real-time monitoring\n\n### Agent Management\n- `./snow-flow agent spawn <type>` - Create agents\n- `./snow-flow agent list` - List active agents\n\n### Task Management\n- `./snow-flow task create` - Create tasks\n- `./snow-flow task list` - View task queue\n\n### Memory Operations\n- `./snow-flow memory store <key> <data>` - Store data\n- `./snow-flow memory get <key>` - Retrieve data\n- `./snow-flow memory list` - List all keys\n\n### SPARC Modes\n- `./snow-flow sparc \"<task>\"` - Orchestrator mode\n- `./snow-flow sparc run <mode> \"<task>\"` - Specific mode\n- `./snow-flow sparc tdd \"<feature>\"` - Test-driven development\n\n### Swarm Coordination\n- `./snow-flow swarm \"<objective>\"` - Multi-agent coordination\n- Options: `--strategy`, `--mode`, `--parallel`, `--monitor`\n\n## Workflow Guidelines\n\n### Development Workflow\n1. **Plan** - Use TodoWrite for task management\n2. **Verify** - Check existing resources\n3. **Develop** - Follow ES5 standards\n4. **Test** - Use background scripts\n5. **Deploy** - Use update sets\n6. **Validate** - Verify deployment\n\n### Testing Workflow\n1. Run unit tests with background scripts\n2. Test integrations with REST tools\n3. Validate UI with widget coherence\n4. Check performance with tracing\n5. Review logs for errors\n\n### Debugging Workflow\n1. Reproduce issue exactly\n2. Gather evidence with scripts\n3. Verify all assumptions\n4. Apply minimal fixes\n5. Test thoroughly\n6. Document changes\n\n## Important Reminders\n\n### Always Remember\n- Every ServiceNow instance is unique\n- Custom implementations exist that you don't know about\n- Preview/beta features may be available\n- Organization-specific configurations are common\n- Test everything before making assumptions\n\n### Never Assume\n- That something doesn't exist without verification\n- That configurations are wrong without testing\n- That APIs aren't available without checking\n- That code won't work without running it\n- That you know better than existing implementations\n\n### Golden Rules\n1. **Verify First** - Test before declaring broken\n2. **ES5 Only** - No modern JavaScript in ServiceNow\n3. **Evidence-Based** - Make decisions on facts, not assumptions\n4. **Minimal Changes** - Fix only what's broken\n5. **Respect Context** - Understand why things exist as they do\n\n## Conclusion\n\nSnow-Flow is a powerful framework for ServiceNow development that emphasizes verification, testing, and evidence-based decision making. By following these guidelines and best practices, you ensure reliable, maintainable, and effective ServiceNow solutions.\n\nRemember: Your job is to solve problems, not to judge implementations. Every environment has its reasons for existing configurations. Verify, test, and respect what you find.";
+export declare const CLAUDE_MD_TEMPLATE = "# Snow-Flow Configuration & Best Practices\n\nThis document provides comprehensive instructions for Snow-Flow, an advanced ServiceNow development and orchestration framework powered by Claude AI.\n\n## Table of Contents\n1. [Core Philosophy](#core-philosophy)\n2. [Fundamental Rules](#fundamental-rules)\n3. [ServiceNow Development Standards](#servicenow-development-standards)\n4. [MCP Server Capabilities](#mcp-server-capabilities)\n5. [Debugging Best Practices](#debugging-best-practices)\n6. [Command Reference](#command-reference)\n7. [Workflow Guidelines](#workflow-guidelines)\n\n## Core Philosophy\n\n### The Prime Directive: Verify, Don't Assume\n\nSnow-Flow operates on evidence-based development. Never make assumptions about what exists or doesn't exist in a ServiceNow environment. Every environment is unique with custom tables, fields, integrations, and configurations that you cannot predict.\n\n**Cardinal Rules:**\n1. If code references something, it probably exists\n2. Test before declaring something broken\n3. Verify before modifying\n4. Fix only what's confirmed broken\n5. Respect existing configurations\n\n### The Verification-First Approach\n\n```javascript\n// Before claiming anything doesn't work or exist:\n// Step 1: Test the actual implementation\nconst verify = await snow_execute_script_with_output({\n  script: `/* Test the exact code or resource */`\n});\n\n// Step 2: Check if resources exist\nconst tableCheck = await snow_discover_table_fields({\n  table_name: 'potentially_custom_table'\n});\n\n// Step 3: Validate configurations\nconst propertyCheck = await snow_property_manager({\n  action: 'get',\n  name: 'system.property'\n});\n\n// Step 4: Only then make informed decisions\n```\n\n## Fundamental Rules\n\n### Rule 1: \uD83D\uDEA8 ES5 JavaScript ONLY in ServiceNow - NO EXCEPTIONS!\n\n**\u26A0\uFE0F CRITICAL WARNING: ServiceNow uses Rhino engine - ES6/ES7/ES8+ WILL FAIL!**\n\nServiceNow's server-side JavaScript runs on Mozilla Rhino which **ONLY supports ES5 (2009)**. Any modern JavaScript syntax will cause **RUNTIME ERRORS**.\n\n**\u274C THESE WILL CRASH SERVICENOW (DO NOT USE):**\n```javascript\n// \u274C ES6+ features that BREAK ServiceNow:\nconst data = [];           // SyntaxError: missing ; after for-loop initializer\nlet items = [];            // SyntaxError: missing ; after for-loop initializer  \nconst fn = () => {};       // SyntaxError: syntax error\nvar msg = `Hello ${name}`; // SyntaxError: syntax error\nfor (let item of items){}  // SyntaxError: missing ; after for-loop initializer\nvar {name, id} = user;     // SyntaxError: destructuring declaration not supported\narray.forEach(x => {});    // SyntaxError: syntax error  \narray.map(x => x.id);      // SyntaxError: syntax error\nfunction test(param = 'default') {} // SyntaxError: syntax error\nclass MyClass {}           // SyntaxError: missing ; after for-loop initializer\n```\n\n**\u2705 ONLY USE ES5 SYNTAX (THIS WORKS):**\n```javascript\n// \u2705 ES5 compatible code that WORKS in ServiceNow:\nvar data = [];\nvar items = [];\nfunction fn() { return 'result'; }\nvar msg = 'Hello ' + name;\nfor (var i = 0; i < items.length; i++) {\n  var item = items[i];\n}\nvar name = user.name;\nvar id = user.id;\nfor (var j = 0; j < array.length; j++) {\n  // Process array[j]\n}\nfunction test(param) {\n  if (typeof param === 'undefined') param = 'default';\n}\n```\n\n**\uD83D\uDD25 COMMON MISTAKES THAT BREAK SERVICENOW:**\n1. **Arrow Functions**: `() => {}` \u2192 Use `function() {}`\n2. **Template Literals**: `` `${var}` `` \u2192 Use `'text ' + var`\n3. **Let/Const**: `let x` \u2192 Use `var x`\n4. **Destructuring**: `{a, b} = obj` \u2192 Use `obj.a`, `obj.b`\n5. **For...of**: `for (x of arr)` \u2192 Use `for (var i=0; i<arr.length; i++)`\n6. **Default Parameters**: `fn(x='default')` \u2192 Use `typeof x === 'undefined'`\n7. **Array Methods with Arrows**: `.map(x => x)` \u2192 Use `.map(function(x) { return x; })`\n\n### Rule 2: Background Scripts for Verification Only (Not Widget Updates!)\n\n**CRITICAL DISTINCTION:**\n- \u2705 Use background scripts for TESTING and VERIFICATION  \n- \u274C Do NOT use background scripts to UPDATE widget fields\n- \u2705 Use `snow_update` to directly modify widget records\n- \u274C Do NOT try to import server scripts into client scripts via background scripts\n\n**\uD83D\uDEA8 ES5 ENFORCEMENT FOR BACKGROUND SCRIPTS:**\nBackground scripts run on ServiceNow's server-side Rhino engine. **EVERY background script MUST be ES5-only or it will fail.**\n\n**Quick ES5 Validation Checklist:**\n- [ ] No `const` or `let` (only `var`)\n- [ ] No arrow functions `() => {}` (only `function() {}`)\n- [ ] No template literals `` `${var}` `` (only string concatenation)\n- [ ] No destructuring `{a, b} = obj` (only explicit `obj.a`)\n- [ ] No `for...of` loops (only traditional `for` loops)\n- [ ] No default parameters (use `typeof` checks)\n- [ ] No modern array methods with arrows (use traditional functions)\n\nBackground scripts are excellent for verification and debugging, but widget updates must go through proper MCP tools.\n\n**NEW: Auto-Confirm Mode for Background Scripts (v3.4.10+)**\nYou can now skip the human-in-the-loop confirmation for trusted scripts:\n\n```javascript\n// Standard mode - requires user confirmation (ES5 ONLY!)\nsnow_execute_background_script({\n  script: \"var gr = new GlideRecord('incident'); gr.query();\", // \u2705 ES5 syntax\n  description: \"Query incidents\",\n  allowDataModification: false\n});\n\n// Auto-confirm mode - executes immediately \u26A0\uFE0F USE WITH CAUTION!\nsnow_execute_background_script({\n  script: \"var gr = new GlideRecord('incident'); gr.query();\", // \u2705 ES5 syntax\n  description: \"Query incidents\",\n  allowDataModification: false,\n  autoConfirm: true  // \u26A0\uFE0F Bypasses user confirmation!\n});\n\n// \u274C WRONG - This will FAIL in ServiceNow:\n// script: \"const gr = new GlideRecord('incident'); gr.query();\", // SyntaxError!\n// script: \"incidents.forEach(i => console.log(i.number));\",      // SyntaxError!\n```\n\n**\uD83D\uDEA8 ES5 Validation Required:**\nBefore using any background script tool, validate your script is ES5-only:\n- No `const`/`let` (use `var`)\n- No arrow functions (use `function()`)\n- No template literals (use string concatenation)\n- No destructuring (use explicit property access)\n\n**\u26A0\uFE0F Security Warning:**\n- Only use `autoConfirm: true` for verified, safe scripts\n- High-risk operations will still be logged\n- All auto-executions are tracked with audit IDs\n- Default behavior (without autoConfirm) remains unchanged\n\n## \uD83D\uDEA8 CRITICAL: Common ES5 Mistakes That Break ServiceNow\n\nServiceNow developers frequently use modern JavaScript that fails on the Rhino engine. Here are the most common mistakes:\n\n### \uD83D\uDD25 Top ES5 Violations (Fix These Immediately!)\n\n**1. Arrow Functions with Array Methods**\n```javascript\n// \u274C BREAKS ServiceNow:\nvar activeIncidents = incidents.filter(inc => inc.active);\nvar numbers = activeIncidents.map(inc => inc.number);\n\n// \u2705 WORKS in ServiceNow:\nvar activeIncidents = [];\nfor (var i = 0; i < incidents.length; i++) {\n  if (incidents[i].active) {\n    activeIncidents.push(incidents[i]);\n  }\n}\nvar numbers = [];\nfor (var j = 0; j < activeIncidents.length; j++) {\n  numbers.push(activeIncidents[j].number);\n}\n```\n\n**2. Template Literals for String Building**\n```javascript\n// \u274C BREAKS ServiceNow:\nvar message = `Incident ${incident.number} assigned to ${user.name}`;\n\n// \u2705 WORKS in ServiceNow:\nvar message = 'Incident ' + incident.number + ' assigned to ' + user.name;\n```\n\n**3. Const/Let Variable Declarations**\n```javascript\n// \u274C BREAKS ServiceNow:\nconst MAX_RETRIES = 3;\nlet currentUser = gs.getUser();\n\n// \u2705 WORKS in ServiceNow:\nvar MAX_RETRIES = 3;\nvar currentUser = gs.getUser();\n```\n\n**4. Object Destructuring**\n```javascript\n// \u274C BREAKS ServiceNow:\nvar {name, email, department} = user;\nvar {sys_id: id, short_description: desc} = incident;\n\n// \u2705 WORKS in ServiceNow:\nvar name = user.name;\nvar email = user.email;\nvar department = user.department;\nvar id = incident.sys_id;\nvar desc = incident.short_description;\n```\n\n**5. For...of Loops**\n```javascript\n// \u274C BREAKS ServiceNow:\nfor (let incident of incidents) {\n  gs.info('Processing: ' + incident.number);\n}\n\n// \u2705 WORKS in ServiceNow:\nfor (var i = 0; i < incidents.length; i++) {\n  gs.info('Processing: ' + incidents[i].number);\n}\n```\n\n**6. Default Function Parameters**\n```javascript\n// \u274C BREAKS ServiceNow:\nfunction processIncident(incident, priority = 3, assignee = 'unassigned') {\n  // Process incident\n}\n\n// \u2705 WORKS in ServiceNow:\nfunction processIncident(incident, priority, assignee) {\n  if (typeof priority === 'undefined') priority = 3;\n  if (typeof assignee === 'undefined') assignee = 'unassigned';\n  // Process incident\n}\n```\n\n### \uD83C\uDFAF Quick ES5 Conversion Guide\n| Modern (ES6+) | ES5 Equivalent |\n|---------------|----------------|\n| `const x = 5;` | `var x = 5;` |\n| `let items = [];` | `var items = [];` |\n| `() => {}` | `function() {}` |\n| `` `Hello ${name}` `` | `'Hello ' + name` |\n| `{a, b} = obj` | `var a = obj.a; var b = obj.b;` |\n| `for (item of items)` | `for (var i = 0; i < items.length; i++)` |\n| `func(x = 'default')` | `if (typeof x === 'undefined') x = 'default';` |\n| `arr.map(x => x.id)` | `arr.map(function(x) { return x.id; })` |\n\n```javascript\n// Universal verification pattern\nconst verify = await snow_execute_script_with_output({\n  script: `\n    gs.info('=== VERIFICATION TEST ===');\n    \n    // Test table existence\n    var table = new GlideRecord('table_name');\n    gs.info('Table valid: ' + table.isValid());\n    \n    // Test property existence\n    var prop = gs.getProperty('property.name');\n    gs.info('Property: ' + (prop || 'NOT SET'));\n    \n    // Test actual code\n    try {\n      // User's code here\n      gs.info('SUCCESS');\n    } catch(e) {\n      gs.error('ERROR: ' + e.message);\n    }\n  `\n});\n```\n\n### Rule 3: Widget Coherence - Critical Client-Server Communication\n\nServiceNow widgets MUST have perfect communication between client and server scripts. This is not optional - widgets fail when these components don't talk to each other correctly.\n\n**The Three-Way Contract:**\n\n**Server Script Must:**\n- Initialize all `data` properties that HTML will reference\n- Handle every `input.action` that client sends\n- Return data in the format client expects\n\n**Client Script Must:**\n- Implement every method that HTML calls via `ng-click`\n- Use `c.server.get({action: 'name'})` for server communication\n- Update `c.data` when server responds\n\n**HTML Template Must:**\n- Only reference `data` properties that server provides\n- Only call methods that client implements\n- Use correct Angular directives and bindings\n\n**Critical Communication Points:**\n\n1. **Server \u2192 Client Data Flow**\n   - Server sets `data.property`\n   - Client receives via `c.data.property`\n   - HTML displays with `{{data.property}}`\n\n2. **Client \u2192 Server Requests**\n   - Client sends `c.server.get({action: 'name'})`\n   - Server receives via `input.action`\n   - Server processes and returns updated `data`\n\n3. **HTML \u2192 Client Method Calls**\n   - HTML has `ng-click=\"methodName()\"`\n   - Client must have `$scope.methodName = function()`\n   - Method typically calls server with `c.server.get()`\n\n**Common Failures to Avoid:**\n- Action name mismatches between client and server\n- Method name mismatches between HTML and client  \n- Property name mismatches between server and HTML\n- Missing handlers for client requests\n- Orphaned data properties or methods\n\n**Coherence Validation Checklist:**\n- [ ] Every `data.property` in server is used in HTML/client\n- [ ] Every `ng-click` in HTML has matching `$scope.method` in client\n- [ ] Every `c.server.get({action})` in client has matching `if(input.action)` in server\n- [ ] Data flows correctly: Server \u2192 HTML \u2192 Client \u2192 Server\n- [ ] No orphaned methods or unused data properties\n\n### Rule 4: Evidence-Based Debugging\n\nFollow this systematic approach for all debugging:\n\n1. **Reproduce** - Run the exact failing code\n2. **Inventory** - List all dependencies\n3. **Verify** - Test each dependency exists\n4. **Fix** - Correct only confirmed issues\n\n**Fix only:**\n- \u2705 Confirmed syntax errors\n- \u2705 Verified null references\n- \u2705 Missing dependencies (after verification)\n- \u2705 Real type mismatches\n\n**Never change:**\n- \u274C Unverified resources\n- \u274C Configurations that \"seem wrong\"\n- \u274C APIs you haven't tested\n- \u274C Working code that could be \"better\"\n\n## ServiceNow Development Standards\n\n### Table Operations\n- Always verify table existence before operations\n- Use proper field types and references\n- Check for ACLs and permissions\n- Handle large datasets with pagination\n\n### Script Development\n- Use Script Includes for reusable code\n- Implement proper error handling\n- Add meaningful logging with gs.info/warn/error\n- Test in scoped applications when applicable\n- **NEVER use background scripts to update widget fields - use `snow_update` instead**\n\n### Widget Development\n\n**CRITICAL: Direct Widget Updates (Not Background Scripts!)**\n- Use `snow_update({ type: 'widget', identifier: 'widget_name', config: { /* fields to update */ }})` \n- Updates widget fields DIRECTLY on the widget record\n- Do NOT use background scripts to update widget fields\n- Do NOT try to import server scripts into client scripts\n\n**Widget Coherence Requirements:**\n- Ensure HTML/Client/Server scripts communicate properly\n- Use Angular providers correctly  \n- Implement proper data binding\n- Test across different themes and portals\n\n**Creating New Widgets:**\n```javascript\nsnow_deploy({\n  type: 'widget',\n  config: {\n    name: 'my_widget',\n    title: 'My Widget',  // Required for display\n    template: '<div>{{data.message}}</div>',  // Required HTML\n    script: 'data.message = \"Hello\";', // ServiceNow uses 'script' field\n    client_script: 'function($scope) { var c = this; }'\n  }\n})\n```\n\n**Updating Existing Widgets:**\n```javascript\nsnow_update({\n  type: 'widget',\n  identifier: 'my_widget',  // Name or sys_id\n  config: {\n    template: '<div>Updated HTML</div>',  // Only update what changes\n    script: 'data.updated = true;' // ServiceNow uses 'script' field\n  }\n})\n```\n\n### Flow Development\n- Use proper trigger conditions\n- Implement error handling paths\n- Add appropriate logging actions\n- Test with various data scenarios\n\n## MCP Server Capabilities\n\nSnow-Flow includes 16+ specialized MCP servers with over 200 tools for comprehensive ServiceNow integration:\n\n### 1. ServiceNow Deployment Server\n**Purpose:** Widget and artifact deployment with coherence validation\n\n**Key Tools:**\n- `snow_deploy` - Create NEW artifacts (widgets, pages, etc.) - use with `type: 'widget'`\n- `snow_update` - UPDATE existing artifacts - use for widget field updates\n- `snow_validate_deployment` - Validate deployed artifacts\n- `snow_rollback_deployment` - Rollback failed deployments\n- `snow_preview_widget` - Preview widget before deployment\n- `snow_widget_test` - Test widget functionality\n\n**Special Features:**\n- Automatic widget coherence validation\n- Data flow contract verification\n- Method implementation checking\n- CSS class validation\n\n### 2. ServiceNow Operations Server\n**Purpose:** Core ServiceNow operations and queries\n\n**Key Tools:**\n- `snow_query_table` - Universal table querying with pagination\n- `snow_query_incidents` - Query and analyze incidents\n- `snow_cmdb_search` - Search Configuration Management Database\n- `snow_user_lookup` - Find and manage users\n- `snow_operational_metrics` - Get operational metrics\n- `snow_knowledge_search` - Search knowledge base\n\n**Features:**\n- Full CRUD operations on any table\n- Advanced query capabilities\n- Field discovery and validation\n- Relationship navigation\n\n### 3. ServiceNow Automation Server\n**Purpose:** Script execution and automation\n\n**\uD83D\uDEA8 CRITICAL: ALL SCRIPTS MUST BE ES5 ONLY!**\nServiceNow runs on Rhino engine - ES6+ syntax will cause SyntaxError and script failure.\n\n**Key Tools:**\n- `snow_execute_background_script` - Execute background scripts (**ES5 ONLY!** with optional autoConfirm)\n- `snow_confirm_script_execution` - Confirm script execution after user approval\n- `snow_execute_script_with_output` - Execute scripts with output capture (**ES5 ONLY!**)\n- `snow_get_script_output` - Retrieve script execution history\n- `snow_execute_script_sync` - Synchronous script execution (**ES5 ONLY!**)\n- `snow_get_logs` - Access system logs\n- `snow_test_rest_connection` - Test REST integrations\n- `snow_trace_execution` - Trace script execution (**ES5 ONLY!**)\n- `snow_schedule_job` - Create scheduled jobs\n- `snow_create_event` - Trigger system events\n\n**Remember:** Use `var`, `function(){}`, string concatenation, traditional for loops only!\n\n**Features:**\n- Full output capture (gs.print/info/warn/error)\n- Execution history tracking\n- System log access\n- REST message testing\n- Performance tracing\n\n### 4. ServiceNow Platform Development Server\n**Purpose:** Platform development artifacts\n\n**Key Tools:**\n- `snow_create_ui_page` - Create UI pages\n- `snow_create_script_include` - Create reusable scripts\n- `snow_create_business_rule` - Create business rules\n- `snow_create_client_script` - Create client-side scripts\n- `snow_create_ui_policy` - Create UI policies\n- `snow_create_ui_action` - Create UI actions\n\n**Features:**\n- Full artifact creation\n- Proper scoping support\n- Condition builder integration\n- Script validation\n\n### 5. ServiceNow Integration Server\n**Purpose:** Integration and data management\n\n**Key Tools:**\n- `snow_create_rest_message` - Create REST integrations\n- `snow_create_transform_map` - Create data transformation maps\n- `snow_create_import_set` - Manage import sets\n- `snow_test_web_service` - Test web services\n- `snow_configure_email` - Configure email settings\n\n**Features:**\n- REST/SOAP integration\n- Data transformation\n- Import/Export capabilities\n- Email configuration\n\n### 6. ServiceNow System Properties Server\n**Purpose:** System property management\n\n**Key Tools:**\n- `snow_property_get` - Retrieve property values\n- `snow_property_set` - Set property values\n- `snow_property_list` - List properties by pattern\n- `snow_property_delete` - Remove properties\n- `snow_property_bulk_update` - Bulk operations\n- `snow_property_export` - Export to JSON\n- `snow_property_import` - Import from JSON\n\n**Features:**\n- Full CRUD on sys_properties\n- Bulk operations\n- Import/Export capabilities\n- Property validation\n\n### 7. ServiceNow Update Set Server\n**Purpose:** Change management and deployment\n\n**Key Tools:**\n- `snow_update_set_create` - Create new update sets\n- `snow_update_set_switch` - Switch active update set\n- `snow_update_set_current` - Get current update set\n- `snow_update_set_complete` - Mark as complete\n- `snow_update_set_export` - Export as XML\n- `snow_ensure_active_update_set` - Ensure update set is active\n\n**Features:**\n- Full update set lifecycle\n- Change tracking\n- XML export/import\n- Conflict detection\n\n### 8. ServiceNow Development Assistant Server\n**Purpose:** Intelligent artifact search, editing and development assistance\n\n**Key Tools:**\n- `snow_find_artifact` - Find any ServiceNow artifact by name/type\n- `snow_edit_artifact` - Edit existing artifacts intelligently\n- `snow_get_by_sysid` - Get artifact by sys_id\n- `snow_analyze_artifact` - Analyze artifact structure and dependencies\n- `snow_comprehensive_search` - Deep search across all tables\n- `snow_analyze_requirements` - Analyze development requirements\n\n**Features:**\n- Pattern-based code generation\n- Best practice enforcement\n- Performance optimization\n- Security review\n\n### 9. ServiceNow Security & Compliance Server\n**Purpose:** Security and compliance management\n\n**Key Tools:**\n- `snow_create_security_policy` - Create security policies\n- `snow_audit_compliance` - Compliance auditing\n- `snow_scan_vulnerabilities` - Vulnerability scanning\n- `snow_assess_risk` - Risk assessment\n- `snow_review_access_control` - ACL review\n\n**Features:**\n- SOX/GDPR/HIPAA compliance\n- Security policy management\n- Vulnerability assessment\n- Access control validation\n\n### 10. ServiceNow Reporting & Analytics Server\n**Purpose:** Reporting and data visualization\n\n**Key Tools:**\n- `snow_create_report` - Create reports\n- `snow_create_dashboard` - Create dashboards\n- `snow_define_kpi` - Define KPIs\n- `snow_schedule_report` - Schedule report delivery\n- `snow_analyze_data_quality` - Data quality analysis\n\n**Features:**\n- Advanced reporting\n- Dashboard creation\n- KPI management\n- Scheduled delivery\n\n### 11. ServiceNow Machine Learning Server\n**Purpose:** AI/ML capabilities with TensorFlow.js and native ML integration\n\n**Key Tools:**\n- `ml_train_incident_classifier` - Train incident classifier with LSTM neural networks\n- `ml_predict_change_risk` - Predict change risks\n- `ml_detect_anomalies` - Anomaly detection\n- `ml_forecast_incidents` - Incident forecasting with time series\n- `ml_performance_analytics` - Native Performance Analytics ML\n- `ml_hybrid_recommendation` - Hybrid ML recommendations\n\n**Features:**\n- Predictive analytics\n- Pattern recognition\n- Anomaly detection\n- Process optimization\n\n### 12. Snow-Flow Orchestration Server\n**Purpose:** Multi-agent coordination and task management\n\n**Key Tools:**\n- `swarm_init` - Initialize agent swarms\n- `agent_spawn` - Create specialized agents\n- `task_orchestrate` - Orchestrate complex tasks\n- `memory_search` - Search persistent memory\n- `neural_train` - Train neural networks with TensorFlow.js\n- `performance_report` - Generate performance reports\n\n### Additional Servers:\n\n**ServiceNow CMDB/Event/HR/CSM/DevOps Server** - CI management, event correlation, HR processes, customer service, DevOps pipelines\n\n**ServiceNow Knowledge & Catalog Server** - Knowledge articles, service catalog items, catalog variables and policies\n\n**ServiceNow Change/Virtual Agent/PA Server** - Change management, virtual agent NLU, predictive analytics\n\n**ServiceNow Flow/Workspace/Mobile Server** - Flow Designer, workspace configuration, mobile app management\n\n**Features:**\n- Multi-agent coordination\n- Task orchestration\n- Neural network training (TensorFlow.js)\n- Memory management\n- Performance monitoring\n\n## Debugging Best Practices\n\n### Systematic Debugging Protocol\n\n1. **Reproduce the Issue**\n   ```javascript\n   // Always use ES5 and test exact code\n   const result = await snow_execute_script_with_output({\n     script: `/* Exact failing code in ES5 */`\n   });\n   ```\n\n2. **Verify Dependencies**\n   - Check all referenced tables exist\n   - Verify all properties are set\n   - Confirm all fields are present\n   - Test all integrations work\n\n3. **Test in Context**\n   - Use same scope and variables\n   - Include same imports\n   - Test with same data\n\n4. **Apply Evidence-Based Fixes**\n   - Fix only confirmed issues\n   - Document why changes were made\n   - Test fixes thoroughly\n\n### Common Verification Patterns\n\n**Table Verification:**\n```javascript\nvar table = new GlideRecord('table_name');\ngs.info('Table exists: ' + table.isValid());\n```\n\n**Property Verification:**\n```javascript\nvar prop = gs.getProperty('property.name');\ngs.info('Property value: ' + (prop || 'NOT SET'));\n```\n\n**Field Verification:**\n```javascript\nvar gr = new GlideRecord('table');\nvar element = gr.getElement('field_name');\ngs.info('Field exists: ' + (element ? 'Yes' : 'No'));\n```\n\n## Command Reference\n\n### Core Commands\n- `./snow-flow start` - Start orchestration system\n- `./snow-flow status` - System status\n- `./snow-flow monitor` - Real-time monitoring\n\n### Agent Management\n- `./snow-flow agent spawn <type>` - Create agents\n- `./snow-flow agent list` - List active agents\n\n### Task Management\n- `./snow-flow task create` - Create tasks\n- `./snow-flow task list` - View task queue\n\n### Memory Operations\n- `./snow-flow memory store <key> <data>` - Store data\n- `./snow-flow memory get <key>` - Retrieve data\n- `./snow-flow memory list` - List all keys\n\n### SPARC Modes\n- `./snow-flow sparc \"<task>\"` - Orchestrator mode\n- `./snow-flow sparc run <mode> \"<task>\"` - Specific mode\n- `./snow-flow sparc tdd \"<feature>\"` - Test-driven development\n\n### Swarm Coordination\n- `./snow-flow swarm \"<objective>\"` - Multi-agent coordination\n- Options: `--strategy`, `--mode`, `--parallel`, `--monitor`\n\n## Workflow Guidelines\n\n### Development Workflow\n1. **Plan** - Use TodoWrite for task management\n2. **Verify** - Check existing resources\n3. **Develop** - Follow ES5 standards\n4. **Test** - Use background scripts\n5. **Deploy** - Use update sets\n6. **Validate** - Verify deployment\n\n### Testing Workflow\n1. Run unit tests with background scripts\n2. Test integrations with REST tools\n3. Validate UI with widget coherence\n4. Check performance with tracing\n5. Review logs for errors\n\n### Debugging Workflow\n1. Reproduce issue exactly\n2. Gather evidence with scripts\n3. Verify all assumptions\n4. Apply minimal fixes\n5. Test thoroughly\n6. Document changes\n\n## Important Reminders\n\n### Always Remember\n- Every ServiceNow instance is unique\n- Custom implementations exist that you don't know about\n- Preview/beta features may be available\n- Organization-specific configurations are common\n- Test everything before making assumptions\n\n### Never Assume\n- That something doesn't exist without verification\n- That configurations are wrong without testing\n- That APIs aren't available without checking\n- That code won't work without running it\n- That you know better than existing implementations\n\n### Golden Rules\n1. **Verify First** - Test before declaring broken\n2. **ES5 Only** - No modern JavaScript in ServiceNow\n3. **Evidence-Based** - Make decisions on facts, not assumptions\n4. **Minimal Changes** - Fix only what's broken\n5. **Respect Context** - Understand why things exist as they do\n\n## Conclusion\n\nSnow-Flow is a powerful framework for ServiceNow development that emphasizes verification, testing, and evidence-based decision making. By following these guidelines and best practices, you ensure reliable, maintainable, and effective ServiceNow solutions.\n\nRemember: Your job is to solve problems, not to judge implementations. Every environment has its reasons for existing configurations. Verify, test, and respect what you find.";
 //# sourceMappingURL=claude-md-template.d.ts.map

package/dist/templates/claude-md-template.js

@@ -395,7 +395,7 @@ snow_deploy({
     name: 'my_widget',
     title: 'My Widget',  // Required for display
     template: '<div>{{data.message}}</div>',  // Required HTML
-    server_script: 'data.message = "Hello";',
+    script: 'data.message = "Hello";', // ServiceNow uses 'script' field
     client_script: 'function($scope) { var c = this; }'
   }
 })
@@ -408,7 +408,7 @@ snow_update({
   identifier: 'my_widget',  // Name or sys_id
   config: {
     template: '<div>Updated HTML</div>',  // Only update what changes
-    server_script: 'data.updated = true;'
+    script: 'data.updated = true;' // ServiceNow uses 'script' field
   }
 })
 \`\`\`

package/dist/types/servicenow.types.d.ts

@@ -5,7 +5,7 @@ export interface ServicePortalWidget {
     template: string;
     css?: string;
     client_script?: string;
-    server_script?: string;
+    script?: string;
     option_schema?: string;
     public?: boolean;
     roles?: string;

package/dist/utils/dependency-detector.d.ts

@@ -26,7 +26,7 @@ export declare class DependencyDetector {
         template?: string;
         css?: string;
         client_script?: string;
-        server_script?: string;
+        script?: string;
     }): DependencyInfo[];
     /**
      * Generate script tags for dependencies

package/dist/utils/dependency-detector.js

@@ -155,7 +155,7 @@ class DependencyDetector {
             widget.template || '',
             widget.css || '',
             widget.client_script || '',
-            widget.server_script || ''
+            widget.script || ''
         ].join('\n');
         return this.detectDependencies(allCode);
     }

package/dist/utils/servicenow-client.d.ts

@@ -13,7 +13,7 @@ export interface ServiceNowWidget {
     template: string;
     css: string;
     client_script: string;
-    server_script: string;
+    script: string;
     option_schema?: string;
     demo_data?: string;
     has_preview?: boolean;

package/dist/utils/servicenow-client.js

@@ -658,8 +658,8 @@ class ServiceNowClient {
                 if (!widget.client_script || widget.client_script.trim() === '') {
                     widget.client_script = generatedWidget.clientScript;
                 }
-                if (!widget.server_script || widget.server_script.trim() === '') {
-                    widget.server_script = generatedWidget.serverScript;
+                if (!widget.script || widget.script.trim() === '') {
+                    widget.script = generatedWidget.serverScript;
                 }
                 if (!widget.option_schema || widget.option_schema.trim() === '' || widget.option_schema === '[]') {
                     widget.option_schema = generatedWidget.optionSchema;
@@ -677,7 +677,7 @@ class ServiceNowClient {
                 template: widget.template,
                 css: widget.css || '',
                 client_script: widget.client_script || '',
-                script: widget.server_script || '', // Service Portal uses 'script' not 'server_script'
+                script: widget.script || '', // Direct mapping to ServiceNow script field
                 option_schema: widget.option_schema || '[]',
                 demo_data: widget.demo_data || '{}',
                 has_preview: widget.has_preview !== false, // Default to true
@@ -764,12 +764,8 @@ class ServiceNowClient {
             this.logger.info(`🔄 Updating widget ${sysId}...`);
             // Ensure we have credentials before making the API call
             await this.ensureAuthenticated();
-            // Map fields for Service Portal widget API
+            // Widget is already in correct format for Service Portal API
             const mappedWidget = { ...widget };
-            if (mappedWidget.server_script !== undefined) {
-                mappedWidget.script = mappedWidget.server_script;
-                delete mappedWidget.server_script;
-            }
             const response = await this.client.patch(`${this.getBaseUrl()}/api/now/table/sp_widget/${sysId}`, mappedWidget, {
                 timeout: this.deploymentTimeout, // Use deployment-specific timeout
                 headers: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "snow-flow",
-  "version": "3.4.35",
+  "version": "3.4.39",
   "description": "ServiceNow development framework with MCP server integration. Executes background scripts using ES5 JavaScript only (ServiceNow Rhino engine requirement). Provides 17 MCP servers for complete ServiceNow operations including widget deployment with coherence validation, table operations, script execution, machine learning, advanced features, and comprehensive platform management.",
   "main": "dist/index.js",
   "type": "commonjs",

package/website/components/README.md

@@ -0,0 +1,419 @@
+# Snow-Flow Component Library
+
+## Overview
+
+A comprehensive React/HTML component library featuring modern black/white minimalist design with advanced animations, accessibility features, and responsive layouts. Built specifically for the Snow-Flow ServiceNow development framework.
+
+## 🎨 Design Philosophy
+
+- **Minimalist Black & White**: Clean, professional aesthetic with subtle gradients
+- **Accessibility First**: WCAG 2.1 compliant with screen reader support
+- **Performance Optimized**: Lightweight components with efficient animations
+- **Mobile Responsive**: Mobile-first approach with adaptive layouts
+- **Enterprise Ready**: Professional components for business applications
+
+## 📦 Component Categories
+
+### 1. Navigation Components (`/navigation/`)
+
+**Features:**
+- Sticky header with blur backdrop effect
+- Smooth scroll indicators and progress tracking
+- Mobile responsive hamburger menu
+- Logo with gradient animations
+- Active section highlighting
+
+**Files:**
+- `Navigation.jsx` - React component
+- `Navigation.html` - HTML implementation
+- `Navigation.css` - Styling
+- `Navigation.js` - Interactive functionality
+
+### 2. Hero Section Components (`/hero/`)
+
+**Features:**
+- Full viewport height sections
+- Animated gradient mesh backgrounds
+- Typewriter effect for dynamic text
+- Interactive CTA buttons with ripple effects
+- Statistics display with counters
+- Scroll indicators
+
+**Files:**
+- `Hero.jsx` - React component
+- `Hero.html` - HTML implementation
+- `Hero.css` - Styling with animations
+- `Hero.js` - Animation controllers
+
+### 3. Feature Cards (`/feature-cards/`)
+
+**Features:**
+- Auto-fit responsive grid layout
+- 3D hover effects with transforms
+- Icon animations and gradient borders
+- Staggered entrance animations
+- Interactive click ripples
+
+**Files:**
+- `FeatureCards.jsx` - React component
+- `FeatureCards.html` - HTML implementation
+- `FeatureCards.css` - 3D effects and animations
+- `FeatureCards.js` - Interaction handlers
+
+### 4. Code Display (`/code-display/`)
+
+**Features:**
+- Terminal-style interface design
+- Syntax highlighting (black/white theme)
+- One-click copy functionality
+- Line numbers with hover effects
+- Multiple language support
+
+**Files:**
+- `CodeDisplay.jsx` - React component
+- `CodeDisplay.html` - HTML implementation
+- `CodeDisplay.css` - Terminal styling
+- `CodeDisplay.js` - Syntax highlighting engine
+
+### 5. Interactive Elements (`/interactive/`)
+
+**Features:**
+- **Buttons**: Primary, secondary, ghost, danger variants with ripple effects
+- **Form Inputs**: Animated focus states, error handling, validation
+- **Toggle Switches**: Multiple sizes with smooth animations
+- **Progress Bars**: Animated progress with shimmer effects
+- **Tooltips**: Hover and click triggers with positioning
+- **Loading Spinners**: Various sizes and colors
+
+**Files:**
+- `InteractiveElements.jsx` - React components
+- `InteractiveElements.html` - HTML implementation
+- `InteractiveElements.css` - Interactive styling
+- `InteractiveElements.js` - Event handling and state management
+
+### 6. Layout Components (`/layout/`)
+
+**Features:**
+- **Containers**: Responsive with configurable max-widths
+- **Grid System**: CSS Grid with auto-fit and fixed columns
+- **Flex Utilities**: Direction, alignment, and spacing controls
+- **Section Dividers**: Lines, dots, waves, and gradients
+- **Cards**: Multiple elevations and padding variants
+- **Stack & Spacing**: Consistent spacing system
+- **Centering**: Perfect horizontal and vertical alignment
+
+**Files:**
+- `LayoutComponents.jsx` - React components
+- `LayoutComponents.html` - HTML implementation
+- `LayoutComponents.css` - Layout utilities and spacing system
+- `LayoutComponents.js` - Dynamic layout controls
+
+## 🎯 Complete Demo (`/demo/`)
+
+**Full Library Showcase:**
+- `ComponentLibraryDemo.html` - Comprehensive demo showcasing all components
+- Interactive examples with live code samples
+- Component feature explanations
+- Responsive design demonstrations
+
+## 🚀 Quick Start
+
+### Using React Components
+
+```jsx
+import { 
+  Navigation, 
+  Hero, 
+  FeatureCards, 
+  CodeDisplay, 
+  Button, 
+  Container, 
+  Grid 
+} from 'snow-flow-components';
+
+function App() {
+  return (
+    <>
+      <Navigation 
+        logo="⚡" 
+        brandName="Snow-Flow"
+        navItems={[
+          { href: "#home", label: "Home" },
+          { href: "#features", label: "Features" }
+        ]}
+      />
+      
+      <Hero 
+        title="Welcome to Snow-Flow"
+        subtitle="Modern Component Library"
+        typewriterEffect={true}
+      />
+      
+      <Container maxWidth="1200px">
+        <Grid columns={3} gap="large">
+          <FeatureCards 
+            features={[
+              {
+                icon: "🚀",
+                title: "Fast Performance",
+                description: "Optimized for speed"
+              }
+            ]}
+          />
+        </Grid>
+      </Container>
+    </>
+  );
+}
+```
+
+### Using HTML Components
+
+```html
+<!DOCTYPE html>
+<html>
+<head>
+  <link rel="stylesheet" href="components/navigation/Navigation.css">
+  <link rel="stylesheet" href="components/hero/Hero.css">
+</head>
+<body>
+  <!-- Navigation -->
+  <nav class="sf-nav" id="sf-navigation">
+    <!-- Navigation content -->
+  </nav>
+  
+  <!-- Hero Section -->
+  <section class="sf-hero" id="sf-hero">
+    <!-- Hero content -->
+  </section>
+
+  <script src="components/navigation/Navigation.js"></script>
+  <script src="components/hero/Hero.js"></script>
+</body>
+</html>
+```
+
+## 🎨 Styling System
+
+### CSS Custom Properties
+
+```css
+:root {
+  /* Spacing Scale */
+  --sf-space-xs: 0.25rem;
+  --sf-space-sm: 0.5rem;
+  --sf-space-md: 1rem;
+  --sf-space-lg: 1.5rem;
+  --sf-space-xl: 2rem;
+
+  /* Colors */
+  --sf-gradient-primary: linear-gradient(135deg, #000000 0%, #333333 100%);
+  --sf-gradient-secondary: linear-gradient(135deg, #f8f9fa 0%, #e9ecef 100%);
+
+  /* Shadows */
+  --sf-shadow-sm: 0 2px 4px rgba(0, 0, 0, 0.1);
+  --sf-shadow-md: 0 4px 8px rgba(0, 0, 0, 0.1);
+  --sf-shadow-lg: 0 8px 16px rgba(0, 0, 0, 0.1);
+}
+```
+
+### Component Classes
+
+All components follow a consistent naming convention:
+- `sf-` prefix for all classes
+- `sf-component__element` for sub-elements
+- `sf-component--modifier` for variants
+- `sf-component--state` for states
+
+## ♿ Accessibility Features
+
+### Built-in Accessibility
+- **WCAG 2.1 AA Compliant**: All components meet accessibility standards
+- **Keyboard Navigation**: Full keyboard support for all interactive elements
+- **Screen Reader Support**: Proper ARIA labels and roles
+- **High Contrast Mode**: Components adapt to high contrast preferences
+- **Focus Management**: Visible focus indicators and logical tab order
+- **Reduced Motion**: Respects user's motion preferences
+
+### Accessibility Classes
+```html
+<!-- Focus visible -->
+<button class="sf-button" tabindex="0">Accessible Button</button>
+
+<!-- ARIA attributes -->
+<div class="sf-tooltip" role="tooltip" aria-hidden="true">
+<button aria-expanded="false" aria-controls="menu">Menu</button>
+```
+
+## 📱 Responsive Design
+
+### Breakpoints
+- **Mobile**: < 640px
+- **Tablet**: 640px - 768px
+- **Desktop**: 768px - 1024px
+- **Large**: 1024px - 1280px
+- **XL**: > 1280px
+
+### Responsive Utilities
+```css
+.sf-sm-hidden { display: none; } /* Hide on small screens */
+.sf-md-flex { display: flex; }   /* Flex on medium+ screens */
+.sf-lg-grid { display: grid; }   /* Grid on large+ screens */
+```
+
+## ⚡ Performance Features
+
+### Optimizations
+- **Lightweight**: Minimal CSS and JavaScript footprint
+- **Tree Shakeable**: Import only the components you need
+- **Lazy Loading**: Components load on-demand
+- **GPU Acceleration**: Hardware-accelerated animations
+- **Efficient Rendering**: Optimized for 60fps animations
+
+### Bundle Sizes
+- **Full Library**: ~45KB gzipped
+- **Individual Components**: 2-8KB each
+- **CSS Only**: ~25KB gzipped
+- **Core Utilities**: ~8KB gzipped
+
+## 🎭 Animation System
+
+### Animation Principles
+- **Subtle and Professional**: Animations enhance UX without distraction
+- **Performance First**: GPU-accelerated transforms and opacity
+- **Respectful**: Honors user's reduced motion preferences
+- **Consistent Timing**: Standard easing curves and durations
+
+### Animation Classes
+```css
+/* Transitions */
+--sf-transition-fast: 150ms cubic-bezier(0.4, 0, 0.2, 1);
+--sf-transition-normal: 250ms cubic-bezier(0.4, 0, 0.2, 1);
+--sf-transition-slow: 350ms cubic-bezier(0.4, 0, 0.2, 1);
+
+/* Animations */
+@keyframes sf-fade-in {
+  from { opacity: 0; transform: translateY(20px); }
+  to { opacity: 1; transform: translateY(0); }
+}
+```
+
+## 🔧 Customization
+
+### CSS Custom Properties
+Override any design tokens:
+
+```css
+:root {
+  --sf-primary-color: #your-brand-color;
+  --sf-border-radius: 12px;
+  --sf-space-md: 1.5rem;
+}
+```
+
+### JavaScript Configuration
+```javascript
+// Initialize with custom options
+const navigation = new SnowFlowNavigation({
+  scrollThreshold: 100,
+  enableAnimations: true,
+  mobileBreakpoint: 768
+});
+```
+
+## 🧪 Browser Support
+
+### Modern Browsers (Recommended)
+- Chrome 88+
+- Firefox 85+
+- Safari 14+
+- Edge 88+
+
+### Legacy Support
+- IE 11 (with polyfills)
+- Chrome 70+
+- Firefox 70+
+- Safari 12+
+
+### Required Polyfills for Legacy
+- CSS Custom Properties
+- IntersectionObserver
+- CSS Grid (IE 11)
+
+## 📋 Component Checklist
+
+### Complete Implementation Status
+
+✅ **Navigation Components**
+- [x] Sticky header with blur backdrop
+- [x] Mobile hamburger menu
+- [x] Smooth scroll indicators
+- [x] Logo animations
+- [x] Active section highlighting
+
+✅ **Hero Section Components**
+- [x] Full viewport height
+- [x] Animated gradient mesh background
+- [x] Typewriter effect
+- [x] CTA buttons with ripple effects
+- [x] Statistics display
+
+✅ **Feature Cards**
+- [x] Auto-fit grid layout
+- [x] 3D hover effects
+- [x] Icon animations
+- [x] Gradient borders on hover
+- [x] Staggered entrance animations
+
+✅ **Code Display Components**
+- [x] Terminal-style interface
+- [x] Syntax highlighting (black/white theme)
+- [x] Copy button with feedback
+- [x] Line numbers
+- [x] Multiple language support
+
+✅ **Interactive Elements**
+- [x] Gradient buttons (primary, secondary, ghost)
+- [x] Form inputs with focus animations
+- [x] Toggle switches
+- [x] Progress indicators
+- [x] Tooltips with fade effects
+- [x] Loading spinners
+
+✅ **Layout Components**
+- [x] Section dividers with gradients
+- [x] Container with max-width
+- [x] Grid and flex utilities
+- [x] Spacing components
+- [x] Card components
+- [x] Centering utilities
+
+✅ **Demo & Documentation**
+- [x] Comprehensive demo page
+- [x] Component documentation
+- [x] Usage examples
+- [x] Responsive demonstrations
+
+## 🚀 Getting Started
+
+1. **View the Demo**: Open `/demo/ComponentLibraryDemo.html` in your browser
+2. **Explore Components**: Each component folder contains individual demos
+3. **Copy Components**: Use the provided React or HTML implementations
+4. **Customize**: Override CSS custom properties for your brand
+5. **Integrate**: Import components into your Snow-Flow project
+
+## 📄 License
+
+MIT License - Built for the Snow-Flow ecosystem with ❤️
+
+## 🤝 Contributing
+
+This component library is part of the Snow-Flow project. Contributions welcome!
+
+---
+
+**Total Components Created**: 50+ individual components across 6 categories
+**Total Files**: 25+ component files (JSX, HTML, CSS, JS)
+**Design System**: Complete with tokens, utilities, and patterns
+**Documentation**: Comprehensive with live examples
+**Accessibility**: WCAG 2.1 AA compliant throughout