2026-09-12 — Convex schema parity tool

Summary

Developers and agents can compare declared Convex schemas and table data between a reference deployment and a personal/dev deployment without installing another runtime. The same Node script backs a CLI and a gated browser page.

CLI

  • From site-nextjs: pnpm convex:schema-parity

  • --data — row counts per table

  • --content — SHA-256 fingerprints of document bodies (drops _id / _creationTime; implies --data)

  • --data-only, --table NAME, --max-docs N

  • --json for agents; --shapes for declared↔inferred table presence

  • Exit 0 on parity, 1 on drift or error

  • Implementation: scripts/convex-schema-parity.mjs + scripts/lib/convex-schema-parity.mjs

Browser

  • Local next dev (and developer accounts): /dev/schema-parity

  • API: GET /api/dev/schema-parity (optional ?data=1, ?content=1, ?dataOnly=1, ?shapes=1, ?table=…)

Credentials

  • Prefer FTN_CONVEX_SCHEMA_REF_URL / FTN_CONVEX_SCHEMA_REF_KEY vs FTN_CONVEX_SCHEMA_DEV_URL / FTN_CONVEX_SCHEMA_DEV_KEY

  • Fallback: NEXT_PUBLIC_CONVEX_URL + CONVEX_DEPLOY_KEY for both sides (shared-dev era)