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/data-and-images.md

@@ -263,18 +263,23 @@ Discovered rows are stored with `confidence: discovered` and `discovered_via` (e
 
 Extend `art-influences-data.js` for high-quality curated chains; use discovery to suggest additional artist and movement links for manual review.
 
-## Movement lineage (frontend flow diagram)
+## Movement lineage (timeline / Tree of Art)
 
-Separate from the painting influence graph, `client/src/data/movement-lineage.ts` lists **art-movement** predecessor→successor pairs used only by `MovementBands.tsx` to position streams and draw branch connectors (e.g. Impressionism → Post-Impressionism → Fauvism / Cubism / Expressionism).
+Separate from the painting influence graph, **`movement_lineage_links`** stores art-movement predecessor→successor pairs used by `MovementBands`, `VerticalMovementBands`, and `MovementTree` (e.g. Impressionism → Post-Impressionism → Fauvism / Cubism / Expressionism).
 
 | Aspect | Detail |
 |--------|--------|
-| Storage | TypeScript module in the client — **not** a database table |
-| Format | `[parentMovementName, childMovementName]` tuples; names must match `art_movements.name` from the seed |
-| Multiple parents | Allowed (e.g. Post-Impressionism feeding several modern paths) |
-| Sources | Curator notes in the file reference Met essays, TheArtStory, and similar |
+| Storage | PostgreSQL `movement_lineage_links` (`db/migrate-movement-links.sql`) |
+| Required proof | `proof_url` must be a valid `http(s)` URL (museum essay, literature, web reference) |
+| Optional | `link_year_approx`, `proof_label`, `notes` |
+| Format | FK pairs to `art_movements`; multiple parents allowed |
+| API | Public `GET /api/movement-links`; curator `POST` create + delete votes; **admin-only** hard `DELETE` |
+| UI | Top-left **Movement links** (timeline header); also linked from Influences. Curators create + vote-to-delete (reason); admins review votes and hard-delete |
+| Fallback | `client/src/data/movement-lineage.ts` if the API returns no rows |
+| Defaults | Seeded on migrate / first GET from Met / TheArtStory / Christie's essays |
+| Delete votes | `movement_lineage_delete_votes` (`db/migrate-movement-link-delete-votes.sql`); one vote per curator per link |
 
-To add or fix a branch, edit `MOVEMENT_LINEAGE` in that file and rebuild the client. No migration or API change is required.
+To add a branch, use **Movement links** (proof URL required). To remove one, curators vote with a reason; an admin deletes after review. No client rebuild is required for data changes; rebuild `client/dist` only when shipping SPA changes to the API-static port (`3451` / prod).
 
 ## Movement gallery interiors (frontend)