Chain suite: every --yes path on local anvil chains

[baairon]

Summary

npm run test:chain runs every command that sends a transaction against two local Anvil chains, so the --yes paths are proven on every pull request instead of only by live runs.

How it works (test/run-chain.mjs, test/chain/harness.ts):

• Chains. One Anvil chain stands in for Ethereum Mainnet (ENS), the other for Base (the agent registry). The Base chain starts just past the registry's real start block, so owner lookups scan logs exactly as they do live.
• Stand-in contracts (contracts/test/chain) sit at the real addresses: the ERC-8004 identity registry, the ENS registry, the public resolver, and the universal resolver viem uses. The real Vault is deployed by ethagent itself.
• IPFS is served from the runner process through ETHAGENT_IPFS_API_URL, with raw CIDs so reads still verify the content hashes.
• The wallet. A test wallet signs with Anvil's development keys in place of the browser tab. A request that names its account gets that one; otherwise the test picks the account, the way a person switches accounts.
• No network. Every request to a host other than this machine is refused, and a test asserts it.

The lifecycle (test/chain/lifecycle.test.ts), one agent from start to finish. Each step is checked against chain state, not just exit codes:

1. create, then a profile change;
2. ENS link, then a records change;
3. Advanced custody, with the operator key approved in the Vault;
4. an operator save with no wallet, then a skip when nothing changed;
5. check with nothing to fix;
6. restore --owner while the Vault holds the token;
7. restore --operator on a fresh machine, byte for byte;
8. ENS delete;
9. Simple custody, with operators revoked first;
10. a transfer, after which the token moves and the receiver restores the agent.

It takes about 4 seconds.

Fixes the suite turned up:

• transfer opened a second browser session of its own; it now runs in the command's single wallet tab, like every other command.
• Saves with ETHAGENT_IPFS_API_URL demanded a Pinata JWT they never use, and exited 3. They now go through.
• ETHAGENT_ENS_RPC_URL is new: it puts your own Mainnet RPC first for ENS reads and writes. There was no override before.

CI and docs:

• CI gets a "Chain suite (anvil)" job, with Foundry from foundry-toolchain.
• The README gets a Development section and the two environment variables.

Testing

• npm run typecheck, npm test (776 pass), forge test (17 pass).
• npm run test:chain: 14 of 14 pass locally, on Foundry 1.5.1.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HG2miyE22qTuug1Quxj7iw

---

Generated by Claude Code