[littlehand26]

Summary

• infer top-level CREATE versus CALL from successful and failed root traces in the existing BlockFile
• preserve CALL-to-zero and use the zero-address fallback only when root trace metadata is absent
• keep the inferred kind internal to Leafage without changing the BlockFile schema
• tolerate malformed unrelated internal traces for historical and cross-chain compatibility

Validation

• cargo test -p leafage-evm-types --lib (18 passed)
• cargo test -p leafage-evm block_transactions --bin leafage-evm (3 passed)
• cargo clippy -p leafage-evm-types -p leafage-evm --lib --bins --tests --no-deps
• git diff --check

Deployment note
Deploy this change before enabling warmup against Arc BlockFiles whose CREATE transaction to_addr contains the created contract address.

[littlehand26]

Companion Arc writer change: Chaintable/arc-node#4. The Leafage change should be deployed first so CREATE transactions remain replayable after the writer starts emitting created contract addresses.

[littlehand26]

Both architecture builds and the multiarch manifest passed. The companion Arc writer PR #4 also passed mainnet CREATE validation: block 0x9e7a39 now emits transaction to_addr=0xdc6f9efa59c314a2c5ec8f2b28666415d228f5ee instead of zero while its root trace remains type=create. Keep the deployment order documented here: deploy this Leafage compatibility change before enabling warmup for newly produced Arc BlockFiles.