humainflow-web/src
Lucio Lelii 1aa32efa80 Draw and wire storage nodes as resources, not steps
A storage node comes from the server with the RESOURCE role. In the
editor it is drawn apart from the steps - dashed, teal, labelled
'Storage · not a step' - and its targets take a connection from every
step that writes there; a view parameter (<view>.<parameter>) still
takes one.

Its edges are left out when the editor works out which connections lead
back round a loop: a write followed by a read of the same node is not a
cycle, the same view the server takes.

The execution view draws the node from the flow, since it never has a
step, with no status of its own, so the reads and writes on its edges
still have somewhere to go.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-28 12:23:08 +02:00
..
app Draw and wire storage nodes as resources, not steps 2026-09-28 12:23:08 +02:00
environments Ask for a personal storage connection from the vault 2026-09-28 11:55:45 +02:00
index.html Add the SPDX licence header to every source file 2026-09-16 12:10:18 +02:00
main.ts Add the SPDX licence header to every source file 2026-09-16 12:10:18 +02:00
runtime-config.d.ts Add the SPDX licence header to every source file 2026-09-16 12:10:18 +02:00
styles.css Show a list's full name on hover, and make its count easy to read 2026-09-25 19:35:14 +02:00