Module flow 

The flow file: a list of steps referencing a pixelcoords session by label, never by raw coordinate.

That indirection is the point. A label survives the UI moving; a coordinate does not. It also keeps a flow reviewable in git — a diff shows intent (“click submit”) rather than arithmetic.

Parsing is strict: unknown keys are errors, not silent no-ops, so a typo fails loudly at parse time rather than skipping a step at run time. (Session parsing, by contrast, is deliberately tolerant — see AGENTS.md on the compatibility contract.)

Structs

Flow

A parsed flow file.

Settings

Run-wide settings. Every field has a defensible default so a minimal flow file is three lines.

Enums

Axis

Which way a scroll goes.

FlowError

Parse errors, actionable by construction — the message names what to fix, in the tradition of the sister tool’s strict config parsing.

Step

What a step does.

Verify

Whether a run re-confirms a region before acting on it.