docs/slate-issues/test-candidate-map/5558-5480.md
These TDD handoff notes cover issues #5558 through #5480 from the pilot set. Use the top-level index for range navigation and the dossiers for fuller thread context.
slatenot-a-test-candidateslateready-nowTransforms.moveNodes later-sibling destination semanticsTransforms.moveNodes(editor, { at: [], to: [2], match })not-a-test-candidatenot-a-test-candidatenot-a-test-candidateEditor.start root-path usageslate-reactblocked-on-repronot-a-test-candidatenot-a-test-candidateready-nowslateready-with-minor-setupanother line`
not-a-test-candidateNode.common docs wordingslate-historynot-a-test-candidateslate-reactready-with-minor-setupmobx-react-lite observer<Slate> below itslateready-nowOmitFirstArg membersCustomEditor as in the Slate TypeScript docsBaseEditor member typed with OmitFirstArganynot-a-test-candidatenot-a-test-candidateslate-reactready-with-minor-setupset_selectionset_selection progression rather than duplicate textslateready-nowTransforms.setNodes merge callback typingTransforms.setNodes with a typed merge callbackmerge should be typed to the actual per-key values it receives instead of a generic object-only shapeslate-reactnot-a-test-candidatevalueslateready-nowcreateEditor base type in plugin compositioncreateEditor()createEditor() should expose a base type that allows plugin-order mistakes to be caught instead of being masked by the global Editor typeready-with-minor-setuptestingready-with-minor-setupnot-a-test-candidateready-nownot-a-test-candidateThe thread points at an upstream Chromium fix and a later real-world confirmation that the issue is gone.