ci: witness-producing nodes self-gate pipelined SRC off

[lucca30]

Problem

The pipeline leg asserts that on a witness producer every witness comes from the pipelined SRC completion path:

Witness provenance: on a non-mining full-sync witness producer, every witness must come from the pipelined SRC completion path — the counters track each other 1:1.

bor#2405 removes that combination, so this assertion is what makes that PR's pipeline-e2e-tests leg red.

Why bor is removing it

The SRC witness is derived from a FlatDiff, and CommitSnapshot ends by draining the shared readerWithCache into it. That record carries no attribution, so the speculative block prefetcher's reads land in it alongside the block's own — and ProcessBlock builds the prefetcher's throwaway StateDB from the same reader triple as the processor, so how far the prefetcher got before the block finished is wall-clock dependent.

Two nodes importing the same block therefore derive witnesses of different sizes. WIT/2's cross-peer page-count check reads that as a misbehaving peer and drops and jails it.

core.TestPipelinedSRCDiffCarriesBlockPrefetcherReads in that PR pins the leak; eth.witnessSafeAccelerators turns pipelined import SRC off on any witness-recording node because of it.

Change

Witness producers join stateless-sync nodes as a class that self-gates the pipeline off. Root mismatch and witness production stay strictly asserted on those nodes; only the src > 0 activity expectation goes.

Merge order — why the checks are commented, not inverted

bor's kurtosis-pipeline-e2e.yml pins this repo at ref: main. Asserting src == 0 here before the bor guard reaches develop would fail every open bor PR, not just #2405.

So the two witness-node src checks ship commented with a TIGHTEN AFTER bor #2405 marker. Merge this first, then bor#2405, then a one-line follow-up here to turn them back on.

Cost worth flagging

After this, participant 6 — the plain pipelined rpc node — is the only node exercising pipelined SRC end to end. That is thinner coverage than before. Restoring it means adding a second non-witness pipelined rpc node, which changes the topology the stateless suite asserts on, so it is left for a follow-up rather than bundled here.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YBppHd4UqVqBBkEf7uDT7h

[pratikspatil024]

I guess this is not needed anymore? @lucca30