Update Airdrop documentation regarding IDM installation (#228)

* Update Airdrop documentation regarding IDM installation

* Note fixes

Author: radovanjorgic

fern/docs/pages/airdrop/extraction-phases.mdx

@@ -69,10 +69,21 @@ const run = async (events: AirdropEvent[]) => {
       event,
       initialState,
       workerPath: file,
+      initialDomainMapping: {
+        /* your initial domain mapping JSON here */
+      },
       // options: {},
     });
   }
 };
 
 export default run;
 ```
+
+<Note>
+  You must pass the <code>initialDomainMapping</code> parameter to{" "}
+  <code>spawn</code> when running extraction phases. This ensures the correct
+  domain mapping is installed and used by the snap-in.
+</Note>
+
+```

fern/docs/pages/airdrop/initial-domain-mapping.mdx

@@ -4,7 +4,8 @@ This mapping is configured once and then becomes available to all users of your
 allowing them to import data while maintaining semantic meaning from their source systems.
 
 The initial domain mapping is installed with your snap-in.
-The extractor automatically triggers a function to upload these mappings to the Airdrop system.
+On each snap-in version update, function to upload these mappings to the Airdrop
+system is triggered.
 
 ## Chef-cli initial domain mapping setup
 

fern/docs/pages/airdrop/loading-phases.mdx

@@ -36,6 +36,9 @@ const run = async (events: AirdropEvent[]) => {
       event,
       initialState: initialLoaderState,
       workerPath: file,
+      initialDomainMapping: {
+        /* your initial domain mapping JSON here */
+      },
       // options: {},
     });
   }
@@ -44,6 +47,12 @@ const run = async (events: AirdropEvent[]) => {
 export default run;
 ```
 
+<Note>
+  You must pass the <code>initialDomainMapping</code> parameter to{" "}
+  <code>spawn</code> when running loading phases. This ensures the correct
+  domain mapping is installed and used by the snap-in.
+</Note>
+
 ## State handling
 
 Loading phases run as separate runtime instances, similar to extraction phases, with a maximum execution time of 13 minutes. 
@@ -54,4 +63,4 @@ Access to the `state` is available through the SDK's `adapter` object.
 
 ## Creating items in DevRev
 
-To create an item in DevRev and sync it with the external system, start by creating an item with a **subtype** that was established during the initial sync. After selecting the subtype, fill out the necessary details for the item.
+To create an item in DevRev and sync it with the external system, start by creating an item with a **subtype** that was established during the initial sync. After selecting the subtype, fill out the necessary details for the item.

fern/docs/pages/airdrop/manifest.mdx

@@ -19,8 +19,6 @@ functions:
     description: Extraction function for the template snap-in
   - name: loading
     description: Loading function for the template snap-in
-  - name: install_initial_domain_mapping
-    description: Create blueprint and install initial domain mapping
 ```
 
 If loading is not implemented, remove it from the list. This action also removes the option from the DevRev app.

fern/docs/pages/airdrop/snap-in-template.mdx

@@ -4,7 +4,7 @@ Starting with the template is recommended, as it includes all the necessary boil
 
 The template makes use of **[DevRev's SDK library](https://www.npmjs.com/package/@devrev/ts-adaas)**,
 which provides abstraction over the DevRev’s Airdrop control protocol.
-The SDK simplifies the workflow for data extraction and loading, handling events, 
+The SDK simplifies the workflow for data extraction and loading, handling events,
 state management, and artifacts (batches of extracted items).
 
 It provides features such as:
@@ -35,7 +35,6 @@ If you check the template, you can see that a snap-in is a Node.js project with
           - external-sync-units-extraction.ts
           - metadata-extraction.ts
         - index.ts
-      - install_initial_domain_mapping/
       - loading/
         - workers/
           - load-attachments.ts