M4: add durable named Save Points

A Save Point is a name for a story position, and restoring one is head
movement. That is the whole architecture, and it is what ADR 012 and
BUILD-MILESTONES' note on M4 asked for: M3 made the head a stored
(branch, depth) and made arriving at one a row lookup plus a state restore,
so a Save Point needs no restore machinery of its own.

What the user gets:

- Name the moment they are reading, keep playing, restart the app, and come
  back to it. Restoring moves the story back and deletes nothing: the later
  turns stay, Redo still walks forward into them, and writing something
  different is what starts a new line while the old one is kept.
- Rename, delete, and a list, in a Save Points panel beside the branch panel,
  with a Save Point button next to Undo and Redo. Both confirmations say what
  is *not* destroyed, because that is the part the screen cannot show.
- Save Points survive export and import.

What was deliberately not built:

- No second restore path. `head.move_to_node` is the only new movement: its
  depth half is M3's `head.move_to` unchanged, and its branch half is the
  single assignment `switch_branch` already makes. No head field is written
  in the checkpoint router, nothing reconstructs state, nothing prunes a
  memory, nothing copies or deletes a turn, and restore never forks — the
  first write below the restored head does, through `fork_if_behind_head`.
- No automatic cleanup. A Save Point behind the head, or naming a line the
  story left, is doing its job (STORY-BRANCH-SEMANTICS §19). The one removal
  is a cascade: deleting a branch takes its Save Points, as it takes its
  memories, because the story they named went with it.
- No new ADR. ADR 012 already decides the architecture, and a table is not a
  decision.

The one call the planning package did not already make: restore moves the
branch half of the head only when the coordinate is off the path being read.
Doing it unconditionally would quietly hand back an abandoned continuation
whenever a Save Point in a shared prefix was restored; never doing it would
make a Save Point on a departed line unrestorable, which contradicts §19.
TECHNICAL-DESIGN §8.8 records it.

Schema: a `checkpoints` table holding a name, an optional note and a
(branch, depth) coordinate — no copy of any story. `create_all` builds it as
it did `memories` and `branches`; migration 80 adds the index. No backfill,
because nobody had named a position before M4.

The coordinate is deliberately not an action id: one coordinate holds every
attempt at a turn and exactly one is live, so a coordinate follows a retry
where a row id would pin a take the story no longer tells.

Tests: 680 pass (638 before). 42 new in tests/test_save_points.py covering
D11-D14, I04, L03, E-series lineage and memory isolation after restore and
divergence, the edge cases, and an M3-database migration. One pre-existing
fixture in test_tree_migration.py needed `checkpoints` added to its drop
list — SQLite refuses to drop a table another table references.

Not verified: the browser. No session has had a usable one, so the Save
Point panel's DOM behaviour is unobserved — as M3's Redo control still is.
The twenty-step sequence was driven over HTTP against a live server with a
real process restart instead, and all seventeen checks pass. M4 is
implemented, not accepted: no review has been written.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PWU4gTfLYY6Qq9U7aa9Qw2

backend/app/schemas.py

@@ -25,6 +25,10 @@ ICON_MAX = 16           # One emoji or glyph. VARCHAR(16).
 BRANCH_NAME_MAX = 80    # What a player called one line of the story. VARCHAR(80).
 PERSONA_NAME_MAX = 80   # The protagonist's name. VARCHAR(80).
 PERSONA_PRONOUNS_MAX = 40   # "they/them" and the like. VARCHAR(40).
+# M4: what a player called a Save Point. VARCHAR(120). Wider than a branch name
+# because these are sentences rather than labels — "Before entering the abbey"
+# is the example the specification uses throughout.
+CHECKPOINT_NAME_MAX = 120
 
 Name = Annotated[str, Field(max_length=NAME_MAX)]
 Tags = Annotated[str, Field(max_length=TAGS_MAX)]
@@ -35,6 +39,7 @@ Image = Annotated[str, Field(max_length=IMAGE_MAX)]
 Icon = Annotated[str, Field(max_length=ICON_MAX)]
 PersonaName = Annotated[str, Field(max_length=PERSONA_NAME_MAX)]
 PersonaPronouns = Annotated[str, Field(max_length=PERSONA_PRONOUNS_MAX)]
+CheckpointName = Annotated[str, Field(max_length=CHECKPOINT_NAME_MAX)]
 
 
 class ORMModel(BaseModel):
@@ -267,6 +272,67 @@ class BranchRename(BaseModel):
     name: Annotated[str, Field(max_length=BRANCH_NAME_MAX)] | None = None
 
 
+# ---------- Save Points (M4) ----------
+#
+# "Save Point" is the user-facing term and `checkpoint` is the internal one
+# (`BROWSER-UX-SPEC.md` §23). The wire format uses the internal name, as the
+# rest of this module does.
+
+
+class CheckpointOut(ORMModel):
+    """One Save Point: a name and the position it names.
+
+    The position is reported three ways because the panel needs three different
+    things from it. `turn` is what a reader counts — the same `depth + 1` the
+    branch list shows. `depth` and `branch_id` are the coordinate itself.
+    `on_path` says whether the position lies on the story being read, which is
+    how the panel can tell a Save Point on this line from one naming a line the
+    story has left; restoring either works, but they are not the same offer.
+
+    `resolved` is false when the coordinate no longer names a live turn, which
+    an action deleted out of the middle of a story can do. Restore refuses such
+    a Save Point rather than moving the head somewhere approximate, so the list
+    says so before the button is pressed.
+    """
+
+    id: int
+    adventure_id: int
+    name: str
+    note: str = ""
+    branch_id: int
+    depth: int
+    turn: int = 0
+    on_path: bool = True
+    resolved: bool = True
+    created_at: datetime
+    updated_at: datetime
+
+
+class CheckpointCreate(BaseModel):
+    """A Save Point at wherever the story is being read.
+
+    The position is not a field. A Save Point is made at the campaign's active
+    head, which the server already knows, and accepting a coordinate from the
+    client would be the second way to name a position — the thing this milestone
+    exists not to build.
+    """
+
+    name: CheckpointName
+    note: Prose = ""
+
+
+class CheckpointRename(BaseModel):
+    """A new label, and nothing else.
+
+    There is deliberately no coordinate here. `STORY-BRANCH-SEMANTICS.md` §24
+    keeps a Save Point's meaning auditable by refusing to move one: rename it,
+    or delete it and make another where you are.
+    """
+
+    name: CheckpointName | None = None
+    note: Prose | None = None
+
+
 class ActionUpdate(BaseModel):
     text: ActionText