Symptom

Clicking a Project node in ClientScreen immediately navigated to ProjectScreen, skipping the avatar-bubble node menu that every other node type shows. There was no opportunity to add child nodes from the ClientScreen graph view, and the transition was jarring.

Root cause

NodeItem.kt’s showMenu() function grouped KrillApp.Project with DataPoint.Graph, Project.Diagram, and Project.Camera in the branch that called executeCommand(MenuCommand.Expand). MenuCommand.Expand for a Project causes KrillScreen to render ProjectScreen immediately, bypassing the speech-bubble node menu entirely.

Fix

• NodeItem.kt: removed KrillApp.Project from the Expand branch in showMenu(). Added an explicit no-op Unit branch so Project nodes leave selectedCommand null, keeping KrillScreen on ClientScreen and letting the avatar bubble render the per-node NodeMenu.
• NodeMenu.kt: changed the chip-row click handler to call executeCommand(MenuCommand.Expand) when node.type is KrillApp.Project, and viewEditor() for all other types. This gives the Project chip the same navigate-to-ProjectScreen role that the old immediate tap had, while keeping add-child options one level above it in the menu.

Prevention

When a new node type has a dedicated full-screen view, the showMenu() dispatch in NodeItem.kt and the chip click in NodeMenu.kt must be reviewed together. A node that belongs in KrillScreen’s fullScreenTypes set should not automatically belong in the showMenu() Expand branch — the branch drives whether clicking in the graph navigates away or stays to show the menu.