feat(deployments): track SwapProxy across 13 chains (incl. Arc 5042 + Robinhood 4663)

[david-uniswap]

Pull Request

Description

Tracks the canonical SwapProxy deployment across every chain it exists on by adding its entry (latest + history) to the deployment registry (deployments/json/<chainId>.json).

SwapProxy lives at the deterministic address 0x02e5be68d46dac0b524905bff209cf47ee6db2a9 on every chain. The address is produced by a plain CREATE from deployer 0xb259f71F8Fa2B0165c4d71061C4bf6c77444aC87 at nonce 0 (not CREATE2), so wherever that deployer's first transaction is the SwapProxy creation, the address is identical.

This PR adds SwapProxy tracking for 13 chains:

	Chain IDs
Previously deployed	1, 10, 130, 1301, 1868, 4326, 8453, 42220, 42161, 7777777, 11155111
Newly deployed in this effort	Arc 5042, Robinhood 4663

Arc and Robinhood were deployed using the canonical nonce-0 deployer so they land at the same 0x02e5…b2a9 address as all other chains.

This is a JSON-only change. Per-chain .md files and index.md are generated artifacts (forge-chronicles in CI) and are intentionally left for that tooling to regenerate.

Fixes # (n/a)

How Has This Been Tested?

No contract code changed — this is deployment-registry metadata only. Verification performed:

• Confirmed each new deployment landed at 0x02e5…b2a9 and that the on-chain runtime bytecode is byte-identical to the canonical instances (diffed against the captured canonical initcode runtime; Arc == Robinhood == canonical).
• Verified the deployer was at nonce 0 on each target chain before deploying, and cast compute-address <deployer> --nonce 0 resolves to the canonical address.
• Validated all modified JSON files parse and that each SwapProxy entry matches the established schema.
• Arc (5042): SwapProxy is fully verified on explorer.arc.io (v0.8.26, viaIR, optimizer runs 4444, cancun).
• Robinhood (4663): source is visible on the explorer via a byte-identical verified twin.

Checklist:

Before deployment

• 100% test and branch coverage — n/a (no contract code changed)
• check slither for severe issues — n/a
• fuzz and invariant tests (when applicable) — n/a
• formal verification (when applicable) — n/a
• deployment or upgrade scripts ready — deployed via canonical nonce-0 CREATE of the captured initcode

After deployment

• transfer ownership after deployments (when applicable) — n/a (SwapProxy is ownerless)
• complete upgrade (when applicable) — n/a
• generate deployment/upgrade log files — registry entries added; .md/index.md regenerated by CI

---

Considerations

• I have followed the contributing guidelines.
• My code follows the style guidelines of this project and I have run forge fmt and prettier to ensure the code style is valid
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas — n/a (JSON registry only)
• I have made corresponding changes to the documentation — registry is the documentation; generated .md left to CI
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works — n/a (no code change)
• New and existing unit tests pass locally with my changes

Additional context

• The address is deterministic via nonce-0 CREATE, so it matches across all chains regardless of initcode; the bytecode diff confirms the deployed contract is the genuine canonical SwapProxy.
• Chain 4326 carries the same executable code at 0x02e5…b2a9 but a metadata-stripped (bytecode_hash=none) build; address and behavior are identical.