snow-flow 3.6.0 → 3.6.2

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

@@ -1,1064 +1,314 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.CLAUDE_MD_TEMPLATE = void 0;
-exports.CLAUDE_MD_TEMPLATE = `# Snow-Flow Configuration & Best Practices
+exports.CLAUDE_MD_TEMPLATE_VERSION = exports.CLAUDE_MD_TEMPLATE = void 0;
+exports.CLAUDE_MD_TEMPLATE = `# Snow-Flow ServiceNow Development Framework
 
-This document provides comprehensive instructions for Snow-Flow, an advanced ServiceNow development and orchestration framework powered by Claude AI.
+## 🚨 ABSOLUTE RULES - NO EXCEPTIONS
 
-## Table of Contents
-1. [Core Philosophy](#core-philosophy)
-2. [Fundamental Rules](#fundamental-rules)
-3. [ServiceNow Development Standards](#servicenow-development-standards)
-4. [MCP Server Capabilities](#mcp-server-capabilities)
-5. [Debugging Best Practices](#debugging-best-practices)
-6. [Command Reference](#command-reference)
-7. [Workflow Guidelines](#workflow-guidelines)
+### Rule #1: NO MOCK DATA - EVERYTHING REAL & COMPLETE
+**FORBIDDEN:** Mock data, placeholders, TODOs, stub implementations, test values, simulations, "this would normally...", partial implementations.
+**REQUIRED:** Complete, production-ready, fully functional code. Take time to implement EVERYTHING properly. Real integrations, comprehensive error handling, full validation.
 
-## CRITICAL: Widget Debugging Must Use Local Sync
+### Rule #2: ES5 ONLY - ServiceNow Rhino Engine
+**NEVER USE:** const/let, arrow functions =>, template literals \`\${}\`, destructuring, for...of, default parameters, classes
+**ALWAYS USE:** var, function(){}, string concatenation +, traditional for loops, typeof checks
 
-### 🔴 When User Reports Widget Issues, ALWAYS Use \`snow_pull_artifact\` FIRST!
+### Rule #3: VERIFY FIRST - Never Assume
+Test before claiming broken. Check resources exist. Validate configurations. Evidence-based fixes only.
 
-**Common scenarios that REQUIRE Local Sync:**
-- "Widget skips questions" → \`snow_pull_artifact\`
-- "Form doesn't submit properly" → \`snow_pull_artifact\`
-- "Data not displaying" → \`snow_pull_artifact\`
-- "Button doesn't work" → \`snow_pull_artifact\`
-- "Debug this widget" → \`snow_pull_artifact\`
-- "Fix widget issue" → \`snow_pull_artifact\`
+## 📋 MCP SERVERS & TOOLS (18 Servers, 200+ Tools)
 
-**DO NOT use \`snow_query_table\` for widget debugging!** It will hit token limits and you can't use native search/edit tools.
-
-## Core Philosophy
-
-### The Prime Directive: Verify, Don't Assume
-
-Snow-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.
-
-**Cardinal Rules:**
-1. If code references something, it probably exists
-2. Test before declaring something broken
-3. Verify before modifying
-4. Fix only what's confirmed broken
-5. Respect existing configurations
-
-### The Verification-First Approach
-
-\`\`\`javascript
-// Before claiming anything doesn't work or exist:
-// Step 1: Test the actual implementation
-const verify = await snow_execute_script_with_output({
-  script: \`/* Test the exact code or resource */\`
-});
-
-// Step 2: Check if resources exist
-const tableCheck = await snow_discover_table_fields({
-  table_name: 'potentially_custom_table'
-});
-
-// Step 3: Validate configurations
-const propertyCheck = await snow_property_manager({
-  action: 'get',
-  name: 'system.property'
-});
-
-// Step 4: Only then make informed decisions
+### 1. **servicenow-local-development** 🔧 Widget/Artifact Sync
 \`\`\`
-
-### 🔄 CRITICAL: Sync User Modifications Before Working
-
-**When a user mentions they've modified an artifact directly in ServiceNow, ALWAYS fetch the latest version first!**
-
-If a user says any of these:
-- "I've updated the widget in ServiceNow"
-- "I made some changes to the flow"
-- "I modified the script"
-- "I adjusted the configuration"
-- "Ik heb het zelf aangepast" (Dutch: I adjusted it myself)
-
-**YOU MUST:**
-
-1. **Immediately fetch the current version from ServiceNow:**
-\`\`\`javascript
-// For any artifact the user has modified
-const currentVersion = await snow_query_table({
-  table: 'artifact_table_name',
-  query: \`sys_id=\${artifact_sys_id}\`,
-  fields: ['*'],  // Get all fields
-  limit: 1
-});
-
-// Or for widgets specifically
-const widgetData = await snow_query_table({
-  table: 'sp_widget',
-  query: \`sys_id=\${widget_sys_id}\`,
-  fields: ['name', 'template', 'client_script', 'script', 'css', 'option_schema'],
-  limit: 1
-});
-
-// Or use snow_get_by_sysid for comprehensive retrieval
-const artifact = await snow_get_by_sysid({
-  table: 'table_name',
-  sys_id: 'the_sys_id'
-});
+snow_pull_artifact - Pull ANY artifact to local files for native editing
+snow_push_artifact - Push local changes back to ServiceNow  
+snow_cleanup_artifacts - Clean local artifact cache
+snow_get_sync_status - Check artifact sync status
+snow_list_local_artifacts - List all pulled artifacts
 \`\`\`
 
-2. **Analyze the user's modifications:**
-   - Review what they changed
-   - Understand their intent
-   - Preserve their modifications
-
-3. **Build upon their changes:**
-   - Don't overwrite their work
-   - Integrate new features with their modifications
-   - Maintain their code style and patterns
-
-4. **Inform the user:**
-   - Acknowledge that you've fetched their latest changes
-   - Summarize what modifications you found
-   - Explain how you'll build upon their work
-
-**Example Workflow:**
-\`\`\`javascript
-// User: "I've updated the widget to add a loading spinner"
-// Snow-Flow response:
-
-// 1. Fetch current version
-const widget = await snow_query_table({
-  table: 'sp_widget',
-  query: \`sys_id=\${widgetSysId}\`,
-  fields: ['*'],
-  limit: 1
-});
-
-// 2. Analyze changes
-console.log("✅ Fetched your latest widget version from ServiceNow");
-console.log("📝 I see you've added a loading spinner in the template");
-
-// 3. Work with the updated version
-// ... make additional changes based on user's modifications ...
+### 2. **servicenow-deployment** 🚀 Complete Deployment System
 \`\`\`
-
-**Why This Matters:**
-- User modifications are not tracked locally
-- Working with outdated versions causes conflicts
-- User's work could be lost if not synced
-- Builds trust by respecting user's contributions
-- Ensures coherent development flow
-
-## Fundamental Rules
-
-### Rule 1: 🚨 ES5 JavaScript ONLY in ServiceNow - NO EXCEPTIONS!
-
-**⚠️ CRITICAL WARNING: ServiceNow uses Rhino engine - ES6/ES7/ES8+ WILL FAIL!**
-
-ServiceNow's server-side JavaScript runs on Mozilla Rhino which **ONLY supports ES5 (2009)**. Any modern JavaScript syntax will cause **RUNTIME ERRORS**.
-
-**❌ THESE WILL CRASH SERVICENOW (DO NOT USE):**
-\`\`\`javascript
-// ❌ ES6+ features that BREAK ServiceNow:
-const data = [];           // SyntaxError: missing ; after for-loop initializer
-let items = [];            // SyntaxError: missing ; after for-loop initializer  
-const fn = () => {};       // SyntaxError: syntax error
-var msg = \`Hello \${name}\`; // SyntaxError: syntax error
-for (let item of items){}  // SyntaxError: missing ; after for-loop initializer
-var {name, id} = user;     // SyntaxError: destructuring declaration not supported
-array.forEach(x => {});    // SyntaxError: syntax error  
-array.map(x => x.id);      // SyntaxError: syntax error
-function test(param = 'default') {} // SyntaxError: syntax error
-class MyClass {}           // SyntaxError: missing ; after for-loop initializer
+snow_deploy - Create NEW artifacts (widgets, flows, scripts, pages)
+snow_update - UPDATE existing artifacts directly
+snow_validate_deployment - Validate before deploy
+snow_rollback_deployment - Rollback failed deployments
+snow_preview_widget - Preview widget rendering
+snow_widget_test - Test widget functionality
+snow_deployment_history - View deployment history
+snow_check_widget_coherence - Validate HTML/Client/Server communication
 \`\`\`
 
-**✅ ONLY USE ES5 SYNTAX (THIS WORKS):**
-\`\`\`javascript
-// ✅ ES5 compatible code that WORKS in ServiceNow:
-var data = [];
-var items = [];
-function fn() { return 'result'; }
-var msg = 'Hello ' + name;
-for (var i = 0; i < items.length; i++) {
-  var item = items[i];
-}
-var name = user.name;
-var id = user.id;
-for (var j = 0; j < array.length; j++) {
-  // Process array[j]
-}
-function test(param) {
-  if (typeof param === 'undefined') param = 'default';
-}
+### 3. **servicenow-operations** 📊 Core Operations
 \`\`\`
-
-**🔥 COMMON MISTAKES THAT BREAK SERVICENOW:**
-1. **Arrow Functions**: \`() => {}\` → Use \`function() {}\`
-2. **Template Literals**: \`\` \`\${var}\` \`\` → Use \`'text ' + var\`
-3. **Let/Const**: \`let x\` → Use \`var x\`
-4. **Destructuring**: \`{a, b} = obj\` → Use \`obj.a\`, \`obj.b\`
-5. **For...of**: \`for (x of arr)\` → Use \`for (var i=0; i<arr.length; i++)\`
-6. **Default Parameters**: \`fn(x='default')\` → Use \`typeof x === 'undefined'\`
-7. **Array Methods with Arrows**: \`.map(x => x)\` → Use \`.map(function(x) { return x; })\`
-
-### Rule 2: Background Scripts for Verification Only (Not Widget Updates!)
-
-**CRITICAL DISTINCTION:**
-- ✅ Use background scripts for TESTING and VERIFICATION  
-- ❌ Do NOT use background scripts to UPDATE widget fields
-- ✅ Use \`snow_update\` to directly modify widget records
-- ❌ Do NOT try to import server scripts into client scripts via background scripts
-
-**🚨 ES5 ENFORCEMENT FOR BACKGROUND SCRIPTS:**
-Background scripts run on ServiceNow's server-side Rhino engine. **EVERY background script MUST be ES5-only or it will fail.**
-
-**Quick ES5 Validation Checklist:**
-- [ ] No \`const\` or \`let\` (only \`var\`)
-- [ ] No arrow functions \`() => {}\` (only \`function() {}\`)
-- [ ] No template literals \`\` \`\${var}\` \`\` (only string concatenation)
-- [ ] No destructuring \`{a, b} = obj\` (only explicit \`obj.a\`)
-- [ ] No \`for...of\` loops (only traditional \`for\` loops)
-- [ ] No default parameters (use \`typeof\` checks)
-- [ ] No modern array methods with arrows (use traditional functions)
-
-Background scripts are excellent for verification and debugging, but widget updates must go through proper MCP tools.
-
-**NEW: Auto-Confirm Mode for Background Scripts (v3.4.10+)**
-You can now skip the human-in-the-loop confirmation for trusted scripts:
-
-\`\`\`javascript
-// Standard mode - requires user confirmation (ES5 ONLY!)
-snow_execute_background_script({
-  script: "var gr = new GlideRecord('incident'); gr.query();", // ✅ ES5 syntax
-  description: "Query incidents",
-  allowDataModification: false
-});
-
-// Auto-confirm mode - executes immediately ⚠️ USE WITH CAUTION!
-snow_execute_background_script({
-  script: "var gr = new GlideRecord('incident'); gr.query();", // ✅ ES5 syntax
-  description: "Query incidents",
-  allowDataModification: false,
-  autoConfirm: true  // ⚠️ Bypasses user confirmation!
-});
-
-// ❌ WRONG - This will FAIL in ServiceNow:
-// script: "const gr = new GlideRecord('incident'); gr.query();", // SyntaxError!
-// script: "incidents.forEach(i => console.log(i.number));",      // SyntaxError!
+snow_query_table - Universal table query with pagination
+snow_query_incidents - Query and analyze incidents
+snow_analyze_incident - AI-powered incident analysis
+snow_auto_resolve_incident - Automated resolution
+snow_cmdb_search - Configuration database search
+snow_user_lookup - Find users and groups
+snow_operational_metrics - Performance metrics
+snow_knowledge_search - Search knowledge base
+snow_catalog_item_manager - Manage service catalog
 \`\`\`
 
-**🚨 ES5 Validation Required:**
-Before using any background script tool, validate your script is ES5-only:
-- No \`const\`/\`let\` (use \`var\`)
-- No arrow functions (use \`function()\`)
-- No template literals (use string concatenation)
-- No destructuring (use explicit property access)
-
-**⚠️ Security Warning:**
-- Only use \`autoConfirm: true\` for verified, safe scripts
-- High-risk operations will still be logged
-- All auto-executions are tracked with audit IDs
-- Default behavior (without autoConfirm) remains unchanged
-
-## 🚨 CRITICAL: Common ES5 Mistakes That Break ServiceNow
-
-ServiceNow developers frequently use modern JavaScript that fails on the Rhino engine. Here are the most common mistakes:
-
-### 🔥 Top ES5 Violations (Fix These Immediately!)
-
-**1. Arrow Functions with Array Methods**
-\`\`\`javascript
-// ❌ BREAKS ServiceNow:
-var activeIncidents = incidents.filter(inc => inc.active);
-var numbers = activeIncidents.map(inc => inc.number);
-
-// ✅ WORKS in ServiceNow:
-var activeIncidents = [];
-for (var i = 0; i < incidents.length; i++) {
-  if (incidents[i].active) {
-    activeIncidents.push(incidents[i]);
-  }
-}
-var numbers = [];
-for (var j = 0; j < activeIncidents.length; j++) {
-  numbers.push(activeIncidents[j].number);
-}
+### 4. **servicenow-automation** ⚙️ Scripts & Automation
 \`\`\`
-
-**2. Template Literals for String Building**
-\`\`\`javascript
-// ❌ BREAKS ServiceNow:
-var message = \`Incident \${incident.number} assigned to \${user.name}\`;
-
-// ✅ WORKS in ServiceNow:
-var message = 'Incident ' + incident.number + ' assigned to ' + user.name;
+snow_execute_background_script - Run ES5 scripts (autoConfirm available)
+snow_execute_script_with_output - Execute with output capture
+snow_execute_script_sync - Synchronous execution
+snow_get_script_output - Retrieve script results
+snow_schedule_job - Create scheduled jobs
+snow_create_event - Trigger system events
+snow_get_logs - Access system logs
+snow_test_rest_connection - Test REST endpoints
+snow_trace_execution - Performance tracing
 \`\`\`
 
-**3. Const/Let Variable Declarations**
-\`\`\`javascript
-// ❌ BREAKS ServiceNow:
-const MAX_RETRIES = 3;
-let currentUser = gs.getUser();
-
-// ✅ WORKS in ServiceNow:
-var MAX_RETRIES = 3;
-var currentUser = gs.getUser();
+### 5. **servicenow-platform-development** 🏗️ Development Artifacts
 \`\`\`
-
-**4. Object Destructuring**
-\`\`\`javascript
-// ❌ BREAKS ServiceNow:
-var {name, email, department} = user;
-var {sys_id: id, short_description: desc} = incident;
-
-// ✅ WORKS in ServiceNow:
-var name = user.name;
-var email = user.email;
-var department = user.department;
-var id = incident.sys_id;
-var desc = incident.short_description;
+snow_create_ui_page - Create UI pages
+snow_create_script_include - Reusable scripts
+snow_create_business_rule - Business rules
+snow_create_client_script - Client-side scripts
+snow_create_ui_policy - UI policies
+snow_create_ui_action - UI actions
+snow_create_acl - Access controls
+snow_create_ui_macro - UI macros
 \`\`\`
 
-**5. For...of Loops**
-\`\`\`javascript
-// ❌ BREAKS ServiceNow:
-for (let incident of incidents) {
-  gs.info('Processing: ' + incident.number);
-}
-
-// ✅ WORKS in ServiceNow:
-for (var i = 0; i < incidents.length; i++) {
-  gs.info('Processing: ' + incidents[i].number);
-}
+### 6. **servicenow-integration** 🔌 Integrations
 \`\`\`
-
-**6. Default Function Parameters**
-\`\`\`javascript
-// ❌ BREAKS ServiceNow:
-function processIncident(incident, priority = 3, assignee = 'unassigned') {
-  // Process incident
-}
-
-// ✅ WORKS in ServiceNow:
-function processIncident(incident, priority, assignee) {
-  if (typeof priority === 'undefined') priority = 3;
-  if (typeof assignee === 'undefined') assignee = 'unassigned';
-  // Process incident
-}
+snow_create_rest_message - REST integrations
+snow_create_soap_message - SOAP integrations
+snow_create_transform_map - Data transformation
+snow_create_import_set - Import management
+snow_test_web_service - Test services
+snow_configure_email - Email configuration
+snow_create_data_source - Data sources
 \`\`\`
 
-### 🎯 Quick ES5 Conversion Guide
-| Modern (ES6+) | ES5 Equivalent |
-|---------------|----------------|
-| \`const x = 5;\` | \`var x = 5;\` |
-| \`let items = [];\` | \`var items = [];\` |
-| \`() => {}\` | \`function() {}\` |
-| \`\` \`Hello \${name}\` \`\` | \`'Hello ' + name\` |
-| \`{a, b} = obj\` | \`var a = obj.a; var b = obj.b;\` |
-| \`for (item of items)\` | \`for (var i = 0; i < items.length; i++)\` |
-| \`func(x = 'default')\` | \`if (typeof x === 'undefined') x = 'default';\` |
-| \`arr.map(x => x.id)\` | \`arr.map(function(x) { return x.id; })\` |
-
-\`\`\`javascript
-// Universal verification pattern
-const verify = await snow_execute_script_with_output({
-  script: \`
-    gs.info('=== VERIFICATION TEST ===');
-    
-    // Test table existence
-    var table = new GlideRecord('table_name');
-    gs.info('Table valid: ' + table.isValid());
-    
-    // Test property existence
-    var prop = gs.getProperty('property.name');
-    gs.info('Property: ' + (prop || 'NOT SET'));
-    
-    // Test actual code
-    try {
-      // User's code here
-      gs.info('SUCCESS');
-    } catch(e) {
-      gs.error('ERROR: ' + e.message);
-    }
-  \`
-});
+### 7. **servicenow-system-properties** ⚙️ Properties
 \`\`\`
-
-### Rule 3: Widget Coherence - Critical Client-Server Communication
-
-ServiceNow 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.
-
-**The Three-Way Contract:**
-
-**Server Script Must:**
-- Initialize all \`data\` properties that HTML will reference
-- Handle every \`input.action\` that client sends
-- Return data in the format client expects
-
-**Client Script Must:**
-- Implement every method that HTML calls via \`ng-click\`
-- Use \`c.server.get({action: 'name'})\` for server communication
-- Update \`c.data\` when server responds
-
-**HTML Template Must:**
-- Only reference \`data\` properties that server provides
-- Only call methods that client implements
-- Use correct Angular directives and bindings
-
-**Critical Communication Points:**
-
-1. **Server → Client Data Flow**
-   - Server sets \`data.property\`
-   - Client receives via \`c.data.property\`
-   - HTML displays with \`{{data.property}}\`
-
-2. **Client → Server Requests**
-   - Client sends \`c.server.get({action: 'name'})\`
-   - Server receives via \`input.action\`
-   - Server processes and returns updated \`data\`
-
-3. **HTML → Client Method Calls**
-   - HTML has \`ng-click="methodName()"\`
-   - Client must have \`$scope.methodName = function()\`
-   - Method typically calls server with \`c.server.get()\`
-
-**Common Failures to Avoid:**
-- Action name mismatches between client and server
-- Method name mismatches between HTML and client  
-- Property name mismatches between server and HTML
-- Missing handlers for client requests
-- Orphaned data properties or methods
-
-**Coherence Validation Checklist:**
-- [ ] Every \`data.property\` in server is used in HTML/client
-- [ ] Every \`ng-click\` in HTML has matching \`$scope.method\` in client
-- [ ] Every \`c.server.get({action})\` in client has matching \`if(input.action)\` in server
-- [ ] Data flows correctly: Server → HTML → Client → Server
-- [ ] No orphaned methods or unused data properties
-
-### Rule 4: Use Local Sync for Widget Debugging - NOT snow_query_table!
-
-**CRITICAL: When debugging widgets, ALWAYS use \`snow_pull_artifact\` first!**
-
-\`\`\`javascript
-// ✅ CORRECT - Use Local Sync for widget debugging
-snow_pull_artifact({ 
-  sys_id: 'widget_sys_id',
-  table: 'sp_widget' 
-});
-// Now use Claude Code native search, multi-file edit, etc.
-
-// ❌ WRONG - Don't use snow_query_table for debugging widgets
-snow_query_table({ 
-  table: 'sp_widget',
-  query: 'sys_id=...',
-  fields: ['template', 'script', 'client_script'] 
-});
-// This hits token limits and can't use native tools!
+snow_property_get - Get property value
+snow_property_set - Set property value
+snow_property_list - List by pattern
+snow_property_bulk_update - Bulk operations
+snow_property_export/import - Export/Import JSON
+snow_property_validate - Validate properties
 \`\`\`
 
-**Why Local Sync for Widget Debugging:**
-- **No token limits** - Handle widgets of ANY size
-- **Native search** - Find issues across all files instantly
-- **Multi-file view** - See relationships between components
-- **Better debugging** - Trace data flow, find missing methods
-- **Coherence checking** - Validate all parts work together
-
-**Widget Debugging Workflow:**
-1. User reports issue → \`snow_pull_artifact\`
-2. Search for error patterns across files
-3. Fix using multi-file edit
-4. Validate coherence → \`snow_validate_artifact_coherence\`
-5. Push fixes back → \`snow_push_artifact\`
-
-**IMPORTANT: Use Local Sync Instead of Query for Large Widgets**
-
-When you see "exceeds maximum allowed tokens" errors, don't try to fetch fields separately with \`snow_query_table\`. Use Local Sync instead:
-
-\`\`\`javascript
-// ❌ WRONG - Don't do this when debugging:
-snow_query_table({ table: 'sp_widget', fields: ['name'] });
-snow_query_table({ table: 'sp_widget', fields: ['script'] });
-snow_query_table({ table: 'sp_widget', fields: ['client_script'] });
-// This is inefficient and can't use native tools!
-
-// ✅ CORRECT - Use Local Sync:
-snow_pull_artifact({ 
-  sys_id: '01d01d6983176a502a7ea130ceaad376' 
-});
-// All files available locally with NO token limits!
+### 8. **servicenow-update-set** 📦 Change Management
 \`\`\`
-
-**Local Sync Benefits:**
-- Handles widgets of ANY size automatically
-- All files available for native tool usage
-- Maintains relationships between components
-- Enables powerful search and refactoring
-
-### Rule 5: Evidence-Based Debugging
-
-Follow this systematic approach for all debugging:
-
-1. **Reproduce** - Run the exact failing code
-2. **Inventory** - List all dependencies
-3. **Verify** - Test each dependency exists
-4. **Fix** - Correct only confirmed issues
-
-**Fix only:**
-- ✅ Confirmed syntax errors
-- ✅ Verified null references
-- ✅ Missing dependencies (after verification)
-- ✅ Real type mismatches
-
-**Never change:**
-- ❌ Unverified resources
-- ❌ Configurations that "seem wrong"
-- ❌ APIs you haven't tested
-- ❌ Working code that could be "better"
-
-## ServiceNow Development Standards
-
-### Table Operations
-- Always verify table existence before operations
-- Use proper field types and references
-- Check for ACLs and permissions
-- Handle large datasets with pagination
-
-### Script Development
-- Use Script Includes for reusable code
-- Implement proper error handling
-- Add meaningful logging with gs.info/warn/error
-- Test in scoped applications when applicable
-- **NEVER use background scripts to update widget fields - use \`snow_update\` instead**
-
-### Widget Development
-
-**CRITICAL: Direct Widget Updates (Not Background Scripts!)**
-- Use \`snow_update({ type: 'widget', identifier: 'widget_name', config: { /* fields to update */ }})\` 
-- Updates widget fields DIRECTLY on the widget record
-- Do NOT use background scripts to update widget fields
-- Do NOT try to import server scripts into client scripts
-
-**Widget Coherence Requirements:**
-- Ensure HTML/Client/Server scripts communicate properly
-- Use Angular providers correctly  
-- Implement proper data binding
-- Test across different themes and portals
-
-**Creating New Widgets:**
-\`\`\`javascript
-snow_deploy({
-  type: 'widget',
-  config: {
-    name: 'my_widget',
-    title: 'My Widget',  // Required for display
-    template: '<div>{{data.message}}</div>',  // Required HTML
-    script: 'data.message = "Hello";', // ServiceNow uses 'script' field
-    client_script: 'function($scope) { var c = this; }'
-  }
-})
+snow_update_set_create - Create update set
+snow_update_set_switch - Switch active set
+snow_update_set_complete - Mark complete
+snow_update_set_export - Export as XML
+snow_update_set_preview - Preview changes
+snow_ensure_active_update_set - Auto-create if needed
 \`\`\`
 
-**Updating Existing Widgets:**
-\`\`\`javascript
-snow_update({
-  type: 'widget',
-  identifier: 'my_widget',  // Name or sys_id
-  config: {
-    template: '<div>Updated HTML</div>',  // Only update what changes
-    script: 'data.updated = true;' // ServiceNow uses 'script' field
-  }
-})
+### 9. **servicenow-development-assistant** 🤖 AI Assistant
+\`\`\`
+snow_find_artifact - Find any artifact by name/type
+snow_edit_artifact - Edit existing artifacts
+snow_analyze_artifact - Analyze dependencies
+snow_comprehensive_search - Deep search all tables
+snow_analyze_requirements - Requirement analysis
+snow_generate_code - Pattern-based generation
+snow_optimize_script - Performance optimization
 \`\`\`
 
-### Flow Development
-- Use proper trigger conditions
-- Implement error handling paths
-- Add appropriate logging actions
-- Test with various data scenarios
-
-## MCP Server Capabilities
-
-Snow-Flow includes 16+ specialized MCP servers with over 200 tools for comprehensive ServiceNow integration:
-
-### 1. ServiceNow Deployment Server
-**Purpose:** Widget and artifact deployment with coherence validation
-
-**Key Tools:**
-- \`snow_deploy\` - Create NEW artifacts (widgets, pages, etc.) - use with \`type: 'widget'\`
-- \`snow_update\` - UPDATE existing artifacts - use for widget field updates
-- \`snow_validate_deployment\` - Validate deployed artifacts
-- \`snow_rollback_deployment\` - Rollback failed deployments
-- \`snow_preview_widget\` - Preview widget before deployment
-- \`snow_widget_test\` - Test widget functionality
-
-**Special Features:**
-- Automatic widget coherence validation
-- Data flow contract verification
-- Method implementation checking
-- CSS class validation
-
-### 2. ServiceNow Operations Server
-**Purpose:** Core ServiceNow operations and queries
-
-**Key Tools:**
-- \`snow_query_table\` - Universal table querying with pagination
-- \`snow_query_incidents\` - Query and analyze incidents
-- \`snow_cmdb_search\` - Search Configuration Management Database
-- \`snow_user_lookup\` - Find and manage users
-- \`snow_operational_metrics\` - Get operational metrics
-- \`snow_knowledge_search\` - Search knowledge base
-
-**Features:**
-- Full CRUD operations on any table
-- Advanced query capabilities
-- Field discovery and validation
-- Relationship navigation
-
-### 3. ServiceNow Automation Server
-**Purpose:** Script execution and automation
-
-**🚨 CRITICAL: ALL SCRIPTS MUST BE ES5 ONLY!**
-ServiceNow runs on Rhino engine - ES6+ syntax will cause SyntaxError and script failure.
-
-**Key Tools:**
-- \`snow_execute_background_script\` - Execute background scripts (**ES5 ONLY!** with optional autoConfirm)
-- \`snow_confirm_script_execution\` - Confirm script execution after user approval
-- \`snow_execute_script_with_output\` - Execute scripts with output capture (**ES5 ONLY!**)
-- \`snow_get_script_output\` - Retrieve script execution history
-- \`snow_execute_script_sync\` - Synchronous script execution (**ES5 ONLY!**)
-- \`snow_get_logs\` - Access system logs
-- \`snow_test_rest_connection\` - Test REST integrations
-- \`snow_trace_execution\` - Trace script execution (**ES5 ONLY!**)
-- \`snow_schedule_job\` - Create scheduled jobs
-- \`snow_create_event\` - Trigger system events
-
-**Remember:** Use \`var\`, \`function(){}\`, string concatenation, traditional for loops only!
-
-**Features:**
-- Full output capture (gs.print/info/warn/error)
-- Execution history tracking
-- System log access
-- REST message testing
-- Performance tracing
-
-### 4. ServiceNow Platform Development Server
-**Purpose:** Platform development artifacts
-
-**Key Tools:**
-- \`snow_create_ui_page\` - Create UI pages
-- \`snow_create_script_include\` - Create reusable scripts
-- \`snow_create_business_rule\` - Create business rules
-- \`snow_create_client_script\` - Create client-side scripts
-- \`snow_create_ui_policy\` - Create UI policies
-- \`snow_create_ui_action\` - Create UI actions
-
-**Features:**
-- Full artifact creation
-- Proper scoping support
-- Condition builder integration
-- Script validation
-
-### 5. ServiceNow Integration Server
-**Purpose:** Integration and data management
-
-**Key Tools:**
-- \`snow_create_rest_message\` - Create REST integrations
-- \`snow_create_transform_map\` - Create data transformation maps
-- \`snow_create_import_set\` - Manage import sets
-- \`snow_test_web_service\` - Test web services
-- \`snow_configure_email\` - Configure email settings
-
-**Features:**
-- REST/SOAP integration
-- Data transformation
-- Import/Export capabilities
-- Email configuration
-
-### 6. ServiceNow System Properties Server
-**Purpose:** System property management
-
-**Key Tools:**
-- \`snow_property_get\` - Retrieve property values
-- \`snow_property_set\` - Set property values
-- \`snow_property_list\` - List properties by pattern
-- \`snow_property_delete\` - Remove properties
-- \`snow_property_bulk_update\` - Bulk operations
-- \`snow_property_export\` - Export to JSON
-- \`snow_property_import\` - Import from JSON
-
-**Features:**
-- Full CRUD on sys_properties
-- Bulk operations
-- Import/Export capabilities
-- Property validation
-
-### 7. ServiceNow Update Set Server
-**Purpose:** Change management and deployment
-
-**Key Tools:**
-- \`snow_update_set_create\` - Create new update sets
-- \`snow_update_set_switch\` - Switch active update set
-- \`snow_update_set_current\` - Get current update set
-- \`snow_update_set_complete\` - Mark as complete
-- \`snow_update_set_export\` - Export as XML
-- \`snow_ensure_active_update_set\` - Ensure update set is active
-
-**Features:**
-- Full update set lifecycle
-- Change tracking
-- XML export/import
-- Conflict detection
-
-### 8. ServiceNow Development Assistant Server
-**Purpose:** Intelligent artifact search, editing and development assistance
-
-**Key Tools:**
-- \`snow_find_artifact\` - Find any ServiceNow artifact by name/type
-- \`snow_edit_artifact\` - Edit existing artifacts intelligently
-- \`snow_get_by_sysid\` - Get artifact by sys_id
-- \`snow_analyze_artifact\` - Analyze artifact structure and dependencies
-- \`snow_comprehensive_search\` - Deep search across all tables
-- \`snow_analyze_requirements\` - Analyze development requirements
-
-**Features:**
-- Pattern-based code generation
-- Best practice enforcement
-- Performance optimization
-- Security review
-
-### 9. ServiceNow Security & Compliance Server
-**Purpose:** Security and compliance management
-
-**Key Tools:**
-- \`snow_create_security_policy\` - Create security policies
-- \`snow_audit_compliance\` - Compliance auditing
-- \`snow_scan_vulnerabilities\` - Vulnerability scanning
-- \`snow_assess_risk\` - Risk assessment
-- \`snow_review_access_control\` - ACL review
-
-**Features:**
-- SOX/GDPR/HIPAA compliance
-- Security policy management
-- Vulnerability assessment
-- Access control validation
-
-### 10. ServiceNow Reporting & Analytics Server
-**Purpose:** Reporting and data visualization
-
-**Key Tools:**
-- \`snow_create_report\` - Create reports
-- \`snow_create_dashboard\` - Create dashboards
-- \`snow_define_kpi\` - Define KPIs
-- \`snow_schedule_report\` - Schedule report delivery
-- \`snow_analyze_data_quality\` - Data quality analysis
-
-**Features:**
-- Advanced reporting
-- Dashboard creation
-- KPI management
-- Scheduled delivery
-
-### 11. ServiceNow Machine Learning Server
-**Purpose:** AI/ML capabilities with TensorFlow.js and native ML integration
-
-**Key Tools:**
-- \`ml_train_incident_classifier\` - Train incident classifier with LSTM neural networks
-- \`ml_predict_change_risk\` - Predict change risks
-- \`ml_detect_anomalies\` - Anomaly detection
-- \`ml_forecast_incidents\` - Incident forecasting with time series
-- \`ml_performance_analytics\` - Native Performance Analytics ML
-- \`ml_hybrid_recommendation\` - Hybrid ML recommendations
-
-**Features:**
-- Predictive analytics
-- Pattern recognition
-- Anomaly detection
-- Process optimization
-
-### 12. ServiceNow Local Development Server
-**Purpose:** Bridge between ServiceNow artifacts and Claude Code's native development tools
-
-**Key Tools:**
-- \`snow_pull_artifact\` - Pull any ServiceNow artifact to local files
-- \`snow_push_artifact\` - Push local changes back with validation
-- \`snow_validate_artifact_coherence\` - Validate artifact relationships
-- \`snow_list_supported_artifacts\` - List all supported artifact types
-- \`snow_sync_status\` - Check sync status of local artifacts
-- \`snow_sync_cleanup\` - Clean up local files after sync
-- \`snow_convert_to_es5\` - Convert modern JavaScript to ES5
-
-**Features:**
-- Supports 12+ artifact types dynamically
-- Smart field chunking for large artifacts
-- ES5 validation for server-side scripts
-- Coherence validation for widgets
-- Full Claude Code native tool integration
-
-**Supported Artifact Types:**
-- Service Portal Widgets (\`sp_widget\`)
-- Flow Designer Flows (\`sys_hub_flow\`)
-- Script Includes (\`sys_script_include\`)
-- Business Rules (\`sys_script\`)
-- UI Pages (\`sys_ui_page\`)
-- Client Scripts (\`sys_script_client\`)
-- UI Policies (\`sys_ui_policy\`)
-- REST Messages (\`sys_rest_message\`)
-- Transform Maps (\`sys_transform_map\`)
-- Scheduled Jobs (\`sysauto_script\`)
-- Fix Scripts (\`sys_script_fix\`)
-
-### 13. Snow-Flow Orchestration Server
-**Purpose:** Multi-agent coordination and task management
-
-**Key Tools:**
-- \`swarm_init\` - Initialize agent swarms
-- \`agent_spawn\` - Create specialized agents
-- \`task_orchestrate\` - Orchestrate complex tasks
-- \`memory_search\` - Search persistent memory
-- \`neural_train\` - Train neural networks with TensorFlow.js
-- \`performance_report\` - Generate performance reports
-
-**Features:**
-- Multi-agent coordination
-- Task orchestration
-- Neural network training (TensorFlow.js)
-- Memory management
-- Performance monitoring
-
-### Additional Servers:
-
-**ServiceNow CMDB/Event/HR/CSM/DevOps Server** - CI management, event correlation, HR processes, customer service, DevOps pipelines
-
-**ServiceNow Knowledge & Catalog Server** - Knowledge articles, service catalog items, catalog variables and policies
-
-**ServiceNow Change/Virtual Agent/PA Server** - Change management, virtual agent NLU, predictive analytics
-
-**ServiceNow Flow/Workspace/Mobile Server** - Flow Designer, workspace configuration, mobile app management
-
-**Features:**
-- Multi-agent coordination
-- Task orchestration
-- Neural network training (TensorFlow.js)
-- Memory management
-- Performance monitoring
-
-## Local Development with Artifact Sync
-
-### Dynamic Artifact Synchronization
-
-The Local Development Server enables editing ServiceNow artifacts using Claude Code's native file tools. This creates a powerful development bridge between ServiceNow and local development environments.
-
-**Workflow:**
-
-1. **Pull Artifact to Local Files**
-   \`\`\`javascript
-   // Auto-detect artifact type
-   snow_pull_artifact({ sys_id: 'any_sys_id' });
-   
-   // Or specify table for faster pull
-   snow_pull_artifact({ 
-     sys_id: 'widget_sys_id',
-     table: 'sp_widget' 
-   });
-   \`\`\`
-
-2. **Edit with Claude Code Native Tools**
-   - Full search capabilities across files
-   - Multi-file editing and refactoring
-   - Syntax highlighting and validation
-   - Git-like diff viewing
-   - Go-to-definition and references
-
-3. **Validate Coherence**
-   \`\`\`javascript
-   // Check artifact relationships
-   snow_validate_artifact_coherence({ 
-     sys_id: 'artifact_sys_id' 
-   });
-   \`\`\`
-
-4. **Push Changes Back**
-   \`\`\`javascript
-   // Push with automatic validation
-   snow_push_artifact({ sys_id: 'artifact_sys_id' });
-   
-   // Force push despite warnings
-   snow_push_artifact({ 
-     sys_id: 'artifact_sys_id',
-     force: true 
-   });
-   \`\`\`
-
-5. **Clean Up**
-   \`\`\`javascript
-   // Remove local files after sync
-   snow_sync_cleanup({ sys_id: 'artifact_sys_id' });
-   \`\`\`
-
-**Artifact Registry:**
-
-Each artifact type is configured with:
-- Field mappings to local files
-- Context-aware wrappers for better editing
-- ES5 validation flags for server scripts
-- Coherence rules for interconnected fields
-- Preprocessors/postprocessors for data transformation
+### 10. **servicenow-security-compliance** 🛡️ Security
+\`\`\`
+snow_create_security_policy - Security policies
+snow_audit_compliance - SOX/GDPR/HIPAA audit
+snow_scan_vulnerabilities - Vulnerability scan
+snow_assess_risk - Risk assessment
+snow_review_access_control - ACL review
+snow_encrypt_field - Field encryption
+snow_audit_trail_analysis - Audit analysis
+\`\`\`
 
-**File Structure Example:**
+### 11. **servicenow-reporting-analytics** 📈 Reporting
 \`\`\`
-/tmp/snow-flow-artifacts/
-├── widgets/
-│   └── my_widget/
-│       ├── my_widget.html          # Template
-│       ├── my_widget.server.js     # Server script (ES5)
-│       ├── my_widget.client.js     # Client script
-│       ├── my_widget.css           # Styles
-│       ├── my_widget.config.json   # Configuration
-│       └── README.md               # Context & instructions
-├── script_includes/
-│   └── MyScriptInclude/
-│       ├── MyScriptInclude.js      # Script
-│       └── MyScriptInclude.docs.md # Documentation
-└── business_rules/
-    └── my_rule/
-        ├── my_rule.js               # Rule script
-        └── my_rule.condition.js     # Condition
+snow_create_report - Create reports
+snow_create_dashboard - Build dashboards
+snow_define_kpi - Define KPIs
+snow_schedule_report - Schedule delivery
+snow_analyze_data_quality - Data quality
+snow_create_pa_widget - Performance analytics
 \`\`\`
 
-**Benefits:**
-- Use your favorite editor features
-- Full search and replace capabilities
-- Version control integration
-- Bulk operations across artifacts
-- Offline development capability
-- Advanced refactoring tools
+### 12. **servicenow-machine-learning** 🧠 AI/ML
+\`\`\`
+ml_train_incident_classifier - Train LSTM classifier
+ml_predict_change_risk - Risk prediction
+ml_detect_anomalies - Anomaly detection
+ml_forecast_incidents - Time series forecast
+ml_cluster_similar - Similarity clustering
+ml_performance_analytics - Native PA ML
+\`\`\`
 
-## Debugging Best Practices
+### 13. **servicenow-change-virtualagent-pa** 🔄 Change & Virtual Agent
+\`\`\`
+snow_create_change_request - Change requests
+snow_assess_change_risk - Risk assessment
+snow_create_nlu_model - NLU models
+snow_train_virtual_agent - Train VA
+snow_configure_conversation - VA conversations
+snow_analyze_pa_trends - Performance trends
+\`\`\`
 
-### Systematic Debugging Protocol
+### 14. **servicenow-cmdb-event-hr-csm-devops** 🏢 Enterprise
+\`\`\`
+snow_manage_ci - Configuration items
+snow_correlate_events - Event correlation
+snow_manage_hr_case - HR cases
+snow_csm_project - Customer projects
+snow_devops_pipeline - CI/CD pipelines
+snow_manage_cmdb_relationships - CI relationships
+\`\`\`
 
-1. **Reproduce the Issue**
-   \`\`\`javascript
-   // Always use ES5 and test exact code
-   const result = await snow_execute_script_with_output({
-     script: \`/* Exact failing code in ES5 */\`
-   });
-   \`\`\`
+### 15. **servicenow-knowledge-catalog** 📚 Knowledge & Catalog
+\`\`\`
+snow_create_knowledge_article - KB articles
+snow_manage_catalog_item - Catalog items
+snow_configure_variables - Variable sets
+snow_create_catalog_policy - Catalog policies
+snow_manage_categories - Categories
+\`\`\`
 
-2. **Verify Dependencies**
-   - Check all referenced tables exist
-   - Verify all properties are set
-   - Confirm all fields are present
-   - Test all integrations work
+### 16. **servicenow-flow-workspace-mobile** 📱 Modern UX
+\`\`\`
+snow_create_flow - Flow Designer flows
+snow_add_flow_action - Flow actions
+snow_create_workspace - Workspace config
+snow_configure_mobile_app - Mobile apps
+snow_configure_offline_sync - Offline mode
+\`\`\`
 
-3. **Test in Context**
-   - Use same scope and variables
-   - Include same imports
-   - Test with same data
+### 17. **servicenow-advanced-features** 🎯 Advanced
+\`\`\`
+snow_performance_optimization - Optimize instance
+snow_batch_operations - Bulk processing
+snow_instance_scan - Health check
+snow_dependency_analysis - Dependencies
+snow_code_search - Search all code
+\`\`\`
 
-4. **Apply Evidence-Based Fixes**
-   - Fix only confirmed issues
-   - Document why changes were made
-   - Test fixes thoroughly
+### 18. **snow-flow** 🎛️ Orchestration
+\`\`\`
+swarm_init - Initialize agent swarms
+agent_spawn - Create specialized agents
+task_orchestrate - Complex task coordination
+memory_search - Search persistent memory
+neural_train - Train neural networks
+\`\`\`
 
-### Common Verification Patterns
+## 🔄 Critical Workflows
 
-**Table Verification:**
+### Widget Debugging (ALWAYS use Local Sync!)
 \`\`\`javascript
-var table = new GlideRecord('table_name');
-gs.info('Table exists: ' + table.isValid());
+// ✅ CORRECT - Local sync for debugging
+await snow_pull_artifact({ sys_id: 'widget_sys_id' });
+// Edit with native tools (search, multi-file, etc.)
+await snow_push_artifact({ sys_id: 'widget_sys_id' });
+
+// ❌ WRONG - Token limit explosion
+await snow_query_table({ table: 'sp_widget', query: 'sys_id=...' });
 \`\`\`
 
-**Property Verification:**
+### Verification Pattern
 \`\`\`javascript
-var prop = gs.getProperty('property.name');
-gs.info('Property value: ' + (prop || 'NOT SET'));
+// Always verify with REAL data, not placeholders
+await snow_execute_script_with_output({
+  script: \`
+    var gr = new GlideRecord('incident');
+    gr.addQuery('active', true);
+    gr.query();
+    gs.info('Found: ' + gr.getRowCount() + ' active incidents');
+    
+    // Test actual property
+    var prop = gs.getProperty('instance_name');
+    gs.info('Instance: ' + prop);
+  \`
+});
 \`\`\`
 
-**Field Verification:**
+### Complete Widget Creation (NO PLACEHOLDERS)
 \`\`\`javascript
-var gr = new GlideRecord('table');
-var element = gr.getElement('field_name');
-gs.info('Field exists: ' + (element ? 'Yes' : 'No'));
+await snow_deploy({
+  type: 'widget',
+  config: {
+    name: 'my_widget',
+    title: 'Production Widget',
+    template: '<div ng-repeat="item in data.items">{{item.name}}</div>',
+    script: \`
+      (function() {
+        data.items = [];
+        var gr = new GlideRecord('incident');
+        gr.addQuery('active', true);
+        gr.setLimit(10);
+        gr.query();
+        while (gr.next()) {
+          data.items.push({
+            name: gr.getDisplayValue('number'),
+            description: gr.getDisplayValue('short_description')
+          });
+        }
+      })();
+    \`,
+    client_script: \`
+      function($scope) {
+        var c = this;
+        c.refresh = function() {
+          c.server.get().then(function(r) {
+            console.log('Refreshed');
+          });
+        };
+      }
+    \`
+  }
+});
 \`\`\`
 
-## Command Reference
+## ⚡ Command Reference
 
 ### Core Commands
-- \`./snow-flow start\` - Start orchestration system
-- \`./snow-flow status\` - System status
-- \`./snow-flow monitor\` - Real-time monitoring
-
-### Agent Management
-- \`./snow-flow agent spawn <type>\` - Create agents
-- \`./snow-flow agent list\` - List active agents
-
-### Task Management
-- \`./snow-flow task create\` - Create tasks
-- \`./snow-flow task list\` - View task queue
-
-### Memory Operations
-- \`./snow-flow memory store <key> <data>\` - Store data
-- \`./snow-flow memory get <key>\` - Retrieve data
-- \`./snow-flow memory list\` - List all keys
-
-### SPARC Modes
-- \`./snow-flow sparc "<task>"\` - Orchestrator mode
-- \`./snow-flow sparc run <mode> "<task>"\` - Specific mode
-- \`./snow-flow sparc tdd "<feature>"\` - Test-driven development
-
-### Swarm Coordination
-- \`./snow-flow swarm "<objective>"\` - Multi-agent coordination
-- Options: \`--strategy\`, \`--mode\`, \`--parallel\`, \`--monitor\`
-
-## Workflow Guidelines
-
-### Development Workflow
-1. **Plan** - Use TodoWrite for task management
-2. **Verify** - Check existing resources
-3. **Develop** - Follow ES5 standards
-4. **Test** - Use background scripts
-5. **Deploy** - Use update sets
-6. **Validate** - Verify deployment
-
-### Testing Workflow
-1. Run unit tests with background scripts
-2. Test integrations with REST tools
-3. Validate UI with widget coherence
-4. Check performance with tracing
-5. Review logs for errors
-
-### Debugging Workflow
-1. Reproduce issue exactly
-2. Gather evidence with scripts
-3. Verify all assumptions
-4. Apply minimal fixes
-5. Test thoroughly
-6. Document changes
-
-## Important Reminders
-
-### Always Remember
-- Every ServiceNow instance is unique
-- Custom implementations exist that you don't know about
-- Preview/beta features may be available
-- Organization-specific configurations are common
-- Test everything before making assumptions
-
-### Never Assume
-- That something doesn't exist without verification
-- That configurations are wrong without testing
-- That APIs aren't available without checking
-- That code won't work without running it
-- That you know better than existing implementations
-
-### Golden Rules
-1. **Verify First** - Test before declaring broken
-2. **ES5 Only** - No modern JavaScript in ServiceNow
-3. **Evidence-Based** - Make decisions on facts, not assumptions
-4. **Minimal Changes** - Fix only what's broken
-5. **Respect Context** - Understand why things exist as they do
-
-## Conclusion
-
-Snow-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.
-
-Remember: 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.`;
+- \`snow-flow init\` - Initialize project with this CLAUDE.md
+- \`snow-flow auth login\` - Authenticate with ServiceNow
+- \`snow-flow status\` - System status
+- \`snow-flow swarm "<task>"\` - Multi-agent coordination
+
+### Development Flow
+1. **Pull artifact**: \`snow_pull_artifact\` for local editing
+2. **Edit locally**: Use Claude's native search/edit tools
+3. **Push changes**: \`snow_push_artifact\` to ServiceNow
+4. **Test**: \`snow_execute_script_with_output\` with REAL code
+5. **Deploy**: \`snow_update_set_complete\` when ready
+
+## 🎯 Golden Rules
+
+1. **NO MOCK DATA** - Everything real, complete, production-ready
+2. **ES5 ONLY** - var, function(){}, no modern JS
+3. **VERIFY FIRST** - Test before assuming
+4. **LOCAL SYNC** - Use snow_pull_artifact for widgets
+5. **COMPLETE CODE** - No TODOs, no placeholders
+6. **TOKEN AWARE** - Use batch operations
+7. **UPDATE SETS** - Track all changes
+
+## 📊 Quick Reference
+
+| Issue | Solution |
+|-------|----------|
+| Widget doesn't work | \`snow_pull_artifact\` → debug locally |
+| Script syntax error | ES5 only! var, function(){} |
+| Can't find table | \`snow_discover_table_fields\` |
+| Property missing | \`snow_property_manager\` |
+| Need to test | \`snow_execute_script_with_output\` |
+| Deployment failed | \`snow_rollback_deployment\` |
+
+Remember: TAKE THE TIME. DO IT RIGHT. NO MOCK DATA. NO EXCEPTIONS.`;
+exports.CLAUDE_MD_TEMPLATE_VERSION = '3.6.2-CONSOLIDATED';
 //# sourceMappingURL=claude-md-template.js.map