when a local binding is used inside a macro call (e.g. write!(s, "{}", x.field) or write!(s, "{}", t.0)), the usage's name node lives in the macro expansion tree while the syntax editor is rooted at the source file tree. passing the expansion node to editor.replace() causes apply_edits to panic when it resolves the SyntaxNodePtr against the wrong tree. instead of skipping macro-expanded usages, map them back to the original source via sema.original_range_opt() and replace the text at the mapped range. this follows the established pattern of upmapping macro code to source code rather than ignoring it. for destructure_struct_binding, macro field accesses like x.y are replaced with the destructured field name y directly in the source. for destructure_tuple_binding, a new TextReplace variant on EditTupleUsage handles text-based replacements for macro-expanded tuple index accesses like x.0 → _0. when original_range_opt cannot map back (e.g. the index originates from the macro body rather than the call site), the code falls back to NoIndex (wrapping in block comments) or skipping, matching previous behavior. this also replaces the MacroStmts ancestor check in destructure_tuple_binding, which only covered macros expanding to multiple statements and missed single-expression macros (MacroExpr). fixes rust-lang/rust-analyzer#20716