@fluentcommerce/fc-connect-sdk 0.1.53 → 0.1.55

package/docs/04-REFERENCE/platforms/versori/modules/platforms-versori-01-introduction.md

@@ -1,398 +1,398 @@
-# Module 1: Introduction to Versori Platform
-
-[← Back to Versori Platform Guide](../platforms-versori-readme.md)
-
-**Module 1 of 8** | **Level**: Beginner | **Time**: 15 minutes
-
----
-
-## Learning Objectives
-
-By the end of this module, you will:
-- ✅ Understand what Versori Platform is and its core capabilities
-- ✅ Know when to use Versori vs standalone Node.js deployments
-- ✅ Understand the platform architecture and runtime model
-- ✅ Recognize the key components: workflows, connections, KV storage
-- ✅ Understand how the FC Connect SDK integrates with Versori
-
----
-
-## What is Versori Platform?
-
-Versori Platform is a **managed serverless runtime** for deploying integration workflows. It provides:
-
-- **Managed Infrastructure**: No servers to manage, automatic scaling
-- **Built-in Features**: HTTP endpoints, cron scheduling, KV storage, OAuth2
-- **Developer Experience**: TypeScript-first, modern tooling, instant deploys
-- **Monitoring**: Built-in logs, execution tracking, error reporting
-
-### Platform vs Traditional Deployment
-
-| Aspect | Versori Platform | Traditional Node.js |
-|--------|------------------|---------------------|
-| **Infrastructure** | Managed (serverless) | Self-managed (EC2, containers) |
-| **Scaling** | Automatic | Manual configuration |
-| **HTTP Endpoints** | Auto-provisioned | Requires web server (Express, etc.) |
-| **Cron Scheduling** | Built-in | External scheduler (cron, systemd) |
-| **State Storage** | Built-in KV store | External DB (Redis, Postgres) |
-| **Monitoring** | Built-in logs | Custom logging (CloudWatch, Datadog) |
-| **Deployment** | `npm run deploy` | CI/CD pipelines, Docker |
-| **Cost Model** | Pay-per-use | Always-on servers |
-
----
-
-## Core Platform Capabilities
-
-### 1. Workflow Runtime
-
-The Versori runtime (`@versori/run`) provides four workflow types:
-
-```typescript
-import { http, webhook, schedule, fn } from '@versori/run';
-
-// HTTP: External API calls with authentication
-export const queryAPI = http('query', { connection: 'fluent_commerce' }, async (ctx) => {
-  // ctx.fetch is pre-authenticated
-  // Access to ctx.log, ctx.activation
-});
-
-// Webhook: Receive external HTTP requests
-export const receiveOrder = webhook('receive-order', async (ctx) => {
-  // ctx.data contains webhook payload
-  // Access to ctx.request() (for headers), ctx.log
-});
-
-// Scheduled: Time-based recurring tasks (cron)
-export const dailySync = schedule('daily', '0 0 * * *', { connection: 'fluent' }, async (ctx) => {
-  // Runs at midnight daily
-  // Full access like http() if connection provided
-});
-
-// Internal: Data transformation, no external APIs
-export const transform = fn('transform', async (ctx) => {
-  // ctx.openKv() for state
-  // NO ctx.fetch (no external API access)
-});
-```
-
-### 2. OAuth2 Connection Management
-
-Versori manages OAuth2 credentials securely:
-
-```typescript
-// Connections are configured in Versori UI
-// Access in workflows via ctx.activation.connection
-export const apiCall = http('call', { connection: 'fluent_commerce' }, async (ctx) => {
-  const client = await createClient(ctx);  // Auto-authenticated
-
-  // Connection provides:
-  // - OAuth2 token management (automatic refresh)
-  // - Base URL
-  // - Headers
-  // - RetailerId extraction
-});
-```
-
-**Benefits**:
-- No credential management in code
-- Automatic token refresh
-- Secure secret storage
-- Per-environment configurations
-
-### 3. Distributed KV Storage
-
-Built-in key-value store for state management:
-
-```typescript
-// Three storage scopes
-const projectKV = ctx.openKv(':project:');      // Shared across workflows
-const workflowKV = ctx.openKv(':workflow:xyz'); // Workflow-specific
-const customKV = ctx.openKv('custom:ns');       // Custom namespace
-
-// Operations
-await projectKV.set('key', { value: 'data' }, { ttl: 3600000 });  // 1 hour TTL
-const data = await projectKV.get('key');
-await projectKV.delete('key');
-const keys = await projectKV.list({ prefix: 'state:' });
-```
-
-**Use Cases**:
-- Track processed files (prevent duplicates)
-- Distributed locking (concurrent workflows)
-- Caching expensive API calls
-- Incremental sync state
-- Rate limiting
-
-### 4. Auto-Scaling & Performance
-
-The platform automatically scales based on workload:
-
-- **Cold Starts**: ~100-300ms for JavaScript/TypeScript
-- **Warm Execution**: ~10-50ms overhead
-- **Concurrent Workflows**: Automatic horizontal scaling
-- **Resource Limits**: Configurable memory (128MB-1GB)
-- **Execution Timeout**: Configurable (default 30s, max 300s)
-
----
-
-## Platform Architecture
-
-### High-Level Overview
-
-```
-┌─────────────────────────────────────────────────────────────┐
-│                    Versori Platform                          │
-├─────────────────────────────────────────────────────────────┤
-│                                                               │
-│  ┌───────────────┐  ┌───────────────┐  ┌──────────────┐    │
-│  │ HTTP Endpoint │  │   Cron Jobs   │  │  Webhooks    │    │
-│  │  /my-workflow │  │ 0 0 * * *     │  │  /receive    │    │
-│  └───────┬───────┘  └───────┬───────┘  └──────┬───────┘    │
-│          │                  │                   │            │
-│          └──────────────────┼───────────────────┘            │
-│                             ▼                                │
-│                   ┌─────────────────┐                        │
-│                   │  Workflow       │                        │
-│                   │  Runtime        │                        │
-│                   │  (@versori/run) │                        │
-│                   └────────┬────────┘                        │
-│                            │                                 │
-│          ┌─────────────────┼─────────────────┐              │
-│          ▼                 ▼                 ▼              │
-│   ┌──────────┐      ┌──────────┐     ┌──────────┐          │
-│   │Connection│      │ KV Store │     │  Logs    │          │
-│   │  OAuth2  │      │  State   │     │ Metrics  │          │
-│   └──────────┘      └──────────┘     └──────────┘          │
-│                                                               │
-└─────────────────────────────────────────────────────────────┘
-                             │
-                             ▼
-                ┌────────────────────────┐
-                │  Fluent Commerce API   │
-                │  GraphQL / Batch       │
-                └────────────────────────┘
-```
-
-### Request Flow Example: HTTP Workflow
-
-```
-1. External Request
-   ↓
-2. Versori HTTP Router → Matches workflow endpoint
-   ↓
-3. Workflow Runtime Initialization
-   - Load connection credentials
-   - Initialize context (ctx)
-   - Provide authenticated fetch
-   ↓
-4. Workflow Execution
-   - Your handler function runs
-   - Access to ctx.fetch, ctx.log, ctx.openKv()
-   ↓
-5. FC Connect SDK Integration
-   - createClient(ctx) → FluentVersoriClient
-   - Auto-configured with connection
-   - OAuth2 token managed by platform
-   ↓
-6. Fluent Commerce API Call
-   - GraphQL query/mutation
-   - Batch API operations
-   ↓
-7. Response
-   - JSON (default)
-   - Custom Response object (XML, HTML, CSV, etc.)
-   ↓
-8. Logging & Metrics
-   - Execution time tracked
-   - Logs stored
-   - Errors captured
-```
-
----
-
-## FC Connect SDK Integration
-
-The FC Connect SDK is designed to work seamlessly with Versori:
-
-### Universal Client Factory
-
-```typescript
-import { createClient } from '@fluentcommerce/fc-connect-sdk';
-
-// Auto-detects Versori context
-export const workflow = http('name', { connection: 'fluent_commerce' }, async (ctx) => {
-  // Creates FluentVersoriClient automatically
-  const client = await createClient(ctx);
-
-  // All SDK features available:
-  // - GraphQL queries/mutations
-  // - Batch API operations
-  // - Event sending
-  // - Auto-pagination
-  // - Field mapping
-});
-```
-
-### Context Detection
-
-The SDK automatically detects the runtime environment:
-
-| Runtime | Client Type | Auth Method |
-|---------|-------------|-------------|
-| Versori HTTP (`http()`) | `FluentVersoriClient` | Connection OAuth2 |
-| Versori Webhook (`webhook()`) | `FluentClient` | Connection OAuth2 |
-| Versori Scheduled (`schedule()`) | `FluentVersoriClient` | Connection OAuth2 |
-| Node.js Standalone | `FluentClient` | Manual OAuth2 config |
-| Deno | `FluentClient` | Manual OAuth2 config |
-
-### Versori-Specific Adapters
-
-The SDK provides Versori-optimized utilities:
-
-```typescript
-import {
-  VersoriKVAdapter,       // KV store adapter
-  VersoriFileTracker,     // File processing tracker
-} from '@fluentcommerce/fc-connect-sdk';
-
-// File tracking with KV storage
-const kv = ctx.openKv(':project:');
-const tracker = new VersoriFileTracker(kv, 'inventory-sync');
-
-if (await tracker.wasFileProcessed('file.csv')) {
-  return { skipped: true, reason: 'Already processed' };
-}
-
-// Process file...
-
-await tracker.markFileProcessed('file.csv', {
-  records: 1000,
-  duration: 5000
-});
-```
-
----
-
-## When to Use Versori Platform
-
-### ✅ Ideal Use Cases
-
-1. **Production Integrations**
-   - Daily/hourly inventory syncs
-   - Real-time order processing
-   - Event-driven workflows
-   - Scheduled data extraction
-
-2. **Webhook Receivers**
-   - SFCC order webhooks
-   - Fluent Rubix event webhooks
-   - Third-party system notifications
-   - Real-time data ingestion
-
-3. **Multi-Environment Deployments**
-   - Dev/staging/production isolation
-   - Per-environment credentials
-   - Easy configuration management
-
-4. **Rapid Prototyping**
-   - Quick setup (no infrastructure)
-   - Instant deployment
-   - Built-in monitoring
-
-### ⚠️ Consider Alternatives When
-
-1. **Long-Running Processes** (> 5 minutes)
-   - Heavy data processing
-   - Large file transformations
-   - Consider chunking or async patterns
-
-2. **Stateful Applications**
-   - Real-time streaming
-   - WebSocket connections
-   - Use external services
-
-3. **Complex Networking**
-   - VPC peering requirements
-   - On-premise database access
-   - Consider hybrid deployment
-
----
-
-## Platform Billing Model
-
-Understanding Versori costs helps optimize workflows:
-
-| Component | Billing | Optimization Tips |
-|-----------|---------|-------------------|
-| **Workflow Executions** | Per invocation | Batch operations, reduce redundant calls |
-| **KV Store** | Per read/write | Cache data, use batch operations |
-| **Data Transfer** | Per GB | Compress payloads, paginate results |
-| **Compute Time** | Per second | Optimize code, use async operations |
-
-**Cost Optimization Example**:
-```typescript
-// ❌ Expensive: Multiple KV writes
-for (const item of items) {
-  await kv.set(`item:${item.id}`, item);  // N KV writes
-}
-
-// ✅ Optimized: Single KV write
-await kv.set('items:batch', items);  // 1 KV write
-```
-
----
-
-## Platform Versions
-
-### @versori/run Version Compatibility
-
-| Version | Status | Key Features |
-|---------|--------|--------------|
-| **v0.4.4** | **Current** | Latest stable, dependency updates |
-| v0.4.3 | Stable | Previous stable |
-| v0.4.2 | Stable | Previous stable |
-| v0.4.1 | Stable | Previous stable |
-| v0.4.0 | Stable | Initial v0.4 release |
-
-**Recommendation**: Always use latest v0.4.x for bug fixes and improvements.
-
-### SDK Compatibility
-
-The FC Connect SDK supports all @versori/run v0.4.x versions.
-
-**Installation**:
-```bash
-npm install @fluentcommerce/fc-connect-sdk @versori/run
-```
-
----
-
-## Key Takeaways
-
-- 🎯 **Versori Platform** provides managed serverless runtime for integrations
-- 🎯 **Four workflow types**: http(), webhook(), schedule(), fn() - each for specific use cases
-- 🎯 **Built-in features**: OAuth2 connections, KV storage, cron scheduling, auto-scaling
-- 🎯 **FC Connect SDK** integrates seamlessly via `createClient()` factory
-- 🎯 **Ideal for** production integrations, webhook receivers, scheduled tasks
-- 🎯 **Platform architecture** separates concerns: runtime, storage, connections, monitoring
-
----
-
-## Next Steps
-
-Now that you understand the Versori Platform fundamentals, let's build your first connector!
-
-Continue to [Module 2: Quick Start →](./platforms-versori-02-quick-start.md) to deploy your first Versori workflow.
-
----
-
-## Related Documentation
-
-- [Module 2: Quick Start](./platforms-versori-02-quick-start.md) - Deploy your first connector
-- [Module 3: Authentication](./platforms-versori-03-authentication.md) - OAuth2 and connections
-- [Module 4: Workflows](./platforms-versori-04-workflows.md) - Deep dive into workflow types
-- [Getting Started Guide](../../../../00-START-HERE/getting-started.md) - SDK setup basics
-
----
-
-[← Back to Guide](../platforms-versori-readme.md) | [Next: Module 2: Quick Start →](./platforms-versori-02-quick-start.md)
+# Module 1: Introduction to Versori Platform
+
+[← Back to Versori Platform Guide](../platforms-versori-readme.md)
+
+**Module 1 of 8** | **Level**: Beginner | **Time**: 15 minutes
+
+---
+
+## Learning Objectives
+
+By the end of this module, you will:
+- ✅ Understand what Versori Platform is and its core capabilities
+- ✅ Know when to use Versori vs standalone Node.js deployments
+- ✅ Understand the platform architecture and runtime model
+- ✅ Recognize the key components: workflows, connections, KV storage
+- ✅ Understand how the FC Connect SDK integrates with Versori
+
+---
+
+## What is Versori Platform?
+
+Versori Platform is a **managed serverless runtime** for deploying integration workflows. It provides:
+
+- **Managed Infrastructure**: No servers to manage, automatic scaling
+- **Built-in Features**: HTTP endpoints, cron scheduling, KV storage, OAuth2
+- **Developer Experience**: TypeScript-first, modern tooling, instant deploys
+- **Monitoring**: Built-in logs, execution tracking, error reporting
+
+### Platform vs Traditional Deployment
+
+| Aspect | Versori Platform | Traditional Node.js |
+|--------|------------------|---------------------|
+| **Infrastructure** | Managed (serverless) | Self-managed (EC2, containers) |
+| **Scaling** | Automatic | Manual configuration |
+| **HTTP Endpoints** | Auto-provisioned | Requires web server (Express, etc.) |
+| **Cron Scheduling** | Built-in | External scheduler (cron, systemd) |
+| **State Storage** | Built-in KV store | External DB (Redis, Postgres) |
+| **Monitoring** | Built-in logs | Custom logging (CloudWatch, Datadog) |
+| **Deployment** | `npm run deploy` | CI/CD pipelines, Docker |
+| **Cost Model** | Pay-per-use | Always-on servers |
+
+---
+
+## Core Platform Capabilities
+
+### 1. Workflow Runtime
+
+The Versori runtime (`@versori/run`) provides four workflow types:
+
+```typescript
+import { http, webhook, schedule, fn } from '@versori/run';
+
+// HTTP: External API calls with authentication
+export const queryAPI = http('query', { connection: 'fluent_commerce' }, async (ctx) => {
+  // ctx.fetch is pre-authenticated
+  // Access to ctx.log, ctx.activation
+});
+
+// Webhook: Receive external HTTP requests
+export const receiveOrder = webhook('receive-order', async (ctx) => {
+  // ctx.data contains webhook payload
+  // Access to ctx.request() (for headers), ctx.log
+});
+
+// Scheduled: Time-based recurring tasks (cron)
+export const dailySync = schedule('daily', '0 0 * * *', { connection: 'fluent' }, async (ctx) => {
+  // Runs at midnight daily
+  // Full access like http() if connection provided
+});
+
+// Internal: Data transformation, no external APIs
+export const transform = fn('transform', async (ctx) => {
+  // ctx.openKv() for state
+  // NO ctx.fetch (no external API access)
+});
+```
+
+### 2. OAuth2 Connection Management
+
+Versori manages OAuth2 credentials securely:
+
+```typescript
+// Connections are configured in Versori UI
+// Access in workflows via ctx.activation.connection
+export const apiCall = http('call', { connection: 'fluent_commerce' }, async (ctx) => {
+  const client = await createClient(ctx);  // Auto-authenticated
+
+  // Connection provides:
+  // - OAuth2 token management (automatic refresh)
+  // - Base URL
+  // - Headers
+  // - RetailerId extraction
+});
+```
+
+**Benefits**:
+- No credential management in code
+- Automatic token refresh
+- Secure secret storage
+- Per-environment configurations
+
+### 3. Distributed KV Storage
+
+Built-in key-value store for state management:
+
+```typescript
+// Three storage scopes
+const projectKV = ctx.openKv(':project:');      // Shared across workflows
+const workflowKV = ctx.openKv(':workflow:xyz'); // Workflow-specific
+const customKV = ctx.openKv('custom:ns');       // Custom namespace
+
+// Operations
+await projectKV.set('key', { value: 'data' }, { ttl: 3600000 });  // 1 hour TTL
+const data = await projectKV.get('key');
+await projectKV.delete('key');
+const keys = await projectKV.list({ prefix: 'state:' });
+```
+
+**Use Cases**:
+- Track processed files (prevent duplicates)
+- Distributed locking (concurrent workflows)
+- Caching expensive API calls
+- Incremental sync state
+- Rate limiting
+
+### 4. Auto-Scaling & Performance
+
+The platform automatically scales based on workload:
+
+- **Cold Starts**: ~100-300ms for JavaScript/TypeScript
+- **Warm Execution**: ~10-50ms overhead
+- **Concurrent Workflows**: Automatic horizontal scaling
+- **Resource Limits**: Configurable memory (128MB-1GB)
+- **Execution Timeout**: Configurable (default 30s, max 300s)
+
+---
+
+## Platform Architecture
+
+### High-Level Overview
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                    Versori Platform                          │
+├─────────────────────────────────────────────────────────────┤
+│                                                               │
+│  ┌───────────────┐  ┌───────────────┐  ┌──────────────┐    │
+│  │ HTTP Endpoint │  │   Cron Jobs   │  │  Webhooks    │    │
+│  │  /my-workflow │  │ 0 0 * * *     │  │  /receive    │    │
+│  └───────┬───────┘  └───────┬───────┘  └──────┬───────┘    │
+│          │                  │                   │            │
+│          └──────────────────┼───────────────────┘            │
+│                             ▼                                │
+│                   ┌─────────────────┐                        │
+│                   │  Workflow       │                        │
+│                   │  Runtime        │                        │
+│                   │  (@versori/run) │                        │
+│                   └────────┬────────┘                        │
+│                            │                                 │
+│          ┌─────────────────┼─────────────────┐              │
+│          ▼                 ▼                 ▼              │
+│   ┌──────────┐      ┌──────────┐     ┌──────────┐          │
+│   │Connection│      │ KV Store │     │  Logs    │          │
+│   │  OAuth2  │      │  State   │     │ Metrics  │          │
+│   └──────────┘      └──────────┘     └──────────┘          │
+│                                                               │
+└─────────────────────────────────────────────────────────────┘
+                             │
+                             ▼
+                ┌────────────────────────┐
+                │  Fluent Commerce API   │
+                │  GraphQL / Batch       │
+                └────────────────────────┘
+```
+
+### Request Flow Example: HTTP Workflow
+
+```
+1. External Request
+   ↓
+2. Versori HTTP Router → Matches workflow endpoint
+   ↓
+3. Workflow Runtime Initialization
+   - Load connection credentials
+   - Initialize context (ctx)
+   - Provide authenticated fetch
+   ↓
+4. Workflow Execution
+   - Your handler function runs
+   - Access to ctx.fetch, ctx.log, ctx.openKv()
+   ↓
+5. FC Connect SDK Integration
+   - createClient(ctx) → FluentVersoriClient
+   - Auto-configured with connection
+   - OAuth2 token managed by platform
+   ↓
+6. Fluent Commerce API Call
+   - GraphQL query/mutation
+   - Batch API operations
+   ↓
+7. Response
+   - JSON (default)
+   - Custom Response object (XML, HTML, CSV, etc.)
+   ↓
+8. Logging & Metrics
+   - Execution time tracked
+   - Logs stored
+   - Errors captured
+```
+
+---
+
+## FC Connect SDK Integration
+
+The FC Connect SDK is designed to work seamlessly with Versori:
+
+### Universal Client Factory
+
+```typescript
+import { createClient } from '@fluentcommerce/fc-connect-sdk';
+
+// Auto-detects Versori context
+export const workflow = http('name', { connection: 'fluent_commerce' }, async (ctx) => {
+  // Creates FluentVersoriClient automatically
+  const client = await createClient(ctx);
+
+  // All SDK features available:
+  // - GraphQL queries/mutations
+  // - Batch API operations
+  // - Event sending
+  // - Auto-pagination
+  // - Field mapping
+});
+```
+
+### Context Detection
+
+The SDK automatically detects the runtime environment:
+
+| Runtime | Client Type | Auth Method |
+|---------|-------------|-------------|
+| Versori HTTP (`http()`) | `FluentVersoriClient` | Connection OAuth2 |
+| Versori Webhook (`webhook()`) | `FluentClient` | Connection OAuth2 |
+| Versori Scheduled (`schedule()`) | `FluentVersoriClient` | Connection OAuth2 |
+| Node.js Standalone | `FluentClient` | Manual OAuth2 config |
+| Deno | `FluentClient` | Manual OAuth2 config |
+
+### Versori-Specific Adapters
+
+The SDK provides Versori-optimized utilities:
+
+```typescript
+import {
+  VersoriKVAdapter,       // KV store adapter
+  VersoriFileTracker,     // File processing tracker
+} from '@fluentcommerce/fc-connect-sdk';
+
+// File tracking with KV storage
+const kv = ctx.openKv(':project:');
+const tracker = new VersoriFileTracker(kv, 'inventory-sync');
+
+if (await tracker.wasFileProcessed('file.csv')) {
+  return { skipped: true, reason: 'Already processed' };
+}
+
+// Process file...
+
+await tracker.markFileProcessed('file.csv', {
+  records: 1000,
+  duration: 5000
+});
+```
+
+---
+
+## When to Use Versori Platform
+
+### ✅ Ideal Use Cases
+
+1. **Production Integrations**
+   - Daily/hourly inventory syncs
+   - Real-time order processing
+   - Event-driven workflows
+   - Scheduled data extraction
+
+2. **Webhook Receivers**
+   - SFCC order webhooks
+   - Fluent Rubix event webhooks
+   - Third-party system notifications
+   - Real-time data ingestion
+
+3. **Multi-Environment Deployments**
+   - Dev/staging/production isolation
+   - Per-environment credentials
+   - Easy configuration management
+
+4. **Rapid Prototyping**
+   - Quick setup (no infrastructure)
+   - Instant deployment
+   - Built-in monitoring
+
+### ⚠️ Consider Alternatives When
+
+1. **Long-Running Processes** (> 5 minutes)
+   - Heavy data processing
+   - Large file transformations
+   - Consider chunking or async patterns
+
+2. **Stateful Applications**
+   - Real-time streaming
+   - WebSocket connections
+   - Use external services
+
+3. **Complex Networking**
+   - VPC peering requirements
+   - On-premise database access
+   - Consider hybrid deployment
+
+---
+
+## Platform Billing Model
+
+Understanding Versori costs helps optimize workflows:
+
+| Component | Billing | Optimization Tips |
+|-----------|---------|-------------------|
+| **Workflow Executions** | Per invocation | Batch operations, reduce redundant calls |
+| **KV Store** | Per read/write | Cache data, use batch operations |
+| **Data Transfer** | Per GB | Compress payloads, paginate results |
+| **Compute Time** | Per second | Optimize code, use async operations |
+
+**Cost Optimization Example**:
+```typescript
+// ❌ Expensive: Multiple KV writes
+for (const item of items) {
+  await kv.set(`item:${item.id}`, item);  // N KV writes
+}
+
+// ✅ Optimized: Single KV write
+await kv.set('items:batch', items);  // 1 KV write
+```
+
+---
+
+## Platform Versions
+
+### @versori/run Version Compatibility
+
+| Version | Status | Key Features |
+|---------|--------|--------------|
+| **v0.4.4** | **Current** | Latest stable, dependency updates |
+| v0.4.3 | Stable | Previous stable |
+| v0.4.2 | Stable | Previous stable |
+| v0.4.1 | Stable | Previous stable |
+| v0.4.0 | Stable | Initial v0.4 release |
+
+**Recommendation**: Always use latest v0.4.x for bug fixes and improvements.
+
+### SDK Compatibility
+
+The FC Connect SDK supports all @versori/run v0.4.x versions.
+
+**Installation**:
+```bash
+npm install @fluentcommerce/fc-connect-sdk @versori/run
+```
+
+---
+
+## Key Takeaways
+
+- 🎯 **Versori Platform** provides managed serverless runtime for integrations
+- 🎯 **Four workflow types**: http(), webhook(), schedule(), fn() - each for specific use cases
+- 🎯 **Built-in features**: OAuth2 connections, KV storage, cron scheduling, auto-scaling
+- 🎯 **FC Connect SDK** integrates seamlessly via `createClient()` factory
+- 🎯 **Ideal for** production integrations, webhook receivers, scheduled tasks
+- 🎯 **Platform architecture** separates concerns: runtime, storage, connections, monitoring
+
+---
+
+## Next Steps
+
+Now that you understand the Versori Platform fundamentals, let's build your first connector!
+
+Continue to [Module 2: Quick Start →](./platforms-versori-02-quick-start.md) to deploy your first Versori workflow.
+
+---
+
+## Related Documentation
+
+- [Module 2: Quick Start](./platforms-versori-02-quick-start.md) - Deploy your first connector
+- [Module 3: Authentication](./platforms-versori-03-authentication.md) - OAuth2 and connections
+- [Module 4: Workflows](./platforms-versori-04-workflows.md) - Deep dive into workflow types
+- [Getting Started Guide](../../../../00-START-HERE/getting-started.md) - SDK setup basics
+
+---
+
+[← Back to Guide](../platforms-versori-readme.md) | [Next: Module 2: Quick Start →](./platforms-versori-02-quick-start.md)