@fluentcommerce/fc-connect-sdk 0.1.54 → 0.1.55

package/docs/02-CORE-GUIDES/mapping/graphql-mutation-mapping/modules/graphql-mutation-mapping-13-best-practices.md

@@ -1,477 +1,477 @@
-# Best Practices
-
-[← Back to GraphQL Mutation Mapping Guide](../graphql-mutation-mapping-readme.md)
-
-**Module 13 of 13** | **Level**: Intermediate | **Time**: 15 minutes
-
----
-
-## Best Practices
-
-This module covers recommended practices for building robust, maintainable GraphQL mutation mappings.
-
-## Complete Example
-
-See `examples/mutations/create-order/sfcc-order-example.ts` (at repository root, outside docs folder) for a full end-to-end example with hooks.
-
-## Best Practices
-
-### 1. Use Schema Validation
-
-Always enable schema validation to catch errors early:
-
-```json
-{
-  "schemaValidation": true // default
-}
-```
-
-**Why:**
-
-- ✅ Catches field name typos before runtime
-- ✅ Validates required fields are included
-- ✅ Ensures types match GraphQL schema
-- ✅ Detects schema changes early
-
-**How to validate:**
-
-```bash
-# Step 1: Introspect schema
-npx fc-connect introspect-schema \
-  --endpoint https://YOUR_ACCOUNT.api.fluentcommerce.com/graphql \
-  --output schema.json
-
-# Step 2: Validate mapping
-npx fc-connect validate-schema \
-  --mapping mappings/order-mapping.json \
-  --schema schema.json
-```
-
-### 2. Separate Configs Per Format
-
-Don't try to make one mapping work for both XML and JSON:
-
-```
-mappings/
-├── sfcc-xml-to-fluent-order.json
-├── shopify-json-to-fluent-order.json
-└── magento-xml-to-fluent-order.json
-```
-
-**Why:**
-
-- ✅ Clearer intent (XML vs JSON paths are different)
-- ✅ Easier to maintain (no conditional logic)
-- ✅ Better performance (no format detection overhead)
-- ✅ Simpler testing (one format per config)
-
-**Example:**
-
-**SFCC (XML):**
-
-```json
-{
-  "sourceFormat": "xml",
-  "ref": { "source": "order@order-no" }
-}
-```
-
-**Shopify (JSON):**
-
-```json
-{
-  "sourceFormat": "json",
-  "ref": { "source": "order.orderNo" }
-}
-```
-
-### 3. Use Type Annotations
-
-Explicitly declare types for better validation:
-
-```json
-{
-  "items": {
-    "_type": "[CreateOrderItemInput]!", // ← Validates against schema
-    "_array": true
-  }
-}
-```
-
-**Why:**
-
-- ✅ Documents expected GraphQL type
-- ✅ Enables compile-time validation
-- ✅ Catches type mismatches early
-- ✅ Better IDE autocomplete
-
-**Type Annotation Examples:**
-
-```json
-{
-  "ref": { "_type": "String!", "source": "orderNo" },
-  "quantity": { "_type": "Int!", "source": "qty" },
-  "price": { "_type": "Float!", "source": "price" },
-  "active": { "_type": "Boolean", "source": "isActive" },
-  "items": { "_type": "[OrderItemInput]!", "_array": true }
-}
-```
-
-### 4. Add Descriptions
-
-Document your mappings:
-
-```json
-{
-  "ref": {
-    "source": "order@order-no",
-    "required": true,
-    "description": "Order reference from SFCC export"
-  }
-}
-```
-
-**Why:**
-
-- ✅ Self-documenting configurations
-- ✅ Easier onboarding for new team members
-- ✅ Clear business context
-- ✅ Audit trail of mapping decisions
-
-**Documentation Best Practices:**
-
-```json
-{
-  "version": "1.0",
-  "mutation": "createOrder",
-  "comment": "SFCC Order → Fluent Commerce Order Management",
-
-  "arguments": {
-    "input": {
-      "ref": {
-        "source": "order@order-no",
-        "required": true,
-        "comment": "✅ Maps to CreateOrderInput.ref (String! required) - SFCC order number"
-      },
-      "customer": {
-        "fields": {
-          "ref": {
-            "source": "customer.customer-no",
-            "required": true,
-            "comment": "✅ Maps to CreateOrderInput.customer.ref (String! required) - SFCC customer ID"
-          }
-        },
-        "comment": "Customer information from SFCC customer object"
-      }
-    }
-  }
-}
-```
-
-### 5. Test Incrementally
-
-Build mappings incrementally and test each section:
-
-```typescript
-// ✅ Test with minimal required fields first
-const simpleMapping = {
-  mutation: 'createOrder',
-  sourceFormat: 'xml',
-  arguments: {
-    input: {
-      ref: { source: 'order@order-no', required: true }, // ✅ CreateOrderInput.ref (String! required)
-      type: { value: 'STANDARD', required: true }, // ✅ CreateOrderInput.type (OrderType! required)
-      retailer: { fields: { id: { value: '1' } } }, // ✅ CreateOrderInput.retailer.id (ID! required)
-    },
-  },
-};
-
-// Then add customer (required field)
-// Then add items (required field)
-// Then add payments, shipping, etc. (optional fields)
-```
-
-**Incremental Testing Workflow:**
-
-1. **Step 1: Test minimal mutation**
-
-   ```json
-   {
-     "ref": "ORD-123",
-     "type": "STANDARD",
-     "retailer": { "id": "1" }
-   }
-   ```
-
-2. **Step 2: Add required fields**
-
-   ```json
-   {
-     "customer": {
-       "ref": "CUST-001",
-       "email": "customer@example.com"
-     }
-   }
-   ```
-
-3. **Step 3: Add items array**
-
-   ```json
-   {
-     "items": [{ "ref": "ITEM-1", "productRef": "PROD-1", "quantity": 5 }]
-   }
-   ```
-
-4. **Step 4: Add optional fields**
-   ```json
-   {
-     "totalPrice": 199.99,
-     "currency": "USD",
-     "attributes": { ... }
-   }
-   ```
-
-**Testing Checklist:**
-
-- [ ] Test with valid data
-- [ ] Test with missing required fields
-- [ ] Test with invalid types
-- [ ] Test with empty arrays
-- [ ] Test with single-item arrays (use `_autoWrap: true`)
-- [ ] Test with embedded data (nodes pattern)
-- [ ] Test error handling
-- [ ] Test with real production data samples
-
-## Troubleshooting
-
-### Path Not Found
-
-**Error:** `Cannot resolve path 'order.missing'`
-
-**Solution:** Check path syntax for your format:
-
-- XML: `order@order-no` (attribute)
-- JSON: `order.orderNo` (property)
-
-**Debugging Steps:**
-
-1. Log source data structure
-2. Verify path syntax matches format
-3. Check for typos in element/property names
-4. Ensure XML attributes use `@` without dot prefix
-
-### Array Type Mismatch
-
-**Error:** `Expected array but got object`
-
-**Solution:** Add `_autoWrap: true` if source can be single object:
-
-```json
-{
-  "_array": true,
-  "_autoWrap": true
-}
-```
-
-**Why this happens:**
-XML parsers often return single objects when there's only one element, but arrays when there are multiple. `_autoWrap` normalizes this behavior.
-
-### Required Field Missing
-
-**Error:** `Required field 'ref' is missing`
-
-**Solution:** Add default value or make field optional:
-
-```json
-{
-  "ref": {
-    "source": "order.ref",
-    "defaultValue": "UNKNOWN"
-  }
-}
-```
-
-**Alternatives:**
-
-- Remove `required: true` if field is truly optional
-- Add validation in `beforeMapping` hook to ensure field exists
-- Use custom resolver to generate value if missing
-
-## Configuration Organization
-
-### Directory Structure
-
-```
-project/
-├── mappings/
-│   ├── sfcc/
-│   │   ├── order-to-fluent.json
-│   │   ├── customer-to-fluent.json
-│   │   └── product-to-fluent.json
-│   ├── shopify/
-│   │   ├── order-to-fluent.json
-│   │   └── customer-to-fluent.json
-│   └── shared/
-│       ├── address-fields.json
-│       └── customer-fields.json
-├── schemas/
-│   └── fluent-commerce-schema.json
-└── src/
-    └── mappers/
-        ├── sfcc-order-mapper.ts
-        └── shopify-order-mapper.ts
-```
-
-### Naming Conventions
-
-**Mapping files:**
-
-- `{source}-{entity}-to-{target}.json`
-- Examples: `sfcc-order-to-fluent.json`, `shopify-customer-to-fluent.json`
-
-**Operation names:**
-
-- `{Action}{Entity}From{Source}`
-- Examples: `CreateOrderFromSFCC`, `UpdateCustomerFromShopify`
-
-**Custom resolvers:**
-
-- `custom.{action}{Entity}`
-- Examples: `custom.parseQuantity`, `custom.lookupCustomer`
-
-## Performance Optimization
-
-### 1. Cache Schema Introspection
-
-```typescript
-const mapper = new GraphQLMutationMapper(config, logger, {
-  fluentClient: client,
-  schemaCacheTTL: 3600000, // 1 hour (default)
-});
-```
-
-### 2. Use Batch Processing
-
-```typescript
-// Process multiple files in batches
-const files = await listS3Files(bucket, prefix);
-const batches = chunk(files, 10);
-
-for (const batch of batches) {
-  await Promise.all(
-    batch.map(async file => {
-      const data = await readFile(file);
-      const payload = await mapper.map(data);
-      await client.graphql(payload);
-    })
-  );
-}
-```
-
-### 3. Optimize Resolvers
-
-```typescript
-// ❌ Inefficient - queries API for each item
-'custom.lookupProduct': async (value, data, config, helpers) => {
-  return await api.getProduct(value);  // N+1 queries!
-}
-
-// ✅ Efficient - batch load all products
-'custom.lookupProducts': async (value, data, config, helpers) => {
-  const items = helpers.get(data, 'order.items');
-  const skus = items.map(i => i.sku);
-  const products = await api.getProductsBatch(skus);  // Single query
-  return helpers.keyBy(products, 'sku');
-}
-```
-
-## Security Best Practices
-
-### 1. Sanitize Logs
-
-```typescript
-function sanitizeForLogging(data: any): any {
-  const sanitized = { ...data };
-
-  // Remove PII
-  delete sanitized.customer?.email;
-  delete sanitized.customer?.phone;
-  delete sanitized.billingAddress;
-
-  // Remove credentials
-  delete sanitized.apiKey;
-  delete sanitized.secretKey;
-
-  return sanitized;
-}
-
-logger.debug('Processing order', sanitizeForLogging(sourceData));
-```
-
-### 2. Validate Input
-
-```typescript
-const hooks = {
-  beforeMapping: async (sourceData, context) => {
-    // Validate required fields exist
-    if (!sourceData.order?.orderNo) {
-      throw new Error('Missing order number');
-    }
-
-    // Sanitize inputs
-    if (sourceData.order.email) {
-      sourceData.order.email = sourceData.order.email.toLowerCase().trim();
-    }
-
-    return sourceData;
-  },
-};
-```
-
-### 3. Environment Variables
-
-```json
-{
-  "retailer": {
-    "fields": {
-      "id": {
-        "value": "${FLUENT_RETAILER_ID}",
-        "comment": "From environment - never hardcode"
-      }
-    }
-  }
-}
-```
-
----
-
-## Navigation
-
-[← Previous: Arguments vs Nodes](./graphql-mutation-mapping-12-arguments-vs-nodes.md) | [Back to Guide](../graphql-mutation-mapping-readme.md)
-
-## Related Documentation
-
-- [API Reference](../../../api-reference/api-reference-readme.md) - Complete API documentation
-- [Complete Error Handling Guide](../../../../03-PATTERN-GUIDES/error-handling/error-handling-readme.md) - Error handling patterns
-- [Universal Mapping Guide](../../mapping-readme.md) - Universal mapping patterns
-- [CLI Tools](../../../../../bin/readme.md) - Schema introspection and validation tools
-
-## Additional Resources
-
-- [Real-world Examples](../../../../01-TEMPLATES/versori/workflows/readme.md) - Production-ready mapping examples
-- [SFCC Connector](../../../../01-TEMPLATES/versori/webhooks/template-webhook-xml-order-ingestion.md) - Complete SFCC integration
-- [Test Data](../../../../03-PATTERN-GUIDES/examples/test-data/03-PATTERN-GUIDES-readme.md) - Sample data for testing
-- [Integration Guide](../../../../03-PATTERN-GUIDES/integration-patterns/integration-patterns-readme.md) - Complete integration patterns
-
----
-
-**Congratulations!** You've completed all 13 modules of the GraphQL Mutation Mapping Guide.
-
-## Next Steps
-
-1. **Read the API Reference**: [API Documentation](../../../api-reference/api-reference-readme.md)
-2. **Try the Examples**: [Versori Workflows](../../../../01-TEMPLATES/versori/workflows/readme.md)
-3. **Build Your First Mapping**: Start with a simple order or customer mapping
-4. **Join the Community**: Share your experiences and get help
-
-**Questions or feedback?** See the main [README](../graphql-mutation-mapping-readme.md) for support information.
+# Best Practices
+
+[← Back to GraphQL Mutation Mapping Guide](../graphql-mutation-mapping-readme.md)
+
+**Module 13 of 13** | **Level**: Intermediate | **Time**: 15 minutes
+
+---
+
+## Best Practices
+
+This module covers recommended practices for building robust, maintainable GraphQL mutation mappings.
+
+## Complete Example
+
+See `examples/mutations/create-order/sfcc-order-example.ts` (at repository root, outside docs folder) for a full end-to-end example with hooks.
+
+## Best Practices
+
+### 1. Use Schema Validation
+
+Always enable schema validation to catch errors early:
+
+```json
+{
+  "schemaValidation": true // default
+}
+```
+
+**Why:**
+
+- ✅ Catches field name typos before runtime
+- ✅ Validates required fields are included
+- ✅ Ensures types match GraphQL schema
+- ✅ Detects schema changes early
+
+**How to validate:**
+
+```bash
+# Step 1: Introspect schema
+npx fc-connect introspect-schema \
+  --endpoint https://YOUR_ACCOUNT.api.fluentcommerce.com/graphql \
+  --output schema.json
+
+# Step 2: Validate mapping
+npx fc-connect validate-schema \
+  --mapping mappings/order-mapping.json \
+  --schema schema.json
+```
+
+### 2. Separate Configs Per Format
+
+Don't try to make one mapping work for both XML and JSON:
+
+```
+mappings/
+├── sfcc-xml-to-fluent-order.json
+├── shopify-json-to-fluent-order.json
+└── magento-xml-to-fluent-order.json
+```
+
+**Why:**
+
+- ✅ Clearer intent (XML vs JSON paths are different)
+- ✅ Easier to maintain (no conditional logic)
+- ✅ Better performance (no format detection overhead)
+- ✅ Simpler testing (one format per config)
+
+**Example:**
+
+**SFCC (XML):**
+
+```json
+{
+  "sourceFormat": "xml",
+  "ref": { "source": "order@order-no" }
+}
+```
+
+**Shopify (JSON):**
+
+```json
+{
+  "sourceFormat": "json",
+  "ref": { "source": "order.orderNo" }
+}
+```
+
+### 3. Use Type Annotations
+
+Explicitly declare types for better validation:
+
+```json
+{
+  "items": {
+    "_type": "[CreateOrderItemInput]!", // ← Validates against schema
+    "_array": true
+  }
+}
+```
+
+**Why:**
+
+- ✅ Documents expected GraphQL type
+- ✅ Enables compile-time validation
+- ✅ Catches type mismatches early
+- ✅ Better IDE autocomplete
+
+**Type Annotation Examples:**
+
+```json
+{
+  "ref": { "_type": "String!", "source": "orderNo" },
+  "quantity": { "_type": "Int!", "source": "qty" },
+  "price": { "_type": "Float!", "source": "price" },
+  "active": { "_type": "Boolean", "source": "isActive" },
+  "items": { "_type": "[OrderItemInput]!", "_array": true }
+}
+```
+
+### 4. Add Descriptions
+
+Document your mappings:
+
+```json
+{
+  "ref": {
+    "source": "order@order-no",
+    "required": true,
+    "description": "Order reference from SFCC export"
+  }
+}
+```
+
+**Why:**
+
+- ✅ Self-documenting configurations
+- ✅ Easier onboarding for new team members
+- ✅ Clear business context
+- ✅ Audit trail of mapping decisions
+
+**Documentation Best Practices:**
+
+```json
+{
+  "version": "1.0",
+  "mutation": "createOrder",
+  "comment": "SFCC Order → Fluent Commerce Order Management",
+
+  "arguments": {
+    "input": {
+      "ref": {
+        "source": "order@order-no",
+        "required": true,
+        "comment": "✅ Maps to CreateOrderInput.ref (String! required) - SFCC order number"
+      },
+      "customer": {
+        "fields": {
+          "ref": {
+            "source": "customer.customer-no",
+            "required": true,
+            "comment": "✅ Maps to CreateOrderInput.customer.ref (String! required) - SFCC customer ID"
+          }
+        },
+        "comment": "Customer information from SFCC customer object"
+      }
+    }
+  }
+}
+```
+
+### 5. Test Incrementally
+
+Build mappings incrementally and test each section:
+
+```typescript
+// ✅ Test with minimal required fields first
+const simpleMapping = {
+  mutation: 'createOrder',
+  sourceFormat: 'xml',
+  arguments: {
+    input: {
+      ref: { source: 'order@order-no', required: true }, // ✅ CreateOrderInput.ref (String! required)
+      type: { value: 'STANDARD', required: true }, // ✅ CreateOrderInput.type (OrderType! required)
+      retailer: { fields: { id: { value: '1' } } }, // ✅ CreateOrderInput.retailer.id (ID! required)
+    },
+  },
+};
+
+// Then add customer (required field)
+// Then add items (required field)
+// Then add payments, shipping, etc. (optional fields)
+```
+
+**Incremental Testing Workflow:**
+
+1. **Step 1: Test minimal mutation**
+
+   ```json
+   {
+     "ref": "ORD-123",
+     "type": "STANDARD",
+     "retailer": { "id": "1" }
+   }
+   ```
+
+2. **Step 2: Add required fields**
+
+   ```json
+   {
+     "customer": {
+       "ref": "CUST-001",
+       "email": "customer@example.com"
+     }
+   }
+   ```
+
+3. **Step 3: Add items array**
+
+   ```json
+   {
+     "items": [{ "ref": "ITEM-1", "productRef": "PROD-1", "quantity": 5 }]
+   }
+   ```
+
+4. **Step 4: Add optional fields**
+   ```json
+   {
+     "totalPrice": 199.99,
+     "currency": "USD",
+     "attributes": { ... }
+   }
+   ```
+
+**Testing Checklist:**
+
+- [ ] Test with valid data
+- [ ] Test with missing required fields
+- [ ] Test with invalid types
+- [ ] Test with empty arrays
+- [ ] Test with single-item arrays (use `_autoWrap: true`)
+- [ ] Test with embedded data (nodes pattern)
+- [ ] Test error handling
+- [ ] Test with real production data samples
+
+## Troubleshooting
+
+### Path Not Found
+
+**Error:** `Cannot resolve path 'order.missing'`
+
+**Solution:** Check path syntax for your format:
+
+- XML: `order@order-no` (attribute)
+- JSON: `order.orderNo` (property)
+
+**Debugging Steps:**
+
+1. Log source data structure
+2. Verify path syntax matches format
+3. Check for typos in element/property names
+4. Ensure XML attributes use `@` without dot prefix
+
+### Array Type Mismatch
+
+**Error:** `Expected array but got object`
+
+**Solution:** Add `_autoWrap: true` if source can be single object:
+
+```json
+{
+  "_array": true,
+  "_autoWrap": true
+}
+```
+
+**Why this happens:**
+XML parsers often return single objects when there's only one element, but arrays when there are multiple. `_autoWrap` normalizes this behavior.
+
+### Required Field Missing
+
+**Error:** `Required field 'ref' is missing`
+
+**Solution:** Add default value or make field optional:
+
+```json
+{
+  "ref": {
+    "source": "order.ref",
+    "defaultValue": "UNKNOWN"
+  }
+}
+```
+
+**Alternatives:**
+
+- Remove `required: true` if field is truly optional
+- Add validation in `beforeMapping` hook to ensure field exists
+- Use custom resolver to generate value if missing
+
+## Configuration Organization
+
+### Directory Structure
+
+```
+project/
+├── mappings/
+│   ├── sfcc/
+│   │   ├── order-to-fluent.json
+│   │   ├── customer-to-fluent.json
+│   │   └── product-to-fluent.json
+│   ├── shopify/
+│   │   ├── order-to-fluent.json
+│   │   └── customer-to-fluent.json
+│   └── shared/
+│       ├── address-fields.json
+│       └── customer-fields.json
+├── schemas/
+│   └── fluent-commerce-schema.json
+└── src/
+    └── mappers/
+        ├── sfcc-order-mapper.ts
+        └── shopify-order-mapper.ts
+```
+
+### Naming Conventions
+
+**Mapping files:**
+
+- `{source}-{entity}-to-{target}.json`
+- Examples: `sfcc-order-to-fluent.json`, `shopify-customer-to-fluent.json`
+
+**Operation names:**
+
+- `{Action}{Entity}From{Source}`
+- Examples: `CreateOrderFromSFCC`, `UpdateCustomerFromShopify`
+
+**Custom resolvers:**
+
+- `custom.{action}{Entity}`
+- Examples: `custom.parseQuantity`, `custom.lookupCustomer`
+
+## Performance Optimization
+
+### 1. Cache Schema Introspection
+
+```typescript
+const mapper = new GraphQLMutationMapper(config, logger, {
+  fluentClient: client,
+  schemaCacheTTL: 3600000, // 1 hour (default)
+});
+```
+
+### 2. Use Batch Processing
+
+```typescript
+// Process multiple files in batches
+const files = await listS3Files(bucket, prefix);
+const batches = chunk(files, 10);
+
+for (const batch of batches) {
+  await Promise.all(
+    batch.map(async file => {
+      const data = await readFile(file);
+      const payload = await mapper.map(data);
+      await client.graphql(payload);
+    })
+  );
+}
+```
+
+### 3. Optimize Resolvers
+
+```typescript
+// ❌ Inefficient - queries API for each item
+'custom.lookupProduct': async (value, data, config, helpers) => {
+  return await api.getProduct(value);  // N+1 queries!
+}
+
+// ✅ Efficient - batch load all products
+'custom.lookupProducts': async (value, data, config, helpers) => {
+  const items = helpers.get(data, 'order.items');
+  const skus = items.map(i => i.sku);
+  const products = await api.getProductsBatch(skus);  // Single query
+  return helpers.keyBy(products, 'sku');
+}
+```
+
+## Security Best Practices
+
+### 1. Sanitize Logs
+
+```typescript
+function sanitizeForLogging(data: any): any {
+  const sanitized = { ...data };
+
+  // Remove PII
+  delete sanitized.customer?.email;
+  delete sanitized.customer?.phone;
+  delete sanitized.billingAddress;
+
+  // Remove credentials
+  delete sanitized.apiKey;
+  delete sanitized.secretKey;
+
+  return sanitized;
+}
+
+logger.debug('Processing order', sanitizeForLogging(sourceData));
+```
+
+### 2. Validate Input
+
+```typescript
+const hooks = {
+  beforeMapping: async (sourceData, context) => {
+    // Validate required fields exist
+    if (!sourceData.order?.orderNo) {
+      throw new Error('Missing order number');
+    }
+
+    // Sanitize inputs
+    if (sourceData.order.email) {
+      sourceData.order.email = sourceData.order.email.toLowerCase().trim();
+    }
+
+    return sourceData;
+  },
+};
+```
+
+### 3. Environment Variables
+
+```json
+{
+  "retailer": {
+    "fields": {
+      "id": {
+        "value": "${FLUENT_RETAILER_ID}",
+        "comment": "From environment - never hardcode"
+      }
+    }
+  }
+}
+```
+
+---
+
+## Navigation
+
+[← Previous: Arguments vs Nodes](./graphql-mutation-mapping-12-arguments-vs-nodes.md) | [Back to Guide](../graphql-mutation-mapping-readme.md)
+
+## Related Documentation
+
+- [API Reference](../../../api-reference/api-reference-readme.md) - Complete API documentation
+- [Complete Error Handling Guide](../../../../03-PATTERN-GUIDES/error-handling/error-handling-readme.md) - Error handling patterns
+- [Universal Mapping Guide](../../mapping-readme.md) - Universal mapping patterns
+- [CLI Tools](../../../../../bin/readme.md) - Schema introspection and validation tools
+
+## Additional Resources
+
+- [Real-world Examples](../../../../01-TEMPLATES/versori/workflows/readme.md) - Production-ready mapping examples
+- [SFCC Connector](../../../../01-TEMPLATES/versori/webhooks/template-webhook-xml-order-ingestion.md) - Complete SFCC integration
+- [Test Data](../../../../03-PATTERN-GUIDES/examples/test-data/03-PATTERN-GUIDES-readme.md) - Sample data for testing
+- [Integration Guide](../../../../03-PATTERN-GUIDES/integration-patterns/integration-patterns-readme.md) - Complete integration patterns
+
+---
+
+**Congratulations!** You've completed all 13 modules of the GraphQL Mutation Mapping Guide.
+
+## Next Steps
+
+1. **Read the API Reference**: [API Documentation](../../../api-reference/api-reference-readme.md)
+2. **Try the Examples**: [Versori Workflows](../../../../01-TEMPLATES/versori/workflows/readme.md)
+3. **Build Your First Mapping**: Start with a simple order or customer mapping
+4. **Join the Community**: Share your experiences and get help
+
+**Questions or feedback?** See the main [README](../graphql-mutation-mapping-readme.md) for support information.