[marvinkruse]

Summary

Two more fuzz tests failed randomly in CI on dev after #780 and #781 merged. Neither failure was related to those changes.

• ERC20PaymentClientBaseV2Test.test_setFlags: with all 256 bits set, the test's uint8 flag counter overflows. _setFlags has the same limit because _flagCount is a uint8, so setting all 256 flags reverts. It's admin-only and far beyond the number of flags in use, so the contract stays as is and the test excludes that input.
• PP_StreamingV1Test.test_ValidPaymentOrder: the expected value left out the origin/target chain check that validPaymentOrder performs. Whenever the fuzzer produced an otherwise valid order (e.g. a deployed token address) with random chain IDs, the test expected true. The streaming mock now exposes _validOriginAndTargetChain (same as the PP_Simple_v2 mock), and the test includes it.

Test-only change.

Deployment Steps

✅ No deployment steps required.

Test Plan

Pre-merge checklist

• Both tests pass with FOUNDRY_FUZZ_RUNS=30000
• Full suite with FOUNDRY_PROFILE=ci passes under seeds 0x1, 0x2a, 0x1337 (1586/1586 each)
• forge fmt --check passes
• CI green