"""The tool walkthrough's VERSION — the only half of it the server owns.

The steps themselves are content and live in the SPA (`frontend/src/lib/
toolTour.ts`), because they point at easel's own chrome and are written, not
authored: putting them in a table would buy an authoring UI nobody asked for and
a migration every time a sentence changes. This mirrors the precedent rian
pointed at — hartlingowners keeps `TOUR_VERSION` in Python and the step data in
its template.

**Bump this when the steps change enough that someone who has already been
walked through should be walked through again.** Everyone whose stored
`seen_version` on a board is lower is re-offered it on their next visit; nobody
is ever shown it twice at the same version.
"""

TOOL_TOUR_VERSION = 4