Renaming

Renaming changes an entity's identifier, graph references, module paths, and generated symbols. Select Rename ID on the canvas. Changing a display name does not rename an identifier.

Example: rename decrement to choose_next

Renaming the node moves both structural and domain-specific files:

Before	After
◆ nodes/decrement/__init__.py	◆ nodes/choose_next/__init__.py
● nodes/decrement/impl.py	● nodes/choose_next/impl.py
◆ edges/check_counter__decrement/__init__.py	◆ edges/check_counter__choose_next/__init__.py
◆ edges/decrement__update_counter/__init__.py	◆ edges/choose_next__update_counter/__init__.py
◆ nodes/decrement/visit/check_counter__decrement/__init__.py	◆ nodes/choose_next/visit/check_counter__choose_next/__init__.py
● nodes/decrement/visit/check_counter__decrement/impl.py	● nodes/choose_next/visit/check_counter__choose_next/impl.py
◆ nodes/update_counter/visit/decrement__update_counter/__init__.py	◆ nodes/update_counter/visit/choose_next__update_counter/__init__.py
● nodes/update_counter/visit/decrement__update_counter/impl.py	● nodes/update_counter/visit/choose_next__update_counter/impl.py

What changes

Verdog:

• updates the selected ID and every reference to it in ◆ project.json;
• moves affected authored files and regenerates declarations at their new paths;
• updates structural symbols and static Python imports that contain the old module path;
• when a node is renamed, updates the endpoints of its incoming and outgoing edges. An automatically derived edge ID such as decrement__update_counter follows the rename and becomes choose_next__update_counter; a custom edge ID or display name remains unchanged. Automatically derived edge names follow their endpoints.

The operation preserves authored function bodies except for recognized structural references. It does not resolve module names assembled dynamically from strings. Generated files are recreated from the updated graph, and obsolete generated paths are deleted. Local modifications to a recorded generated file block the operation.

Renaming an edge directly moves its generated edges/<edge-id>/ declaration and, for an executable target, its generated and authored visit directory. The edge registry is regenerated with the new import and symbol.