Add curator Movement links config with proof URLs and admin-gated delete votes.

Persist lineage in PostgreSQL, seed documented edges, and keep timeline/tree consumers API-backed with a static fallback.

Co-authored-by: Cursor <cursoragent@cursor.com>

Documentation/movement-tree.md

@@ -102,6 +102,8 @@ All constants sit at the top of the two files and are safe to tune:
 | `FULL_VIEW_WIDTH_SHARE`, `ZOOM_SPREAD_EXPONENT`, `MAX_FIT_BOOST` | `MovementTree.tsx` | crown spread vs. zoom |
 | `MIN_LIMB_RISE_PX`, `MIN_JUNCTION_RISE_PX`, `MAX_THICKNESS_OF_LENGTH` | `MovementTree.tsx` | crown legibility at full zoom-out |
 
-New lineage edges only need adding to
-[`client/src/data/movement-lineage.ts`](../client/src/data/movement-lineage.ts) — the tree
-picks up parents, grafts, thickness and spacing from there automatically.
+New lineage edges: top-left **Movement links** (required proof URL) →
+`movement_lineage_links` / `GET /api/movement-links`. Curators vote to delete;
+admins hard-delete. Static fallback remains in
+[`client/src/data/movement-lineage.ts`](../client/src/data/movement-lineage.ts).
+The tree picks up parents, grafts, thickness and spacing from the active lineage automatically.