update ccip directory

[aelmanaa]

This pull request updates several configuration files to add support for the savUSD token across multiple mainnet chains, introduces new or updated rate limiter settings, and makes several additional updates and corrections to testnet and mainnet token and lane configurations. The most significant changes are grouped below.

Mainnet Token and Lane Configuration Updates:

• Added savUSD as a supported token to multiple chains in lanes.json with rate limiter configuration set to disabled and zero capacity/rate. This ensures the token is recognized but not actively rate-limited or enabled for transfers yet. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16]
• Added savUSD token details for berachain-mainnet and ethereum-mainnet-arbitrum-1 in tokens.json, including pool and token addresses, decimals, and other metadata. [1] [2]

Mainnet Token Corrections:

• Corrected the name, pool address, and token address for APRS (Apeiros) on ronin-mainnet in tokens.json.
• Updated rate limiter capacities and rates for APRS in lanes.json to reflect new values. [1] [2]

Testnet Chain and Lane Configuration Updates:

• Updated addresses, versions, and fee token lists for monad-testnet and other testnets in chains.json, reflecting new deployments and support for additional fee tokens. [1] [2] [3]
• Updated monad-testnet on/off ramp addresses and versions in lanes.json, and added support for CCIP-BnM with a disabled rate limiter.
• Added lane configuration for sei-testnet-atlantic in lanes.json.
• Removed duplicate or outdated monad-testnet lane entries from lanes.json. [1] [2] [3]

These updates collectively improve token support, correct configuration errors, and ensure the latest contract addresses and settings are reflected in the configuration files.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
documentation	Ready	Preview	Jan 23, 2026 5:21pm

[github-actions]

👋 aelmanaa, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!