Say a rebuild has two scopes, and close the notepad items it fixes

The module docstrings and the notepad still described one rebuild that touches everything. Closes the toggle cost, the seeding cost, the per-save rebuild, the modules/apply rebuild and the Playwright spec that could not fit a rebuild into its five seconds; files the follow-ups the refactor leaves behind. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01StpRc2C6au1WJ1EUU7fsfu
2026-08-23 19:05:23 +02:00
parent 56396732a4
commit 32bc0a5e66
3 changed files with 43 additions and 24 deletions
@@ -4,6 +4,11 @@ One pipeline holds the nodes of every loaded flow. Edges are not declared —
 they follow from message names, so a node consuming ``heating.setpoint`` is
 downstream of every node providing it. Several producers of one message are
 allowed: each publication triggers the consumers, and the latest value wins.
+
+Because the wiring is derived rather than declared, one flow's nodes can be
+swapped in place: `replace_flow` splices them into the list and derives the
+whole map again, which gets the edges crossing into other flows right by
+construction. A deploy does that rather than building a second pipeline.
 """

 from __future__ import annotations