Recognize the pre-release Vault build that holds token #45744

[baairon]

Summary

This adds the pre-release Vault build to the table of known builds in src/identity/registry/vault/builds.ts. Ale's Vault 0x6bdC52c8e262c6D139e618260400614c2Bfe51d7 on Base runs this build and holds token #45744.

• Runtime hash: 0xf8f2319752c7b0a6382ef0d233426d0bd605641e65300a4e1b2ece5479a64c13, 1,955 bytes.
• Where it came from: the hash was read with ethagent custody --verify --json, and the bytecode was supplied directly.
• Verified: a reconstructed Solidity source compiles to identical executable code with the repo's settings (solc 0.8.24, 200 optimizer runs, paris). Only the trailing metadata hash differs, since it encodes the source text.

Behavior of this build

The owner, operator, and refusal rules match the current build, with three differences:

• No heldAgent() view. The deposit preflight already falls back to agentOwner on builds without it.
• No registry or token binding. The Vault accepts any ERC-721, one owner per token. There is no UnexpectedToken.
• No operator epoch. Operator approvals survive a withdrawal and apply to whoever next deposits the same token into this Vault.

Effect

Before this change, ethagent treats Ale's Vault as unknown code:

• the manager shows "Vault code not recognized";
• custody --verify exits 4;
• re-depositing is refused.

With this change the build is recognized and those checks work as intended.

Testing

• npm run typecheck is clean.
• npm test passes all 732 tests. The builds test now looks up the pre-release hash.
• After merging, node bin/ethagent.js custody --verify --json should report the pre-release build, list the expected simulation results, and exit 0.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HG2miyE22qTuug1Quxj7iw

---

Generated by Claude Code