Problem:
- flatCallTracer only matched the exact string "max code size exceeded".
- EVM now emits wrapped errors (for example, "max code size exceeded: code size ... limit ..."), causing parity error mapping to miss.
Solution:
- Update convertErrorToParity matching order: exact match first, then unwrap base error by splitting at the first colon, then keep existing prefix-based mappings.
- Add call_flat_error_mapping_test.go to cover exact match, wrapped match, prefix match, and unknown error passthrough.
Impact:
- Restores parity compatibility for wrapped max code size errors in flat call tracer output.
- Preserves existing mapping behavior for known and unknown error messages.
Validation:
- go test ./eth/tracers/native
e6a7add859