Update CCIP Router and Bridge Addresses for ChainID 138

- Changed CCIP Router address from `0x8078A09637e47Fa5Ed34F626046Ea2094a5CDE5e` to `0x42DAb7b888Dd382bD5Adcf9E038dBF1fD03b4817` across multiple documentation files.
- Updated WETH9 Bridge address from `0x89dd12025bfCD38A168455A44B400e913ED33BE2` to `0xcacfd227A040002e49e2e01626363071324f820a`.
- Ensured all references to the new addresses are consistent throughout the documentation.

This update reflects the latest deployment configurations and ensures accurate contract references for ChainID 138.

docs/LINK_TOKEN_SEARCH_RESULTS.md

@@ -14,7 +14,7 @@ Comprehensive search for existing LINK token on ChainID 138 was performed using
 ## Search Methods Used
 
 ### Method 1: CCIP Router Fee Token ✅
-- **Router**: `0x8078A09637e47Fa5Ed34F626046Ea2094a5CDE5e`
+- **Router**: `0x42DAb7b888Dd382bD5Adcf9E038dBF1fD03b4817`
 - **Query**: `getFeeToken()` / `feeToken()`
 - **Result**: ⚠️ Returns address `0x000000000000000000000000514910771af9ca65...`
 - **Finding**: Router references Ethereum Mainnet LINK address (`0x514910771AF9Ca656af840dff83E8264EcF986CA`) but contract does NOT exist at this address on ChainID 138
@@ -30,7 +30,7 @@ Checked the following addresses:
 **Result**: None of the known addresses have deployed contracts.
 
 ### Method 3: Bridge Contract References ✅
-- **WETH9 Bridge**: `0x89dd12025bfCD38A168455A44B400e913ED33BE2`
+- **WETH9 Bridge**: `0xcacfd227A040002e49e2e01626363071324f820a`
 - **WETH10 Bridge**: `0xe0E93247376aa097dB308B92e6Ba36bA015535D0`
 - **Query**: `linkToken()` / `getLinkToken()`
 - **Result**: ⚠️ Bridge contracts don't expose LINK token reference methods
@@ -112,4 +112,3 @@ If bridging is available:
 
 **Last Updated**: 2025-01-12  
 **Status**: ❌ No existing LINK token found - deployment required
-