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>
This commit is contained in:
Danila KhodjaefandCursor committed 2026-09-08 14:37:20 +03:00
1 parent 2b4cdc5a9f
commit 1b760faf0d
36 files changed
+2051 -43

No files matched your search

+11
View File
@@ -18,6 +18,8 @@ const INCREMENTAL_MIGRATIONS = [
'migrate-tours.sql',
'migrate-curator-notes.sql',
'migrate-user-roles.sql',
'migrate-movement-links.sql',
'migrate-movement-link-delete-votes.sql',
];
const BOOTSTRAP_ADMIN_PERMISSIONS = [
@@ -80,6 +82,15 @@ async function migrate() {
console.log('Bootstrapping curator account (if needed) …');
await bootstrapCurator();
try {
const { seedDefaultsIfEmpty } = require('./movement-lineage-service');
console.log('Seeding movement lineage defaults (if empty) …');
const seed = await seedDefaultsIfEmpty();
console.log(` movement lineage: inserted=${seed.inserted}${seed.skipped ? ' (skipped)' : ''}`);
} catch (err) {
console.warn(` movement lineage seed skipped: ${err.message}`);
}
console.log('Database migration complete.');
}