counter-asic-2-node.md: the CPU hash rate across the switch in run 2 (approximate) and the verifier slowdown the era agent measured, to be re-measured after the mixer fix

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs/plans/counter-asic-2-node.md

@@ -108,6 +108,8 @@ Binaries rebuilt on ca2-v3 b105a55 (era layout merged on the mixer: `V3_CLASS` =
 | Forks | sinks `712c1b212091dcdc` on all three nodes, block counts 303 / 303 / 303, one tip each |
 | Program and cache ready, one CPU core | v2 epoch 0 178 ms, the first v3 epoch 181 ms, an in-day swap 2 ms |
 
+CPU hash rate across the switch, run 2, miner cpu0 (one thread, the Mac shared with other agents' builds, so approximate): the cumulative rate read 0.024 MH/s through the v2 epochs (30 to 151 s), then fell to 0.021 MH/s cumulative by 271 s (100 s under v3), which puts the v3 interval rate near 0.017 MH/s, about 30 percent under v2 on the CPU interpreter (the era's strided windowed loads and the mixer path). The node has no per-block verify timing line; the era agent's measurement of the CPU verifier (`igneum-pow`, 0.604 ms per warp on readwidth against 1.332 ms on 88dafbc, the mixer's `derive_items` path at m = 1) is the number to fix before the publish, and the before/after goes here when the mixer agent's commit lands.
+
 Epoch 0's v2 id is the same in both runs (`8f8806638d59850f`: a v2 program is untouched by the era code, on the chain as in the packs); the v3 ids differ from run 1 because the era draw is now inside the class.
 
 The PC 2 suite job for the same tree: `build-20261005-215219` (fork 79bd8e10, main b105a55, published 21:52:19Z; its SUMMARY is the G6 evidence, recorded by the coordinator in the status file).