Prop 1030: Recover expired IBC client 07-tendermint-3714 (Osmosis <> QUAD Core lane)

07-tendermint-3714 is Osmosis' IBC light client of the QUAD Core chain (chain-id: quad). It guards connection-11069 (counterparty: quad connection-9), including the open transfer channel channel-110364 (counterparty channel-13) with 266.9 OSMO in its escrow account backing vouchers on the counterparty chain, and the lane's ICS-27 interchain-account channels whose host accounts are bound to this connection and hold over 1,000 OSMO delegated to an Osmosis validator (osmovaloper196ax4vc0lwpxndu9dyhvca7jhxp70rmcmmarz7) with rewards unharvestable while the lane is down. The client was originally created with a short 3-day trusting period and expired on 2026-07-09 (last consensus state 2026-07-06) after a relaying pause; the connection and transfer channel remain OPEN on both chains, but nothing can be proven against the expired client, so transfers are frozen and the closed ordered ICA channels cannot be reopened.

This proposal performs the standard IBC client recovery (ibc-go MsgRecoverClient): the expired client state is replaced with the state of substitute client 07-tendermint-3733, created 2026-07-23 with identical chain-id, trust level (1/3), unbonding period (21 days) and max clock drift (50s), and a safer 14-day trusting period. No funds move and no new permissions are granted; recovery only revives the existing canonical lane, unfreezes the escrow-backed transfer path, and avoids fragmenting liquidity across duplicate connections.

QUAD (https://uquad.org) operates public RPC infrastructure (including osmosis endpoints) and maintains active hermes relaying for this lane with client-freshness monitoring so it cannot idle-expire again.