Create new sibling editing flow when moving past rightmost node

[deepfates]

Summary

• remove the select+A combo and instead track pending sibling creation when the right arrow is pressed on the last available continuation
• open the edit menu in this case with a draft node and only append a new sibling when the edit is saved
• add a createSiblingNode helper on the story tree hook to append siblings, update selection, and keep metadata in sync

Testing

• npm run lint (fails: ESLint configuration missing)
• npm run build (fails: rollup optional dependency not installed in environment)

---

https://chatgpt.com/codex/tasks/task_e_68cf1f2317048327a73c1ca3ec15e86a

[Copilot]

Pull Request Overview

This PR introduces a new sibling editing flow that replaces the previous select+A combo with automatic sibling creation when navigating past the rightmost node. When the right arrow is pressed on the last continuation, it now opens the edit menu with a draft node and only creates the sibling when the edit is saved.

Key changes:

• Track pending sibling creation state instead of immediately creating nodes
• Open edit menu with draft node when moving past rightmost continuation
• Add createSiblingNode helper to manage sibling creation, selection updates, and metadata synchronization

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
client/interface/hooks/useStoryTree.ts	Adds createSiblingNode helper function for managing sibling node creation and state updates
client/interface/Interface.tsx	Implements pending sibling state tracking and draft node editing flow with right arrow navigation

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The dependency array is missing touchStoryUpdated which is called within the createSiblingNode function. This could lead to stale closure issues if touchStoryUpdated is redefined.

Suggested change

	[storyTree, currentTreeKey, setTrees],
	[storyTree, currentTreeKey, setTrees, touchStoryUpdated],

[Copilot]

Using Date.now().toString(36) for ID generation could potentially create collisions in rapid succession. Consider using a more robust ID generation method like crypto.randomUUID() or a dedicated UUID library.

Suggested change

	id: `draft-${Date.now().toString(36)}`,
	id: `draft-${crypto.randomUUID()}`,

[Copilot]

This ID generation method using Math.random() is inconsistent with the draft ID generation above and could potentially create collisions. Consider using a consistent, more robust ID generation method throughout the codebase.