Publish, delete and module installs rebuild only what changed

Publishing or deleting a flow now splices that one flow into the running
graph instead of reconnecting every node in the installation, saving a
shared node's source rebuilds the flows using it, and installing modules
rebuilds only the flows holding a node that would not load.

Renaming stays on the full rebuild — it rewrites message references in
every other flow's document — and so does startup, which has no graph to
splice into.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01StpRc2C6au1WJ1EUU7fsfu

NOTEPAD.md

@@ -10,6 +10,12 @@ Deferring because out of scope is fine, but don't mention deferring than.
 
 ## Open
 
+### Dashboard UI rework (dedicated session)
+
+Rework the dashboard UI to make it more flexible in terms of the look and feel.
+I consider following design options a) overall appearance: material look or liquid glass (einUI https://github.com/einui/einui) b) color palette
+
+
 ### To be sorted
 
 - FEAT/UI: we promise testing, but currently don't provide an UI for testing e.g. mock values or probing edge cases of a flow. This should be resolved (in a dedicated session); I'm thinking of a "Labs" page, which allows simulating an installation with all the flows (using their draft states) and which allows injecting values or mocking values based on events in the past