Duplicating a shortcut drops you into 'recording' mode

Check the duplicate flow: onDuplicateFromContext in Sidebar.jsx:793 appears to fire alongside assignCtx. Likely the duplicated assignment is placed into a state that requires a fresh key (since the source key is occupied), and the capture overlay auto-opens. Two reasonable resolutions: (a) create the duplicate with a deferred-key state and a clear "Press 'Record' to assign a key" empty state, no auto-capture; or (b) clone the source key onto the duplicate and let the user resolve the conflict afterwards. Option (a) is safer.