migrate-orders-to-canonical-schema

What problem does it solve?

Prevents risky, downtime-prone database changes by guiding a four-phase migration that converts Stripe-specific order columns into provider-agnostic canonical columns without breaking live application reads during the deployment window.

Core Features & Use Cases

• Four-phase safe migration workflow: add nullable canonical columns, backfill from existing Stripe columns, validate with data checks and log-based observation, then drop legacy columns.
• Canonical column mapping: moves stripe_session_id → provider_order_id, stripe_customer_id → provider_customer_id, and sets provider to 'stripe' for existing rows.
• RLS-aware checklist: ensures the related RLS review/update step is considered alongside the column rename to avoid future drift.
• Codebase audit guidance: identifies where the application still references the old column names and must be updated before legacy columns are removed.

Quick Start

Use this skill to run the 0004 migration that converts the orders table to the canonical provider-based schema while ensuring RLS policy review and safe drop timing.