Rework node layout and bit width resolution, and add the Const/AndN/OrN intrinsics

[chelproc]

Two refactors and the features built on top of them: the node renderer is split into a layout and a geometry step, bit widths are resolved per node instead of per component pin, and on that base the Const, AndN and OrN intrinsics, display config editing and a play-mode guard are added.

Node renderer: layout → geometry split

• A layout (size + relative nodePinOffsetById) is separated from a geometry (absolute rect + nodePinPositionById). ccComponentEditorRendererLayoutToGeometry turns one into the other with the position of the node, and getCCComponentEditorRendererNodeGeometry composes the two steps.
• A layout calculator now receives the config of the node instead of its position, so a node can size itself from its config.
• The node wrapper is an <svg> instead of a <g>, so a renderer draws in local coordinates and can use percentage sizes (width="100%" in the Default renderer). Display and Const compose the Default renderer for their frame instead of drawing their own.
• box-sizing: border-box is applied globally, which the HTML embedded in a foreignObject relies on.

Bit width resolution

• getComponentPinBitWidthStatus only knew the component pin definition, so a fixed width was evaluated against definition.initialConfig and changing the resolution of a display never changed the width of its Pixels pin. Aggregate and decompose could not be evaluated there at all and were special cased into a manual fix mode, with their widths recomputed by hand in CCNodePinStore.
• The two concerns are now split: getComponentPinBitWidthStatus reports only how a width is determined (automatic or nodeDependent), and getNodePinBitWidthStatus resolves it from the config of the node and the bit widths manually specified for its pins. The fixed policy is renamed to calculated to match.
• isBitWidthConfigurable and isSplittable are folded into the configurable policy, so the policy is the only source of truth. The hard-coded cases for aggregate, decompose and broadcast are gone: manual widths are collected per pin key (In, Out, …) and passed to calculateBitWidth, for which intrinsic pin attributes now carry their key.
• Results are cached in CCNodePinStore and dropped on node pin and connection changes, and on the new didUpdateConfig event of CCNodeStore, which is kept separate from didUpdate so that frequent position updates do not drop the cache.
• Because a width can now change after a connection was made, hasCompatibleBitWidths backs isConnectable, connections whose ends no longer agree after a config change are dropped, and existing connections are re-validated when a new one is registered.

New intrinsics

• Const — config: { mode, data }, an output whose width is calculated from data.length, and an evaluate that writes the configured data to the output pin. The node renders a text editor whose contents are parsed into data on every keystroke, in one of three modes (binary, hex, UTF-8) chosen by a toggle group and kept in the config. Text that is not valid in the current mode only marks the editor and leaves the last valid data in place.
• AndN / OrN — reduce every bit of their configurable, splittable input to a single output bit.
• Intrinsic evaluate functions receive the config of the node as a fourth argument.

Display

• A settings popover on the node edits the resolution and persists it through store.nodes.update.
• The layout scales with config.resolution and shares its constants with the renderer.
• Pixel fill indexes inputValue in row-major order, fixing the previously reversed pixel order.

Play mode and simulation

• isEachInputPinConnected and the useCanSimulate hook disable the play button of the ViewModeSwitcher while any input pin is unconnected.
• executeSimulation no longer subscribes to raw node and connection store events.
• Input values are keyed by { componentPinId, timeStep } with an explicit serializeInputValueKey instead of JSON.stringify of a tuple, and an initial value takes its width from the node pin implementing the component pin.

Tests

nodePin.test.ts covers bit width resolution (from a display config, propagated over a connection, summed over the manual widths of aggregate and decompose pins, broadcast, and a configurable pin missing its manual width) and the consistency of connections across a config change.

Open points

• Dropping a connection on a config change can invalidate another one; resolving that needs a repeated sweep (TODO in connection.ts).
• The re-validation on didRegister in CCConnectionStore looks up nodes.getManyByComponentId(connection.parentComponentId), which returns the instances of the parent component rather than the nodes inside it, so it is currently a no-op for the component being edited. Making it match, without guarding against re-registering from inside the handler, would recurse.
• The Const layout calculator still carries the grid constants copied from Display, and the width of its foreignObject subtracts a hard-coded 30 for the output pin.

[cloudflare-workers-and-pages]

Deploying create-cpu-c8345196-9409-4cce-afc4-389f413ad8ee with    Cloudflare Pages

Latest commit:	e293840
Status:	✅  Deploy successful!
Preview URL:	https://c4f9f4d5.create-cpu-c8345196-9409-4cce-afc4-389f413ad8ee.pages.dev
Branch Preview URL:	https://20260606.create-cpu-c8345196-9409-4cce-afc4-389f413ad8ee.pages.dev

View logs