Trim needless comments and fix the picker width

Remove comments that only restate the code, keeping the section banners
and the notes that carry a reason, a measured fact or an external
contract.

ButtonOptions.width claimed to be a fixed width but only set minWidth,
so the Graph and Texture pickers grew with the name they showed. It is
now what it promises, with a separate minWidth for the buttons that have
two forms. Narrow buttons shrink their padding, otherwise a 24px icon
button had 8px left for its glyph and truncate dropped it entirely.

__gm.labelsDropped() guards that class: the overflow guard only saw text
that was too wide, never a label truncated to nothing.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/core/graph/NodeRegistry.ts

@@ -15,31 +15,25 @@ export interface PortDef {
 export type NodeCategory = 'event' | 'flow' | 'data' | 'variable' | 'action';
 
 export interface RunResult {
-  /** Values for the node's data outputs (cached for the rest of the pulse). */
+  /** Cached for the rest of the pulse. */
   outputs?: Record<string, Value>;
   /** Exec output(s) to continue along; omitted = the node ends the flow. */
   next?: string | string[];
 }
 
-/**
- * Describes one node type: its ports, its inline settings and how it runs. The editor
- * palette, port rendering, connection validation and the inspector fields are all derived
- * from this – adding a node type means adding one definition, no UI code.
- */
+/** Palette, port rendering, connection validation and inspector fields are all derived from this. */
 export interface NodeDef {
   type: string;
   label: string;
   category: NodeCategory;
-  /** Shown in the palette and the inspector. */
   description: string;
   inputs: PortDef[];
   outputs: PortDef[];
   /** Node settings that are not ports (key name, operator, variable). */
   params: PropertyDef[];
   /**
-   * Executes the node. Pure data nodes (no exec pins) are evaluated on demand whenever an
-   * input downstream needs their value; exec nodes run when the flow reaches them.
-   * Event nodes have no `run`; the interpreter seeds their outputs when it fires them.
+   * Pure data nodes are evaluated on demand when a downstream input needs their value; exec nodes
+   * run when the flow reaches them. Event nodes have no `run` – the interpreter seeds their outputs.
    */
   run?(ctx: NodeContext, inputs: Record<string, Value>, params: PropertyBag): RunResult;
 }
@@ -74,12 +68,11 @@ export function hasExecInput(def: NodeDef): boolean {
   return def.inputs.some((p) => p.type === 'exec');
 }
 
-/** Data inputs that may carry an inline value when unconnected (numbers, strings, booleans, any). */
+/** Data inputs that may carry an inline value while unconnected. */
 export function inlineInputs(def: NodeDef): PortDef[] {
   return def.inputs.filter((p) => p.type !== 'exec' && p.type !== 'object');
 }
 
-/** A PropertyDef for editing the inline value of a port. */
 export function inlineInputDef(port: PortDef): PropertyDef {
   switch (port.type) {
     case 'boolean':