docs(integration-toolkit): document inbound direct mode

docs/integrations/integration-toolkit/configuration.md

@@ -122,6 +122,7 @@ curl -X POST 'https://erp-integration.sls.epilot.io/v1/integrations/{integration
 | `configuration` | object | Yes | Type-specific configuration (see sections below) |
 
 :::info
+- `inbound` — Mapped by default; set `"direct": true` in the configuration to skip mapping and send entity-shaped payloads directly. See [Direct Mode](./inbound/direct-mode.md).
 - `file_proxy` — On-demand file serving from external systems or outbound delivery of epilot files. See the [File Proxy](./file-proxy.md) and [Outbound File Delivery](./outbound-file-delivery.md) guides.
 - `managed_call` — Synchronous external API calls with JSONata mapping. See [Managed Call Use Cases](#managed-call-use-cases).
 - `secure_proxy` — Route requests through epilot's secure proxy for static IP or VPN access. See [Secure Proxy Use Cases](#secure-proxy-use-cases).
@@ -138,6 +139,12 @@ curl -X PUT 'https://erp-integration.sls.epilot.io/v1/integrations/{integrationI
   }'
 ```
 
+:::note Configuration propagation
+Use case configurations are cached by the event-processing pipeline: any configuration change —
+mapping edits, enabling/disabling, mode switches — can take up to **5 minutes** to take effect for
+incoming events. Plan cutovers accordingly.
+:::
+
 ### Use Case History
 
 View the change history for a use case:

docs/integrations/integration-toolkit/inbound/examples.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 7
+sidebar_position: 8
 title: Examples
 description: Complete integration examples for common use cases
 ---

docs/integrations/integration-toolkit/inbound/mapping.md

@@ -8,6 +8,10 @@ description: Configure how ERP data transforms into epilot entities
 
 Mapping defines how ERP data transforms into epilot entities. This page covers the configuration structure and available options.
 
+:::tip
+If your middleware already produces entity-shaped payloads, you can skip mapping entirely — see [Direct Mode](./direct-mode.md).
+:::
+
 ## Mapping Configuration
 
 A mapping configuration consists of one or more entity definitions:

docs/integrations/integration-toolkit/inbound/meter-readings.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 6
+sidebar_position: 7
 title: Meter Readings
 description: Synchronize meter reading data from ERP systems
 ---

docs/integrations/integration-toolkit/inbound/pricing.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 5
+sidebar_position: 6
 title: Pricing
 description: Map ERP line items and calculate prices during inbound synchronization
 ---

docs/integrations/integration-toolkit/inbound/relations.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 4
+sidebar_position: 5
 title: Relations
 description: Link entities together during synchronization
 ---

docs/integrations/integration-toolkit/inbound/unique-identifiers.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 3
+sidebar_position: 4
 title: Unique Identifiers
 description: Configure how entities are matched and looked up
 ---