feat: add ZAIBATSU token metadata

[willdias-consensys]

What changed

• Added CAIP-19 metadata for ZAIBATSU (eip155:4663/erc20:0x5DBaCA8327B0bAA57eB6C872a333Bf8D6F642BA3).
• Added the canonical 800×800 ZAIBATSU icon associated with the project's Dexscreener profile and official website.

Why

ZAIBATSU can currently be resolved dynamically by Token API, but it is absent from MetaMask's curated chain-wide token registry. Adding it to contract-metadata allows the published MetaMask token list to recognize it as a curated asset on Robinhood Chain.

Impact

After merge and downstream token-list ingestion, Token API should attach the metamask aggregator to ZAIBATSU and Accounts API can include it when supported-token filtering is enabled.

Validation

• node cli-update-asset.js verify --caip eip155:4663/erc20:0x5DBaCA8327B0bAA57eB6C872a333Bf8D6F642BA3
• node buildindex.js
• Full repository test suite (yarn test equivalent commands)

---

Note

Low Risk
Metadata-only registry addition with no application or security logic changes.

Overview
Adds curated ZAIBATSU (Zaibatsu Wagies) ERC-20 metadata for Robinhood Chain under CAIP-19 eip155:4663/erc20:0x5DBaCA8327B0bAA57eB6C872a333Bf8D6F642BA3, including name, symbol, 18 decimals, and a logo path consistent with other eip155:4663 entries.

This registers the token in contract-metadata so downstream MetaMask token-list ingestion can treat it as a curated asset on that chain.

^{Reviewed by Cursor Bugbot for commit 64ab925. 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, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 71b3794. Configure here.}