Symptom

Tapping the corner avatar on ClientScreen opened a bubble whose header read “These are the types of node are used here. Select a type for a consolidated list.”, and whose menu listed About first alongside the node-type filters — an anti-pattern that mixed a help action in with type navigation.

Root cause

NodeChildren.loadAvatarMenuItems seeded the avatar menu with KrillApp.Client.About, and the avatar/Client chip face (NodeSummaryAndEditor’s KrillApp.Client -> branch) rendered a plain “select a type” sentence — no affordances for the things a new user actually wants (learn, build, get explained).

Fix

• Removed KrillApp.Client.About from loadAvatarMenuItems; the menu keeps Server/Server.Peer + swarm types. (Regression test: AvatarMenuItemsTest.)
• New AvatarHelpContent composable renders “How can I help?” over three action chips, used from the KrillApp.Client -> chip face:
  • Learn More → screenCore.executeCommand(KrillApp.Client.About) → AboutScreen (the existing About path).
  • Build A Swarm → screenCore.executeCommand(MenuCommand.KeepBuildingSwarm) → walkthrough chooser.
  • Explain Krill → opens https://krillswarm.com/discover in the browser via LocalUriHandler (the discover page is the tutorial entry point).

Prevention

Don’t surface one-off command actions (About, help) as fake entries in a type-filter list — give them their own affordance.