Every venue the desk can see
Pool discovery reads the v4 PoolManager's own Initialize events rather than a third-party token API, so the venue list is derived from the chain the desk trades on and nothing else.
Why there is no v3 here
This is a finding, not a configuration choice, and it is the reason the routing layer has exactly one adapter.
The canonical Uniswap v3 addresses were probed on chain 4663. Code exists at all three, but the three addresses carry three different codehashes — impossible for a genuine v3 deployment, where the factory, router and quoter each have one well-known hash.
Calling feeAmountTickSpacing on the address that should be the factory reverts. Whatever is deployed there, it is not Uniswap v3.
So no v3 adapter is registered and nothing in the routing layer can select one. A desk that assumed the canonical addresses were real would have quoted against contracts it had never verified — which is the specific mistake that turns a market-making strategy into a donation.