2 Commits

Author SHA1 Message Date
d7bbaf483b fix: resend without an account, working --create-project preview, idempotent re-runs, closing CTA line
- resend no longer demands --to or a Scribase token (it only exports JSON)
- --create-project read --region from argv[0] when the flag was absent
- --create-project --kind preview now creates an empty schema_only env; a
  snapshot failed with source_environment_missing on a new project
- clerk --dry-run created users; neon --dry-run wrote into the real
  supabase/migrations folder
- a second neon run re-added the schema step; identical steps are reused and
  pg_dump version banners are stripped so identical dumps stay identical
- <source> --help, --version, clear errors for a missing pg_dump, a reused
  deleted environment name and a missing token (with the signup link)
- output ends with one plain line pointing at scribase.com/migrate
- README: quickstart that works today (npx from Rithub, not the unpublished
  npm name), real output sample, verified/not-verified split; add LICENSE

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-17 20:10:39 +03:00
261ea5dea7 feat: scribase-migrate — one-command migration from Supabase/Neon/Clerk/Resend onto Scribase
Composes Scribase's own shipped APIs (the `scribase` SDK's imports/migrations/
database/environments resources, plus the GoTrue admin API every self-hosted
Supabase migration tool already uses) rather than reinventing a dump format:

- supabase: wraps the real POST /v1/imports one-call migration (Postgres,
  auth.users with hashes, storage).
- neon: pg_dump schema+data as plain SQL, submitted through POST .../migrations
  (environments.connection() is internal-network-only — verified live — so
  this is the only path that actually reaches a Scribase env from outside);
  auto-generates owner-based RLS so the real migration lint's BLOCK on
  RLS-less public tables is satisfied without ever opening a table to every
  user; branches land in branch_<name> schemas.
- clerk: exports users via the real Backend API, creates them via the
  destination's GoTrue admin API with a one-time password + reset flag
  (Clerk never exposes a portable hash on any plan).
- resend: exports sending domains + broadcasts (as templates) to a portable
  JSON bundle; honest about Scribase having no write endpoint for either yet.

Verified live end-to-end against a real local Supabase-shaped Postgres
(Docker, GoTrue-shaped auth.users with a real bcrypt hash) and a real
Scribase project (ereboslab/scribase-migrate-verify-internal): schema+RLS
applied with 0 lint blocks, data row counts matched via a real HTTP query
(2/2 profiles, 3/3 notes), and a real password-grant login returned a real
access_token for the migrated user. Full artifacts in
test-fixtures/verification-run/.

docs/migrate-page.md is a ready-to-paste scribase.com/migrate page.
2026-11-17 14:54:36 +03:00