ENG-1741 Prevent duplicate keyboard shortcuts for node types

[trangdoan982]

https://www.loom.com/share/10168beedb5548b38b716ba59b10138f

Summary

• On node creation, skip auto-assigning the first-letter shortcut if it is already taken by any existing node type; leave empty instead so the user is prompted to set a unique one manually
• In node type settings, validate the shortcut field against all other node types and surface an inline error when a conflict is detected (same warning pattern as the existing tag/format validation)

Fixes: ENG-1741

Changes

• DiscourseNodeConfigPanel.tsx — collision-aware shortcut auto-assignment on "Add node"
• NodeConfig.tsx — validateShortcut callback + shortcutError state wired to the Shortcut text panel

Test plan

• Create a new node type whose label starts with the same letter as an existing node (e.g. add "Concept" when "Claim" with shortcut C exists) — shortcut should be empty, not C
• In node settings, manually set a shortcut that matches another node's shortcut — inline error should appear immediately
• Setting a unique shortcut clears the error
• Existing nodes with no conflicts are unaffected

Made with Cursor

[linear-code]

ENG-1741

[supabase]

This pull request has been ignored for the connected project zytfjzqyijgagqxrzbmz because there are no changes detected in packages/database/supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.