Record mainnet StarkExchangeMigrationV2 deployment

[lfportal]

Summary

• Records the mainnet deployment of `StarkExchangeMigrationV2` at `0x273b65a7231321D4ee47a4c47408Ef43517455Ec` — bumps `stark_exchange_migration.version` to 2 and updates `implementation_address` in `config/deploy/mainnet/eth_deployed.json`
• Populates the already-deployed `VaultRootSenderAdapter` address in both mainnet and sandbox `eth_config_input.json` files so subsequent runs of `DeployEthContracts.s.sol` skip its redeployment

Test plan

• Confirm the V2 implementation address is verified on Etherscan
• Re-run `DeployEthContracts.s.sol` in simulation against mainnet and confirm the script reports "Using existing" for both `VaultRootSenderAdapter` and `StarkExchangeMigration v2`

🤖 Generated with Claude Code

---

Note

Low Risk
Config-only changes that update recorded on-chain addresses and versions; low risk but incorrect addresses could cause deploy scripts to target the wrong contracts.

Overview
Records the mainnet deployment of StarkExchangeMigrationV2 by bumping stark_exchange_migration.version to 2 and updating its implementation_address in config/deploy/mainnet/eth_deployed.json.

Populates already-deployed vault_root_sender_adapter.address values in both mainnet and sandbox eth_config_input.json so subsequent deploy runs reuse the existing VaultRootSenderAdapter instead of redeploying it.

^{Reviewed by Cursor Bugbot for commit 2829d2f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 2829d2f. Configure here.}