DR-081b — Migration-stamp discipline on the shared staging DB: allocate against the REMOTE applied set, verify by object existence, non-round stamps

Retired. This id is kept on disk so citations to it resolve and so the number can never be re-issued. It is not in force.

What it ruled: Migration-stamp discipline on the shared staging DB: allocate against the REMOTE applied set, verify by object existence, non-round stamps.

Recover the full text: git show 5c9d58d0:src/content/docs/reference/decision-register.md

Substance now lives in: canonical:supabase/CLAUDE.md

Note. The three rules: (1) allocate stamps against the remote supabase_migrations.schema_migrations, not the local dir; (2) verify by object existence (to_regclass/pg_class), never supabase migration list parity, which is version-number-blind to collisions; (3) stamps are time-anchored and non-round. When db push refuses because the remote holds a version absent locally, adopt the other lane’s migration file verbatim — never migration repair --status reverted another lane’s applied version.