Let a branch be named, and thrown away

SP7 needs three branch operations and SP5 built one. Switching exists;
naming and deleting had no column and no route between them.

A name is stored because a player chose it. An unnamed branch keeps NULL
rather than a generated "branch 4" — a generated label is derived, and it
would go stale the moment a branch before it is deleted and the ordinals
shift underneath. The client draws those from the fork depth, which
nothing can shift. The v2 bundle carries the name for the same reason it
carries the fork points and leaves `lineage` out: it is a decision, not
something computed from one.

Delete is what stands between a tree and unbounded growth, since nothing
prunes one on its own. It refuses two branches: the root, which holds the
turns every other branch borrows, and the one being read — including any
branch the head was forked from, which is the same mistake in disguise and
the one that would cascade the head away and leave head_branch_id pointing
at nothing. The nodes, memories and descendants go through the foreign
keys that already cascade.

A cursor standing on a deleted branch is cleared. On Postgres a stale
branch id would simply never resolve; SQLite hands the freed id to the
next fork, and then the anchor resolves onto a branch it has never seen
and calls a stretch of story already summarized.

396 tests, 15 new.

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

backend/app/migrations.py

@@ -251,6 +251,12 @@ MIGRATIONS: list[tuple[int, str | dict[str, str]]] = [
     # handful of rows behind it, which ix_actions_branch_depth already serves,
     # so this is a no-op statement that gives the passes a version to hang on.
     (60, "CREATE INDEX IF NOT EXISTS ix_actions_branch_depth ON actions (branch_id, depth)"),
+    # Phase 14, SP7 — a branch can be named. NULL is "nobody named this one",
+    # which is every branch alive when this runs, so there is no backfill and
+    # nothing to derive. `branches` holds a handful of rows per adventure rather
+    # than one per turn, so unlike SP1's and SP4's this rewrite is a few hundred
+    # rows against a few hundred thousand and needs no VACUUM FULL of its own.
+    (61, "ALTER TABLE branches ADD COLUMN name VARCHAR(80)"),
 ]
 
 LATEST_VERSION = max((v for v, _ in MIGRATIONS), default=1)