Hydration does not change identity
attach_transport changes how missing state may be fetched, not which chain, block, or execution state the CLIENT identifies.
- The source CLIENT remains unchanged.
- The transport's trusted declared chain id must match the CLIENT lineage; the pinned header is then validated against the provider.
- Keep credentials in runtime transport configuration; they are not part of durable CLIENT identity.