docs: fix NodeBin docstring to reflect accepted drag types

[Copilot]

The NodeBin component's docstring incorrectly stated it only accepts EXISTING_NODE drag types, while the implementation accepts both EXISTING_NODE and FAMILY_TREE_NODE.

Changes

• Updated JSDoc comment to document both accepted drag-and-drop types

/**
 * Renders a droppable NodeBin which accepts `EXISTING_NODE` and `FAMILY_TREE_NODE`.
 */
const NodeBin = ({ accepts, dropHandler }: NodeBinProps) => {
  const { dropProps, isOver, willAccept } = useDropTarget({
    id: 'node-bin',
    accepts: ['EXISTING_NODE', 'FAMILY_TREE_NODE'],
    // ...
  });
  // ...
};

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
fresco-sandbox	Canceled		Feb 10, 2026 4:33pm

[Copilot]

Pull request overview

Updates NodeBin’s JSDoc to accurately reflect the drag-and-drop types the component actually accepts, aligning documentation with the current useDropTarget configuration.

Changes:

• Updated NodeBin JSDoc to state it accepts both EXISTING_NODE and FAMILY_TREE_NODE.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.