From fe578c57fd154c77cd108c8709b217bb54dd095f Mon Sep 17 00:00:00 2001 From: atlas Date: Sat, 24 Oct 2026 05:06:30 +0200 Subject: [PATCH] ui docs: restore how custom flows are added --- docs/swarm/ui.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/swarm/ui.md b/docs/swarm/ui.md index fb448081..ea07eaea 100644 --- a/docs/swarm/ui.md +++ b/docs/swarm/ui.md @@ -226,11 +226,12 @@ restores it. Each **custom** flow shows its name and whether it's on. Every flow draws as an indented tree: the forge events it starts from, the conditions under it, and the todo each branch ends in. +The page edits nothing else. Add custom flows with `PUT /api/notify/flows`. + A switch sends the whole flows document with the revision the page read, `0` if -it read no document. The controller refuses it when the stored revision is -another, including a document written since the page read none, and the page -shows why. Reload to switch against the current document. -another change landed since, the controller refuses it and the page shows why. +it read no document. The controller refuses the switch when the stored revision +is another, including when someone wrote a document after the page read none, and +the page shows why. Reload to switch against the current document. ### Sending a message to an agent