A task holds the whole night, not one end of it

One command per task was the wrong unit. A charging window is two commands
and reads as one intention, so it was two rows that had to be named twice,
switched off twice, and kept in step by hand — and there was nowhere to put
the third thing, the ease down to 10 A once the house is asleep.

So a task holds a flow. Steps are rows in the editor: an action, a time, and
the ceiling under the one action that takes one. The chargers and the days
belong to the task, because they are the same for every step of a night, and
the switch governs all of it.

The steps keep the order they were written rather than being sorted by the
clock. A night crosses midnight, and clock order files "start at 23:00" last,
behind the stop that closes it — which is not the flow anybody described.
Nothing about firing depends on the order: every step is timed on its own,
and the sweep asks each one whether its minute has come.

Run now moved onto the step. A flow is not a thing that can happen at once —
firing a start and the stop that closes it back to back would leave the
charger where it began and prove nothing — so the button fires the one line
it sits on, and the outcome names the step by its time.

The stored shape changes with it: action/amps/time give way to a steps list.
The collection was a day old and empty, so this replaces them outright rather
than carrying a compatibility path for a schema nothing has run on.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

API Server/internal/bootstrap/schema.go

@@ -236,11 +236,12 @@ var collectionsSchema = map[string][]fieldDef{
 		// standing wish that keeps covering chargers imported later — and a
 		// multi-relation would have to be rewritten on every import to say it.
 		fJSON("chargers", 2000),
-		fSelect("action", []string{"start", "stop", "limit", "boost"}, true),
-		fNumber("amps"), // the ceiling, for the "limit" action
-		// 24-hour "HH:MM", read in the IANA zone the task was written in. The
-		// server's clock is not the one the user set the time by.
-		fText("time", true),
+		// The flow: [{action, amps, time}, …] in the order it runs. A whole
+		// charging window is one task rather than the two that would otherwise
+		// open and close it, so it is named once and switched off once. Times are
+		// 24-hour "HH:MM" read in the zone below — the server's clock is not the
+		// one the user set 23:00 by. Validated in internal/api/chargingtasks.go.
+		fJSON("steps", 4000),
 		fText("zone", false),
 		fJSON("days", 200), // 0=Sunday … 6=Saturday; empty means every day
 		fBool("enabled"),