create-nextblock 0.17.0 → 0.17.2

package/templates/nextblock-template/docs/TECHNICAL_SPECIFICATION.md

@@ -10,7 +10,7 @@ NextBlock CMS is an AI-Native, Open-Core Content Management System purpose-built
 
 The system's central value proposition — "Speed. Scalability. AI-Readiness (coming soon)." — is encoded directly in its architectural decisions: a Next.js 16 App Router application (`apps/nextblock`) backed by Supabase, leveraging React Server Components, edge caching, and an image-optimization pipeline targeting a default 100/100 Lighthouse Performance score. Users bootstrap new projects in under thirty seconds via the `npm create nextblock@latest` CLI, which produces a standalone, production-ready Next.js application.
 
-A live sandbox instance at `https://cms.nextblock.dev/` (accessible with demo credentials `demo@nextblock.dev` / `password`) resets daily via a cron-triggered endpoint (`/api/cron/reset-sandbox`) to provide evaluators with a clean-state environment.
+A live sandbox instance at `https://cms.nextblock.dev/` (accessible with demo credentials `demo@nextblock.dev` / `password`) resets every 15 minutes via a cron-triggered endpoint (`/api/cron/reset-sandbox`) to provide evaluators with a clean-state environment.
 
 ### 1.1.2 Core Business Problem
 
@@ -27,7 +27,7 @@ The core problem statement — "stop cloning heavy repos; start with our CLI and
 
 ### 1.1.3 Key Stakeholders and Users
 
-The system recognizes three database-enforced user roles (defined as the `user_role` enum `ADMIN`, `WRITER`, `USER` in migration `00000000000000_setup_foundation_and_enums.sql`) and three additional implicit stakeholder classes observable from the scaffolding and documentation artifacts.
+The system recognizes three database-enforced user roles (defined as the `user_role` enum `ADMIN`, `WRITER`, `USER` in migration `02001_baseline_schema.sql`) and three additional implicit stakeholder classes observable from the scaffolding and documentation artifacts.
 
 | Stakeholder | Role / Audience | Primary Entry Point |
 |:--|:--|:--|
@@ -247,7 +247,7 @@ The following architectural invariants are enforced at workspace level and must
 | Media Optimization | Blur placeholders generated for uploaded images | `sharp` + `plaiceholder` pipeline |
 | Developer Adoption | CLI install success rate | `apps/create-nextblock/bin/create-nextblock.js` |
 | Commerce Conversion | Checkout success by provider (Stripe / Freemius) | `app/api/checkout/route.ts` + webhooks |
-| Scheduled Job Health | Daily success of reset-sandbox and sync-currencies | `vercel.json` cron configuration |
+| Scheduled Job Health | Success of reset-sandbox (every 15 min) and sync-currencies (daily) | `vercel.json` cron configuration |
 | Bundle Discipline | Removed console calls in production | `compiler.removeConsole` in `next.config.js` |
 
 ---
@@ -267,7 +267,7 @@ The following architectural invariants are enforced at workspace level and must
 
 **Editor Capabilities** — The `@nextblock-cms/editor` library exports `Editor`, `NotionEditor`, `EditorToolbar`, `EditorBubbleMenu`, `EditorFloatingMenu`, `EnhancedFloatingMenu`, `SlashCommandList`, `DragHandle`, `HtmlContent`, and `editorExtensions`. Feature set includes Tiptap StarterKit rich text, syntax-highlighted code blocks, tables, task lists, slash commands, drag handles, image handling, character counting, typography, mathematics, emoji, mentions, inline alert and call-to-action widgets, and custom HTML-preserving extensions for `div`, `style`, `script`, `svg`, `span`, and catch-all attribute preservation. A media-picker bridge is exposed via `setOpenImagePicker()`.
 
-**Translation & Localization** — The set of served locales is the active rows of the `languages` table (managed at `/cms/settings/languages`; the proxy reads them with a 60-second in-memory cache and only falls back to the hardcoded `FALLBACK_LOCALES` `en`/`fr` when the DB is unreadable), backed by `languages` and `translations` tables from migration `00000000000001_setup_cms_core.sql`. First-visit language detection is admin-configurable (see F-007): browser `Accept-Language`, IP-country via host geo headers, combined, or always-default — implemented in `apps/nextblock/lib/i18n/detection.ts` and stored in `site_settings.language_detection_settings`. Content revision history is stored as snapshot + JSON Patch diff (enum `revision_type: snapshot, diff`) per migration `00000000000002_setup_content_tables.sql`.
+**Translation & Localization** — The set of served locales is the active rows of the `languages` table (managed at `/cms/settings/languages`; the proxy reads them with a 60-second in-memory cache and only falls back to the hardcoded `FALLBACK_LOCALES` `en`/`fr` when the DB is unreadable), backed by `languages` and `translations` tables from migration `02001_baseline_schema.sql`. First-visit language detection is admin-configurable (see F-007): browser `Accept-Language`, IP-country via host geo headers, combined, or always-default — implemented in `apps/nextblock/lib/i18n/detection.ts` and stored in `site_settings.language_detection_settings`. Content revision history is stored as snapshot + JSON Patch diff (enum `revision_type: snapshot, diff`) per migration `02001_baseline_schema.sql`.
 
 **Page Lifecycle** — Pages move through `draft`, `published`, and `archived` statuses (enum `page_status`).
 
@@ -343,7 +343,7 @@ Profile completion is enforced via a redirect: users without a `full_name` value
 
 #### 1.3.2.3 Geographic and Market Coverage
 
-Shipping resolution operates at country and state granularity. Multi-currency pricing is supported with a configurable default currency seeded in migration `00000000000008_seed_platform_defaults.sql`. The database schema includes a `shipping_zone_locations.postal_code` column for future finer-grained geographic resolution, although the current runtime resolver does not yet consume it.
+Shipping resolution operates at country and state granularity. Multi-currency pricing is supported with a configurable default currency seeded in migration `02001_baseline_schema.sql`. The database schema includes a `shipping_zone_locations.postal_code` column for future finer-grained geographic resolution, although the current runtime resolver does not yet consume it.
 
 #### 1.3.2.4 Data Domains Included
 
@@ -403,7 +403,7 @@ The system does not natively integrate with: alternative payment processors beyo
 - `tsconfig.base.json` — Shared TypeScript strict-mode configuration and `@nextblock-cms/*` path aliases
 - `components.json` — shadcn/ui configuration (Slate base, CSS variables, RSC)
 - `tailwind.config.js` — Root Tailwind CSS theme tokens and dark-mode configuration
-- `vercel.json` — Cron schedule definitions (reset-sandbox at 03:00 UTC, sync-currencies at 18:00 UTC)
+- `vercel.json` — Cron schedule definitions (reset-sandbox every 15 minutes, sync-currencies at 18:00 UTC)
 - `.env.example` — Environment variable reference template
 
 ### 1.4.2 Documentation Hub (`docs/`)
@@ -446,11 +446,14 @@ The system does not natively integrate with: alternative payment processors beyo
 
 ### 1.4.5 Database Migrations
 
-- `libs/db/src/supabase/migrations/00000000000000_setup_foundation_and_enums.sql` — Enums: `user_role`, `page_status`, `menu_location`, `revision_type`
-- `libs/db/src/supabase/migrations/00000000000001_setup_cms_core.sql` — Languages, translations, media, profiles, settings
-- `libs/db/src/supabase/migrations/00000000000002_setup_content_tables.sql` — Pages, posts, blocks, navigation, revisions
-- `libs/db/src/supabase/migrations/00000000000008_seed_platform_defaults.sql` — Default settings (footer copyright, payment providers, inventory, invoice settings)
-- Migrations 00000000000003 through 00000000000010 — Commerce catalog, fulfillment, and platform seeds
+One squash generation at a time (`GGNNN_name.sql`; see §6.2.3.1 and docs/04):
+
+- `libs/db/src/supabase/migrations/02000_catchup_gen1.sql` — Version-aware replay of the retired generation-1 forward migrations
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — Enums (`user_role`, `page_status`, `menu_location`, `revision_type`, …), functions, every table and sequence
+- `libs/db/src/supabase/migrations/02002_baseline_constraints_and_indexes.sql` — Constraints and indexes
+- `libs/db/src/supabase/migrations/02003_baseline_security_and_grants.sql` — RLS, policies, triggers, grants
+- `libs/db/src/supabase/migrations/02004_baseline_seed.sql` — Default settings (footer copyright, payment providers, inventory, invoice settings), languages, translations, demo content
+- `02005` onward — forward migrations appended since the generation-2 squash
 
 ### 1.4.6 Agent Skill Documents
 
@@ -623,7 +626,7 @@ Served locales are the active rows of the `languages` table, managed at `/cms/se
 
 Locale propagation uses the `NEXT_USER_LOCALE` cookie and the `X-User-Locale` request header, both set by the request proxy. When `rememberVisitorChoice` is `true` (default) the cookie persists for one year (`maxAge: 31_536_000` seconds); when `false` it is a session cookie, so detection re-runs each new browser session (the client `LanguageProvider` mirrors the same expiry for manual switcher choices). A valid cookie always beats detection. The client-side provider chain `LanguageProvider → TranslationsProvider` in `apps/nextblock/app/providers.tsx` bridges server-resolved locale into React context.
 
-**Business Value:** Unlocks multi-market deployments without requiring adopters to integrate a separate i18n library. **User Benefits:** Language switching persists across sessions; same content IDs preserve relationships across translations. **Technical Context:** Implemented at schema level (migration `00000000000001_setup_cms_core.sql`), proxy level, and provider level.
+**Business Value:** Unlocks multi-market deployments without requiring adopters to integrate a separate i18n library. **User Benefits:** Language switching persists across sessions; same content IDs preserve relationships across translations. **Technical Context:** Implemented at schema level (migration `02001_baseline_schema.sql`), proxy level, and provider level.
 
 **Dependencies**
 
@@ -648,7 +651,7 @@ Locale propagation uses the `NEXT_USER_LOCALE` cookie and the `X-User-Locale` re
 
 **Description**
 
-Revisions are implemented in the `page_revisions` and `post_revisions` tables defined in migration `00000000000002_setup_content_tables.sql`, using a hybrid snapshot/diff model. The `revision_type` enum (`snapshot`, `diff`) distinguishes between full snapshots and JSON Patch diffs (generated via `fast-json-patch`). A UNIQUE constraint on `(page_id, version)` ensures monotonically increasing snapshot versions. The CMS surface resides under `apps/nextblock/app/cms/revisions/`.
+Revisions are implemented in the `page_revisions` and `post_revisions` tables defined in migration `02001_baseline_schema.sql`, using a hybrid snapshot/diff model. The `revision_type` enum (`snapshot`, `diff`) distinguishes between full snapshots and JSON Patch diffs (generated via `fast-json-patch`). A UNIQUE constraint on `(page_id, version)` ensures monotonically increasing snapshot versions. The CMS surface resides under `apps/nextblock/app/cms/revisions/`.
 
 **Business Value:** Provides audit trail and rollback capability for authored content. **User Benefits:** Authors can restore prior states; accidental deletions are recoverable. **Technical Context:** Diff generation reduces storage overhead for frequently-updated content.
 
@@ -675,7 +678,7 @@ Revisions are implemented in the `page_revisions` and `post_revisions` tables de
 
 **Description**
 
-Three menu locations are supported: `HEADER`, `FOOTER`, and `SIDEBAR`, encoded by the `menu_location` enum. The `navigation_items` table (migration `00000000000002_setup_content_tables.sql`) supports hierarchical menus through a `parent_id` self-reference, explicit `order` for sibling sorting, translation group affiliation, and optional page references. Administrative CRUD operations reside at `apps/nextblock/app/cms/navigation/`.
+Three menu locations are supported: `HEADER`, `FOOTER`, and `SIDEBAR`, encoded by the `menu_location` enum. The `navigation_items` table (migration `02001_baseline_schema.sql`) supports hierarchical menus through a `parent_id` self-reference, explicit `order` for sibling sorting, translation group affiliation, and optional page references. Administrative CRUD operations reside at `apps/nextblock/app/cms/navigation/`.
 
 **Dependencies**
 
@@ -729,7 +732,7 @@ Authentication is layered over Supabase Auth using `@supabase/ssr` and `@supabas
 
 **Description**
 
-RBAC is enforced through a three-valued `user_role` enum (`ADMIN`, `WRITER`, `USER`) defined in migration `00000000000000_setup_foundation_and_enums.sql`. Route-level enforcement is implemented in `apps/nextblock/proxy.ts` (lines 12–17): `/cms` requires `WRITER` or `ADMIN`; `/cms/admin`, `/cms/users`, and `/cms/settings` require `ADMIN` exclusively. A foundational authorization rule encoded in the `on_auth_user_created` trigger elevates the first registered user to `ADMIN` and assigns all subsequent users the `USER` role, guaranteeing each deployment has exactly one guaranteed administrator at bootstrap. Users without a `full_name` value are redirected to `/profile` before being permitted to access other authenticated surfaces. Database-layer enforcement is provided via Row-Level Security with helper functions `get_current_user_role()` and `is_admin()` (both `SECURITY DEFINER`).
+RBAC is enforced through a three-valued `user_role` enum (`ADMIN`, `WRITER`, `USER`) defined in migration `02001_baseline_schema.sql`. Route-level enforcement is implemented in `apps/nextblock/proxy.ts` (lines 12–17): `/cms` requires `WRITER` or `ADMIN`; `/cms/admin`, `/cms/users`, and `/cms/settings` require `ADMIN` exclusively. A foundational authorization rule encoded in the `on_auth_user_created` trigger elevates the first registered user to `ADMIN` and assigns all subsequent users the `USER` role, guaranteeing each deployment has exactly one guaranteed administrator at bootstrap. Users without a `full_name` value are redirected to `/profile` before being permitted to access other authenticated surfaces. Database-layer enforcement is provided via Row-Level Security with helper functions `get_current_user_role()` and `is_admin()` (both `SECURITY DEFINER`).
 
 **Dependencies**
 
@@ -833,7 +836,7 @@ All features in this section are gated by F-022 (Package Activation) via `verify
 
 **Description**
 
-Products are modeled in migration `00000000000003_setup_catalog_and_licensing.sql` with fields including `sku`, `slug`, `title`, `type` (`physical` | `digital`), `payment_provider` (`stripe` | `freemius`), `price` as an integer in the smallest currency unit, a multi-currency `prices` JSONB column, `stock`, `status` (`draft` | `active` | `archived`), descriptions, Freemius-specific fields, UPC, and an `is_taxable` flag. A CHECK constraint named `products_type_provider_consistency_check` enforces that `physical` products use `stripe` and `digital` products use `freemius`. Related tables `product_media`, `product_attributes`, `product_attribute_terms`, `product_variants`, and `variant_attribute_mapping` model assets and variations. CMS surfaces at `apps/nextblock/app/cms/products/` provide list, create, edit, media, attribute, and variation management flows.
+Products are modeled in migration `02001_baseline_schema.sql` with fields including `sku`, `slug`, `title`, `type` (`physical` | `digital`), `payment_provider` (`stripe` | `freemius`), `price` as an integer in the smallest currency unit, a multi-currency `prices` JSONB column, `stock`, `status` (`draft` | `active` | `archived`), descriptions, Freemius-specific fields, UPC, and an `is_taxable` flag. A CHECK constraint named `products_type_provider_consistency_check` enforces that `physical` products use `stripe` and `digital` products use `freemius`. Related tables `product_media`, `product_attributes`, `product_attribute_terms`, `product_variants`, and `variant_attribute_mapping` model assets and variations. CMS surfaces at `apps/nextblock/app/cms/products/` provide list, create, edit, media, attribute, and variation management flows.
 
 **Dependencies**
 
@@ -858,7 +861,7 @@ Products are modeled in migration `00000000000003_setup_catalog_and_licensing.sq
 
 **Description**
 
-The `inventory_items` table (migration `00000000000003_setup_catalog_and_licensing.sql`) uses SKU as key and enforces `quantity >= 0` via CHECK constraint. Tracking is globally controlled by the `trackQuantities` setting in `ecommerce_inventory_settings`. Inventory deduction during order finalization follows a resilient pattern: the runtime first calls the `apply_order_inventory_deduction()` Postgres RPC, and if that path is unavailable, falls back to direct SQL via the `POSTGRES_URL` or `DATABASE_URL` connection, as coordinated by `libs/ecommerce/src/lib/shared-inventory.ts` and `libs/ecommerce/src/lib/order-inventory.ts`.
+The `inventory_items` table (migration `02001_baseline_schema.sql`) uses SKU as key and enforces `quantity >= 0` via CHECK constraint. Tracking is globally controlled by the `trackQuantities` setting in `ecommerce_inventory_settings`. Inventory deduction during order finalization follows a resilient pattern: the runtime first calls the `apply_order_inventory_deduction()` Postgres RPC, and if that path is unavailable, falls back to direct SQL via the `POSTGRES_URL` or `DATABASE_URL` connection, as coordinated by `libs/ecommerce/src/lib/shared-inventory.ts` and `libs/ecommerce/src/lib/order-inventory.ts`.
 
 **Dependencies**
 
@@ -958,7 +961,7 @@ Freemius integration lives in `libs/ecommerce/src/lib/providers/` and supports d
 
 **Description**
 
-The `currencies` table (migration `00000000000004_setup_fulfillment_shipping_taxes_and_currencies.sql`) stores `exchange_rate` as a `numeric(20,10)`, a single-row `is_default` constraint, `rounding_mode` (`none`, `nearest`, `up`, `down`, `charm`), `rounding_increment`, `rounding_charm_amount`, and flags `auto_update_exchange_rate` and `auto_sync_product_prices`. The default currency must satisfy `exchange_rate = 1`, `auto_update_exchange_rate = false`, and `auto_sync_product_prices = false`. FX rates are pulled from `https://api.frankfurter.dev` (overridable via `FX_API_BASE_URL`). Operations `syncStoreCurrencyRates()` and `rebaseStoreCurrencyExchangeRates()` are exposed by `libs/ecommerce/src/lib/currency-sync.ts`. A daily cron invokes `/api/cron/sync-currencies` at 18:00 UTC (`vercel.json`). Seed migration `00000000000008_seed_platform_defaults.sql` provides USD as the default.
+The `currencies` table (migration `02001_baseline_schema.sql`) stores `exchange_rate` as a `numeric(20,10)`, a single-row `is_default` constraint, `rounding_mode` (`none`, `nearest`, `up`, `down`, `charm`), `rounding_increment`, `rounding_charm_amount`, and flags `auto_update_exchange_rate` and `auto_sync_product_prices`. The default currency must satisfy `exchange_rate = 1`, `auto_update_exchange_rate = false`, and `auto_sync_product_prices = false`. FX rates are pulled from `https://api.frankfurter.dev` (overridable via `FX_API_BASE_URL`). Operations `syncStoreCurrencyRates()` and `rebaseStoreCurrencyExchangeRates()` are exposed by `libs/ecommerce/src/lib/currency-sync.ts`. A daily cron invokes `/api/cron/sync-currencies` at 18:00 UTC (`vercel.json`). Seed migration `02001_baseline_schema.sql` provides USD as the default.
 
 **Dependencies**
 
@@ -1008,7 +1011,7 @@ Three shipping tables model geographic and rate configurations: `shipping_zones`
 
 **Description**
 
-The `tax_rates` table (migration `00000000000004_setup_fulfillment_shipping_taxes_and_currencies.sql`) supports two modes: `manual` (keyed on country and state, supporting stacked rates such as GST + PST) and `automatic` (delegated to Stripe Tax via tax codes on line items). Mode selection is controlled by the `enableTaxes` and `taxCalculationMode` properties in `ecommerce_inventory_settings`. Schema constraints require `tax_rate` between 0 and 100 and enforce a uniqueness constraint on `(country_code, state_code, lower(tax_name))`. Implementation lives in `libs/ecommerce/src/lib/tax-calculation.ts` and `libs/ecommerce/src/lib/order-tax-details.ts`.
+The `tax_rates` table (migration `02001_baseline_schema.sql`) supports two modes: `manual` (keyed on country and state, supporting stacked rates such as GST + PST) and `automatic` (delegated to Stripe Tax via tax codes on line items). Mode selection is controlled by the `enableTaxes` and `taxCalculationMode` properties in `ecommerce_inventory_settings`. Schema constraints require `tax_rate` between 0 and 100 and enforce a uniqueness constraint on `(country_code, state_code, lower(tax_name))`. Implementation lives in `libs/ecommerce/src/lib/tax-calculation.ts` and `libs/ecommerce/src/lib/order-tax-details.ts`.
 
 **Dependencies**
 
@@ -1033,7 +1036,7 @@ The `tax_rates` table (migration `00000000000004_setup_fulfillment_shipping_taxe
 
 **Description**
 
-Orders transition through five statuses — `pending`, `paid`, `shipped`, `cancelled`, `refunded` — and store totals (`total`, `subtotal`, `shipping_total`, `tax_total`), a JSONB `tax_details` breakdown, `exchange_rate_at_purchase` as `numeric(20,10)`, `invoice_number`, `paid_at`, and `inventory_deducted_at`. Stable invoice numbering is produced by the `order_invoice_number_seq` sequence. The `invoice_settings` site-setting (seeded by `00000000000008_seed_platform_defaults.sql`) stores business name, email, address, and tax registrations. UI components `InvoiceDocument` and `InvoiceViewerShell` in `libs/ecommerce/src/lib/` render invoices. Customer order history is surfaced via `libs/ecommerce/src/lib/customer-orders.ts`, with admin management at `apps/nextblock/app/cms/orders/` and customer self-service at `apps/nextblock/app/profile/orders/`.
+Orders transition through five statuses — `pending`, `paid`, `shipped`, `cancelled`, `refunded` — and store totals (`total`, `subtotal`, `shipping_total`, `tax_total`), a JSONB `tax_details` breakdown, `exchange_rate_at_purchase` as `numeric(20,10)`, `invoice_number`, `paid_at`, and `inventory_deducted_at`. Stable invoice numbering is produced by the `order_invoice_number_seq` sequence. The `invoice_settings` site-setting (seeded by `02001_baseline_schema.sql`) stores business name, email, address, and tax registrations. UI components `InvoiceDocument` and `InvoiceViewerShell` in `libs/ecommerce/src/lib/` render invoices. Customer order history is surfaced via `libs/ecommerce/src/lib/customer-orders.ts`, with admin management at `apps/nextblock/app/cms/orders/` and customer self-service at `apps/nextblock/app/profile/orders/`.
 
 **Dependencies**
 
@@ -1058,7 +1061,7 @@ Orders transition through five statuses — `pending`, `paid`, `shipped`, `cance
 
 **Description**
 
-The `package_activations` table (migration `00000000000003_setup_catalog_and_licensing.sql`) contains `license_key`, `instance_name`, `package_id`, `status` (defaulting to `active`), `meta`, `last_validated_at`, and a UNIQUE constraint on `(license_key, package_id)`. The helper `verifyPackageOnline(packageId, customClient?)` in `libs/db/src/lib/package-validation.ts` returns a boolean based on `status === 'active'` and uses `unstable_cache` with a 60-second revalidation window. This function is invoked from four surfaces: the CMS commerce navigation visibility check, the checkout API gate at `apps/nextblock/app/api/checkout/route.ts` line 36, premium route wrappers injected during scaffold activation, and the CLI's module activation flows.
+The `package_activations` table (migration `02001_baseline_schema.sql`) contains `license_key`, `instance_name`, `package_id`, `status` (defaulting to `active`), `meta`, `last_validated_at`, and a UNIQUE constraint on `(license_key, package_id)`. The helper `verifyPackageOnline(packageId, customClient?)` in `libs/db/src/lib/package-validation.ts` returns a boolean based on `status === 'active'` and uses `unstable_cache` with a 60-second revalidation window. This function is invoked from four surfaces: the CMS commerce navigation visibility check, the checkout API gate at `apps/nextblock/app/api/checkout/route.ts` line 36, premium route wrappers injected during scaffold activation, and the CLI's module activation flows.
 
 **Dependencies**
 
@@ -1160,7 +1163,7 @@ The SDK library at `libs/sdk` provides a typed contract for external block autho
 
 **Description**
 
-Two cron jobs are declared in `vercel.json`. The `/api/cron/reset-sandbox` endpoint runs daily at 03:00 UTC (`0 3 * * *`); it clears R2 storage, executes the generated SQL bootstrap (`SANDBOX_RESET_SQL`), normalizes media records, ensures required assets, seeds commerce and content data, and synchronizes Freemius products (product ID `24851`). The `/api/cron/sync-currencies` endpoint runs daily at 18:00 UTC (`0 18 * * *`) and invokes `syncStoreCurrencyRates()` from `@nextblock-cms/ecommerce/server`. Both endpoints require an `Authorization: Bearer ${CRON_SECRET}` header.
+Two cron jobs are declared in `vercel.json`. The `/api/cron/reset-sandbox` endpoint runs every 15 minutes (`*/15 * * * *`); it clears R2 storage, executes the generated SQL bootstrap (`SANDBOX_RESET_SQL`), normalizes media records, ensures required assets, seeds commerce and content data, and synchronizes Freemius products (product ID `24851`). The `/api/cron/sync-currencies` endpoint runs daily at 18:00 UTC (`0 18 * * *`) and invokes `syncStoreCurrencyRates()` from `@nextblock-cms/ecommerce/server`. Both endpoints require an `Authorization: Bearer ${CRON_SECRET}` header.
 
 **Dependencies**
 
@@ -1185,13 +1188,13 @@ Two cron jobs are declared in `vercel.json`. The `/api/cron/reset-sandbox` endpo
 
 **Description**
 
-Sandbox mode is toggled via the `NEXT_PUBLIC_IS_SANDBOX` environment variable. When enabled, the application renders the `SandboxBanner` and `SandboxCredentialsAlert` components (with demo credentials `demo@nextblock.dev`/`password`), and relaxes Freemius webhook signature verification to tolerate signature mismatches. A live deployment at `https://cms.nextblock.dev/` demonstrates the feature and resets daily via F-025.
+Sandbox mode is toggled via the `NEXT_PUBLIC_IS_SANDBOX` environment variable. When enabled, the application renders the `SandboxBanner` and `SandboxCredentialsAlert` components (with demo credentials `demo@nextblock.dev`/`password`), and relaxes Freemius webhook signature verification to tolerate signature mismatches. A live deployment at `https://cms.nextblock.dev/` demonstrates the feature and resets every 15 minutes via F-025.
 
 **Dependencies**
 
 | Dependency Type | Details |
 |:--|:--|
-| Prerequisite Features | F-025 (for daily reset) |
+| Prerequisite Features | F-025 (for the 15-minute reset) |
 | System Dependencies | None |
 | External Dependencies | None |
 | Integration Requirements | `NEXT_PUBLIC_IS_SANDBOX` flag |
@@ -1422,7 +1425,7 @@ This subsection provides the detailed, testable requirements that operationalize
 | F-023-RQ-002 | `activate ecommerce` MUST install the alias `@nextblock-cms/ecommerce@npm:@nextblock-cms/ecom@latest` and inject route wrappers with `verifyPackageOnline()` | Must-Have | High |
 | F-024-RQ-001 | SDK MUST expose `BlockContentSchema`, `BlockData`, `BlockProps`, `BlockEditorProps`, `BlockConfig`, `LucideIcon` | Must-Have | Low |
 | F-024-RQ-002 | External block authoring MUST follow the contract shape documented in `docs/07-BLOCK-SDK-AND-EXTENSIBILITY.md` | Must-Have | Medium |
-| F-025-RQ-001 | `/api/cron/reset-sandbox` MUST run daily at 03:00 UTC with `Bearer CRON_SECRET` authorization | Must-Have | Medium |
+| F-025-RQ-001 | `/api/cron/reset-sandbox` MUST run every 15 minutes with `Bearer CRON_SECRET` authorization | Must-Have | Medium |
 | F-025-RQ-002 | `/api/cron/sync-currencies` MUST run daily at 18:00 UTC with `Bearer CRON_SECRET` authorization | Must-Have | Low |
 | F-026-RQ-001 | Sandbox banner and credential alert MUST render when `NEXT_PUBLIC_IS_SANDBOX === 'true'` | Should-Have | Low |
 | F-027-RQ-001 | `/api/revalidate` MUST validate `REVALIDATE_SECRET_TOKEN` before calling `revalidatePath` | Must-Have | Medium |
@@ -1679,7 +1682,7 @@ The following matrix links features to the sections of the technical specificati
 | Package alignment | `@nextblock-cms/ecom` package name vs. `@nextblock-cms/ecommerce` alias (per §1.3.3.1) requires coordination when republished | F-013–F-022 |
 | Locale expansion | Locales are DB-driven: add an active `languages` row (plus translations/content); `FALLBACK_LOCALES` in `proxy.ts` is only a DB-unreachable safety net | F-007 |
 | Block registry updates | New block types must satisfy F-024 contract and register in `blockRegistry.ts` | F-004, F-024 |
-| RLS policy review | Migration `00000000000006_setup_rls_and_grants.sql` should be audited on new table introduction | All DB-backed features |
+| RLS policy review | Migration `02001_baseline_schema.sql` should be audited on new table introduction | All DB-backed features |
 
 ### 2.4.6 Assumptions and Constraints Summary
 
@@ -1700,7 +1703,7 @@ The following matrix links features to the sections of the technical specificati
 - `README.md` — Product value proposition, competitive positioning, Lighthouse and CLI claims
 - `package.json` — Workspace dependency versions (Next.js, React, TypeScript, Nx, Tailwind, Tiptap)
 - `nx.json` — Nx plugin and release configuration
-- `vercel.json` — Cron schedule definitions (reset-sandbox 03:00 UTC; sync-currencies 18:00 UTC)
+- `vercel.json` — Cron schedule definitions (reset-sandbox every 15 minutes; sync-currencies 18:00 UTC)
 - `.env.example` — Environment variable reference template
 - `eslint.config.mjs` — `@nx/enforce-module-boundaries` scope-tag rules (F-028)
 - `apps/nextblock/next.config.js` — Image format/device-size config; CSP; `transpilePackages`
@@ -1726,14 +1729,14 @@ The following matrix links features to the sections of the technical specificati
 - `apps/create-nextblock/bin/create-nextblock.js` — CLI `create` and `activate` commands (F-023)
 - `libs/db/src/lib/package-validation.ts` — `verifyPackageOnline()` with 60 s cache (F-022)
 - `libs/db/src/lib/media-actions.ts` — Role-gated media recording (F-006)
-- `libs/db/src/supabase/migrations/00000000000000_setup_foundation_and_enums.sql` — `user_role`, `page_status`, `menu_location`, `revision_type` enums
-- `libs/db/src/supabase/migrations/00000000000001_setup_cms_core.sql` — languages, translations, media, profiles (F-002, F-006, F-007)
-- `libs/db/src/supabase/migrations/00000000000002_setup_content_tables.sql` — pages, posts, blocks, navigation, revisions (F-004, F-008, F-009)
-- `libs/db/src/supabase/migrations/00000000000003_setup_catalog_and_licensing.sql` — products, variants, attributes, inventory, package_activations (F-013, F-014, F-022)
-- `libs/db/src/supabase/migrations/00000000000004_setup_fulfillment_shipping_taxes_and_currencies.sql` — orders, shipping zones, tax rates, currencies (F-018–F-021)
-- `libs/db/src/supabase/migrations/00000000000005_setup_functions_and_triggers.sql` — `handle_new_user()`, `on_auth_user_created` (F-002, F-003)
-- `libs/db/src/supabase/migrations/00000000000006_setup_rls_and_grants.sql` — RLS policies and helper functions
-- `libs/db/src/supabase/migrations/00000000000008_seed_platform_defaults.sql` — Default settings, USD currency, `en`/`fr` languages
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — `user_role`, `page_status`, `menu_location`, `revision_type` enums
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — languages, translations, media, profiles (F-002, F-006, F-007)
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — pages, posts, blocks, navigation, revisions (F-004, F-008, F-009)
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — products, variants, attributes, inventory, package_activations (F-013, F-014, F-022)
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — orders, shipping zones, tax rates, currencies (F-018–F-021)
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — `handle_new_user()`, `on_auth_user_created` (F-002, F-003)
+- `libs/db/src/supabase/migrations/02003_baseline_security_and_grants.sql` — RLS policies and helper functions
+- `libs/db/src/supabase/migrations/02004_baseline_seed.sql` — Default settings, USD currency, `en`/`fr` languages
 - `libs/db/src/supabase/templates/` — Six Supabase Auth email templates (F-002)
 - `libs/editor/README.md` — Public editor surface exports (F-005)
 - `libs/editor/ADVANCED_FEATURES.md` — Enhanced floating menu, placeholder behaviors (F-005)
@@ -2203,7 +2206,7 @@ The `vercel.json` file declares two scheduled jobs:
 
 | Path | Schedule (UTC) | Purpose |
 |:--|:--|:--|
-| `/api/cron/reset-sandbox` | `0 3 * * *` (03:00 daily) | Resets sandbox R2 + data for the demo deployment (F-025, F-026) |
+| `/api/cron/reset-sandbox` | `*/15 * * * *` (every 15 minutes) | Resets sandbox R2 + data for the demo deployment (F-025, F-026) |
 | `/api/cron/sync-currencies` | `0 18 * * *` (18:00 daily) | FX rate synchronization (F-018, F-025) |
 
 Both endpoints enforce `Authorization: Bearer ${CRON_SECRET}` per the security mitigation in Section 2.4.4.
@@ -2222,14 +2225,14 @@ Supabase PostgreSQL is the authoritative data store for all structured data in t
 
 | Migration File | Purpose |
 |:--|:--|
-| `00000000000000_setup_foundation_and_enums.sql` | Enums: `user_role`, `page_status`, `menu_location`, `revision_type` |
-| `00000000000001_setup_cms_core.sql` | `languages`, `translations`, `media`, `profiles`, `settings`, `logos` |
-| `00000000000002_setup_content_tables.sql` | `pages`, `posts`, `blocks`, `navigation_items`, `page_revisions`, `post_revisions` |
-| `00000000000003_setup_catalog_and_licensing.sql` | `products`, `product_variants`, `inventory_items`, `package_activations` |
-| `00000000000004_setup_fulfillment_shipping_taxes_and_currencies.sql` | `currencies`, `tax_rates`, shipping tables |
+| `02001_baseline_schema.sql` | Enums: `user_role`, `page_status`, `menu_location`, `revision_type` |
+| `02001_baseline_schema.sql` | `languages`, `translations`, `media`, `profiles`, `settings`, `logos` |
+| `02001_baseline_schema.sql` | `pages`, `posts`, `blocks`, `navigation_items`, `page_revisions`, `post_revisions` |
+| `02001_baseline_schema.sql` | `products`, `product_variants`, `inventory_items`, `package_activations` |
+| `02001_baseline_schema.sql` | `currencies`, `tax_rates`, shipping tables |
 | `00000000000005` through `00000000000007` | Commerce extensions |
-| `00000000000006_setup_rls_and_grants.sql` | Row-Level Security policies |
-| `00000000000008_seed_platform_defaults.sql` | Default settings, USD currency, English language |
+| `02001_baseline_schema.sql` | Row-Level Security policies |
+| `02001_baseline_schema.sql` | Default settings, USD currency, English language |
 | `00000000000009` — `00000000000010` | Additional platform seeds |
 | `00000000000011` through `00000000000016` | Cortex AI settings, coupons, audit, drafts, and page feature images |
 | `00000000000017` through `00000000000024` | Product blocks, bot-protection settings, product categories + translations, hero→section migration, Cortex AI guide seed, custom block definitions, and cart sessions |
@@ -2521,7 +2524,7 @@ The premium `libs/ecommerce` is guarded at runtime by the `verifyPackageOnline('
 - `package.json` — Root workspace package metadata, all dependency versions, and npm scripts
 - `nx.json` — Nx workspace configuration, registered plugins, generators, and targets
 - `tsconfig.base.json` — Shared TypeScript strict-mode configuration and monorepo path aliases
-- `vercel.json` — Cron schedules for `reset-sandbox` (03:00 UTC) and `sync-currencies` (18:00 UTC)
+- `vercel.json` — Cron schedules for `reset-sandbox` (every 15 minutes) and `sync-currencies` (18:00 UTC)
 - `tailwind.config.js` — Root Tailwind CSS theme tokens, dark-mode configuration, content globs
 - `postcss.config.js` — PostCSS pipeline with `@tailwindcss/postcss` and `autoprefixer`
 - `eslint.config.mjs` — Flat ESLint configuration with `@nx/enforce-module-boundaries` rules
@@ -3432,7 +3435,7 @@ flowchart LR
 
 ### 4.5.1 Sandbox Reset Cron
 
-The sandbox reset cron at `/api/cron/reset-sandbox/` executes daily at 03:00 UTC and performs a comprehensive environment rebuild: R2 storage deletion and re-seeding, database bootstrap via generated `SANDBOX_RESET_SQL`, and seeding of commerce products, localized content, and navigation entries. The endpoint requires `NEXT_PUBLIC_IS_SANDBOX === 'true'` and rejects execution in production environments.
+The sandbox reset cron at `/api/cron/reset-sandbox/` executes every 15 minutes and performs a comprehensive environment rebuild: R2 storage deletion and re-seeding, database bootstrap via generated `SANDBOX_RESET_SQL`, and seeding of commerce products, localized content, and navigation entries. The endpoint requires `NEXT_PUBLIC_IS_SANDBOX === 'true'` and rejects execution in production environments.
 
 ```mermaid
 flowchart TB
@@ -3923,7 +3926,7 @@ The following table consolidates all documented timing constraints and SLAs acro
 | Sync-Currencies maxDuration | 30 seconds | `api/cron/sync-currencies` |
 | Reset-Sandbox maxDuration | 60 seconds | `api/cron/reset-sandbox` |
 | Currency Sync Schedule | 18:00 UTC daily (`0 18 * * *`) | `vercel.json` |
-| Sandbox Reset Schedule | 03:00 UTC daily (`0 3 * * *`) | `vercel.json` |
+| Sandbox Reset Schedule | every 15 minutes (`*/15 * * * *`) | `vercel.json` |
 | Max Source Image Width | 2560 pixels | `api/process-image` |
 | Image Derivative Widths | 1920, 1280, 768, 384, 128 | `api/process-image` |
 | Lighthouse Performance Target | 100/100 | `README.md` |
@@ -3953,9 +3956,9 @@ flowchart LR
         HstsHeader[HSTS Header<br/>2 years max-age]
     end
     
-    subgraph Scheduled[" Scheduled Daily "]
+    subgraph Scheduled[" Scheduled (Vercel Cron) "]
         CurrencyDay[18:00 UTC<br/>Sync Currencies]
-        ResetDay[03:00 UTC<br/>Sandbox Reset]
+        ResetDay[Every 15 min<br/>Sandbox Reset]
     end
 ```
 
@@ -4002,14 +4005,14 @@ flowchart LR
 
 #### Database Migrations Referenced
 
-- `00000000000000_setup_foundation_and_enums.sql` - `user_role` enum
-- `00000000000001_setup_cms_core.sql` - Translations schema
-- `00000000000002_setup_content_tables.sql` - Pages, posts, revisions, navigation
-- `00000000000003_setup_catalog_and_licensing.sql` - Products, inventory, package_activations
-- `00000000000004_setup_fulfillment_shipping_taxes_and_currencies.sql` - Orders, tax, shipping, currencies
-- `00000000000005_*.sql` - `on_auth_user_created` trigger (first-user ADMIN rule)
-- `00000000000006_*.sql` - RLS policies and helper functions
-- `00000000000008_seed_platform_defaults.sql` - Default currency, languages, invoice settings
+- `02001_baseline_schema.sql` - `user_role` enum
+- `02001_baseline_schema.sql` - Translations schema
+- `02001_baseline_schema.sql` - Pages, posts, revisions, navigation
+- `02001_baseline_schema.sql` - Products, inventory, package_activations
+- `02001_baseline_schema.sql` - Orders, tax, shipping, currencies
+- `02003_baseline_security_and_grants.sql` - `on_auth_user_created` trigger (first-user ADMIN rule), RLS policies
+- `02001_baseline_schema.sql` - helper functions
+- `02001_baseline_schema.sql` - Default currency, languages, invoice settings
 
 #### Folders Explored
 
@@ -4194,7 +4197,7 @@ The integration landscape comprises eight external domains declared in `libs/env
 | Freemius | HTTPS + `x-freemius-signature` (HMAC SHA-256) | Sandbox bypass when `NEXT_PUBLIC_IS_SANDBOX===true` |
 | Frankfurter FX | HTTPS (JSON) | Cron runs 18:00 UTC daily; `maxDuration: 30s` |
 | SMTP | SMTP + TLS | Best-effort from server actions |
-| Vercel Cron | HTTPS + Bearer `CRON_SECRET` | 03:00 UTC (reset-sandbox, 60s); 18:00 UTC (sync-currencies, 30s) |
+| Vercel Cron | HTTPS + Bearer `CRON_SECRET` | every 15 min (reset-sandbox, 60s); 18:00 UTC (sync-currencies, 30s) |
 | Google Tag Manager | HTTPS (JS) | GTM id from `privacy_settings` (site_settings); allowlisted in CSP |
 
 ## 5.2 COMPONENT DETAILS
@@ -4638,7 +4641,7 @@ Observability instrumentation includes @vercel/speed-insights for performance me
 | Prefetch Accuracy | Correct `X-Prefetch-Priority` per page-type | `proxy.ts` |
 | Media Optimization | Blur placeholders on uploads | sharp + plaiceholder pipeline |
 | Commerce Conversion | Checkout success by provider | `app/api/checkout/route.ts` + webhooks |
-| Scheduled Job Health | Daily success of sandbox reset + currency sync | `vercel.json` cron configuration |
+| Scheduled Job Health | Success of sandbox reset (every 15 min) + currency sync (daily) | `vercel.json` cron configuration |
 | Bundle Discipline | Removed console calls in production | `compiler.removeConsole` in `next.config.js` |
 
 ### 5.4.2 Logging and Tracing Strategy
@@ -4761,7 +4764,7 @@ Measurable performance objectives include 100/100 Lighthouse performance, a CLI
 
 #### 5.4.6.1 Sandbox Reset
 
-The `/api/cron/reset-sandbox` endpoint, scheduled daily at 03:00 UTC, reconstructs the demo environment end-to-end: it clears and repopulates Cloudflare R2 media, runs a generated SQL bootstrap (`sandboxResetSql.ts`) against Supabase, normalizes legacy media records, ensures required media assets exist, and seeds commerce/content data. The endpoint only executes when in sandbox mode and after verifying the Bearer `CRON_SECRET`.
+The `/api/cron/reset-sandbox` endpoint, scheduled every 15 minutes, reconstructs the demo environment end-to-end: it clears and repopulates Cloudflare R2 media, runs a generated SQL bootstrap (`sandboxResetSql.ts`) against Supabase, normalizes legacy media records, ensures required media assets exist, and seeds commerce/content data. The endpoint only executes when in sandbox mode and after verifying the Bearer `CRON_SECRET`.
 
 #### 5.4.6.2 Currency Synchronization
 
@@ -4779,8 +4782,8 @@ Supabase provides point-in-time recovery at the platform level; the eleven canon
 
 ```mermaid
 flowchart LR
-    subgraph Scheduled["Daily Schedules (Vercel Cron)"]
-        Reset[03:00 UTC<br/>/api/cron/reset-sandbox<br/>maxDuration 60s]
+    subgraph Scheduled["Schedules (Vercel Cron)"]
+        Reset[Every 15 min<br/>/api/cron/reset-sandbox<br/>maxDuration 60s]
         Sync[18:00 UTC<br/>/api/cron/sync-currencies<br/>maxDuration 30s]
     end
 
@@ -5443,7 +5446,7 @@ Two scheduled recovery flows are declared in `vercel.json` and serve both routin
 ```mermaid
 flowchart LR
     subgraph Schedules["vercel.json crons[]"]
-        Reset03[03:00 UTC daily<br/>/api/cron/reset-sandbox<br/>maxDuration 60s]
+        Reset03[Every 15 min<br/>/api/cron/reset-sandbox<br/>maxDuration 60s]
         Sync18[18:00 UTC daily<br/>/api/cron/sync-currencies<br/>maxDuration 30s]
     end
 
@@ -5480,7 +5483,7 @@ flowchart LR
     C4 --> C5
 ```
 
-The sandbox reset (`apps/nextblock/app/api/cron/reset-sandbox/route.ts`) only executes when in sandbox mode, providing a self-healing loop for the public demo environment. It serves as a **nightly reconstruction rehearsal** that validates the schema migrations and seed scripts.
+The sandbox reset (`apps/nextblock/app/api/cron/reset-sandbox/route.ts`) only executes when in sandbox mode, providing a self-healing loop for the public demo environment. It serves as a **continuous reconstruction rehearsal** that validates the schema migrations and seed scripts.
 
 #### 6.1.6.3 Content Recovery via Revisions
 
@@ -5533,7 +5536,7 @@ Failover behavior is **implicit via Vercel's platform** and **explicit via dual-
 - The workspace uses **library decomposition** (eight components in an Nx monorepo) with boundaries enforced at compile time by ESLint `@nx/enforce-module-boundaries`.
 - **Scalability is platform-delegated**: Vercel provides automatic horizontal scaling of stateless serverless functions. Application-level tuning is confined to cache TTLs, `maxDuration`, and caching layers.
 - **Resilience is expressed at the integration surface** via a five-pattern classification (strict failure, dual-path, and graceful degrade), exemplified by the RPC + SQL fallback inventory deduction.
-- **Disaster recovery** rests on Supabase platform PITR, 11 canonical migrations, `page_revisions`/`post_revisions` hybrid snapshot/diff content history, and a nightly sandbox-reset cron that doubles as a reconstruction rehearsal.
+- **Disaster recovery** rests on Supabase platform PITR, 11 canonical migrations, `page_revisions`/`post_revisions` hybrid snapshot/diff content history, and a 15-minute sandbox-reset cron that doubles as a reconstruction rehearsal.
 
 #### 6.1.7.2 Cross-References
 
@@ -5565,7 +5568,7 @@ Failover behavior is **implicit via Vercel's platform** and **explicit via dual-
 - `apps/nextblock/app/api/checkout/route.ts` — Checkout orchestration with `resolveProviderFromItem` chain and license-gate integration
 - `apps/nextblock/app/api/webhooks/stripe/route.ts` — Stripe signature verification + event dispatch
 - `apps/nextblock/app/api/webhooks/freemius/route.ts` — Freemius HMAC-SHA-256 verification + sandbox bypass
-- `apps/nextblock/app/api/cron/reset-sandbox/route.ts` — Daily sandbox reset flow; R2 clearing, SQL bootstrap, media normalization, seeding
+- `apps/nextblock/app/api/cron/reset-sandbox/route.ts` — 15-minute sandbox reset flow; R2 clearing, SQL bootstrap, media normalization, seeding
 - `apps/nextblock/app/api/cron/sync-currencies/route.ts` — Daily Frankfurter FX sync; Bearer `CRON_SECRET` auth
 - `apps/nextblock/app/api/revalidate/route.ts` — On-demand ISR invalidation from Supabase webhooks
 - `apps/nextblock/app/api/upload/presigned-url/route.ts` — R2 presigned URL generation (300s TTL, 10 MB cap)
@@ -5580,7 +5583,7 @@ Failover behavior is **implicit via Vercel's platform** and **explicit via dual-
 - `libs/db/src/lib/supabase/middleware.ts` — Supabase session synchronization helper
 - `libs/db/project.json` — Nx project definition with `scope:public` tag
 - `libs/environment.d.ts` — NodeJS.ProcessEnv augmentation declaring all external-service env vars
-- `vercel.json` — Two cron schedule declarations (03:00 UTC reset-sandbox; 18:00 UTC sync-currencies)
+- `vercel.json` — Two cron schedule declarations (every-15-minutes reset-sandbox; 18:00 UTC sync-currencies)
 - `nx.json` — Nx workspace orchestration and target defaults
 - `eslint.config.mjs` — `@nx/enforce-module-boundaries` rules for scope:public/scope:premium
 - `tsconfig.base.json` — Path aliases for all `@nextblock-cms/*` packages
@@ -5643,7 +5646,7 @@ The design leans on the Supabase managed platform for replication, connection po
 
 #### 6.2.2.1 Enumerated Types
 
-All domain-specific enumerations are declared in migration `00000000000000_setup_foundation_and_enums.sql` using idempotent `DO $$` guards so re-application is safe. The migration also grants `USAGE` on the `public` schema to the Supabase-managed roles `postgres`, `anon`, `authenticated`, and `service_role`.
+All domain-specific enumerations are declared in migration `02001_baseline_schema.sql` using idempotent `DO $$` guards so re-application is safe. The migration also grants `USAGE` on the `public` schema to the Supabase-managed roles `postgres`, `anon`, `authenticated`, and `service_role`.
 
 | Enum | Values | Usage |
 |------|--------|-------|
@@ -5654,7 +5657,7 @@ All domain-specific enumerations are declared in migration `00000000000000_setup
 
 #### 6.2.2.2 Identity and Core CMS Entities
 
-Declared in migration `00000000000001_setup_cms_core.sql`, these tables bootstrap the authentication mirror, languages, media registry, translations, logos, and the global key/value settings store.
+Declared in migration `02001_baseline_schema.sql`, these tables bootstrap the authentication mirror, languages, media registry, translations, logos, and the global key/value settings store.
 
 | Table | Primary Key | Key Columns / Constraints |
 |-------|-------------|----------------------------|
@@ -5673,7 +5676,7 @@ Declared in migration `00000000000001_setup_cms_core.sql`, these tables bootstra
 
 #### 6.2.2.3 Authoring Content Entities
 
-Declared in migration `00000000000002_setup_content_tables.sql`, these tables form the CMS authoring domain. The relationships are summarized in the ER diagram below.
+Declared in migration `02001_baseline_schema.sql`, these tables form the CMS authoring domain. The relationships are summarized in the ER diagram below.
 
 ```mermaid
 erDiagram
@@ -5760,7 +5763,7 @@ erDiagram
 
 #### 6.2.2.4 Commerce Entities
 
-Declared across migrations `00000000000003_setup_catalog_and_licensing.sql` and `00000000000004_setup_fulfillment_shipping_taxes_and_currencies.sql`, commerce spans catalog, licensing, orders, shipping, taxation, and currency infrastructure.
+Declared across migration `02001_baseline_schema.sql`, commerce spans catalog, licensing, orders, shipping, taxation, and currency infrastructure.
 
 ```mermaid
 erDiagram
@@ -5896,7 +5899,7 @@ Both `products` and `product_variants` store prices in two redundant shapes —
 
 #### 6.2.2.5 Indexing Strategy
 
-Migration `00000000000007_setup_indexes.sql` adds 38 secondary indexes. The strategy groups into four categories:
+Migration `02001_baseline_schema.sql` adds 38 secondary indexes. The strategy groups into four categories:
 
 | Category | Representative Indexes | Optimization Target |
 |----------|------------------------|---------------------|
@@ -5957,7 +5960,7 @@ flowchart TB
 | Manual restore | `psql` with duplicate-error collapser | `apps/nextblock/scripts/restore.js` |
 | Schema reconstruction | Replay 11 migrations in order | `npm run db:reset` via `supabase db reset --workdir libs/db/src` |
 | Content rollback | Hybrid snapshot/diff revisions | `page_revisions`, `post_revisions` (F-008) |
-| Sandbox rehearsal | Daily 03:00 UTC cron, 60s maxDuration | `/api/cron/reset-sandbox` (§4.5) |
+| Sandbox rehearsal | Every 15 minutes, 60s maxDuration | `/api/cron/reset-sandbox` (§4.5) |
 
 The `backup.js` script reads `POSTGRES_URL` or `DATABASE_URL` via `dotenv`, parses the connection URL, supports a `--name` CLI flag (or interactive prompt) for friendly backup names, creates timestamped directories under `apps/nextblock/backups/`, and spawns `pg_dump` with `PGPASSWORD` and `PGSSLMODE` passed via environment variables.
 
@@ -5967,29 +5970,17 @@ The `backup.js` script reads `POSTGRES_URL` or `DATABASE_URL` via `dotenv`, pars
 
 #### 6.2.3.1 Migration Procedures
 
-Migrations live in `libs/db/src/supabase/migrations/` and are managed via the Supabase CLI. Each file is a single SQL script prefixed by a lexicographically ordered timestamp. The **eleven consolidated migrations** represent merged historical migrations; internal comment headers preserve the original logical ordering within each file.
+Migrations live in `libs/db/src/supabase/migrations/` and are managed via the Supabase CLI plus the repo's own appliers (the `/setup` wizard, the build hook, `npm run update`, the Docker migration runner). The folder holds exactly one **squash generation**; files are named `GGNNN_name.sql` (GG = generation, NNN = contiguous sequence) and applied in lexical order. The current generation is 2 (built 2026-09-10); its first five slots are fixed and everything from `02005` upward is an ordinary forward migration.
 
 | File | Purpose | Key Outputs |
 |------|---------|-------------|
-| `00000000000000_setup_foundation_and_enums.sql` | Foundation grants and enums | `user_role`, `page_status`, `menu_location`, `revision_type` |
-| `00000000000001_setup_cms_core.sql` | Identity + content primitives | `profiles`, `user_addresses`, `languages`, `media`, `translations`, `logos`, `site_settings` |
-| `00000000000002_setup_content_tables.sql` | Authoring domain | `pages`, `posts`, `blocks`, `navigation_items`, `page_revisions`, `post_revisions` |
-| `00000000000003_setup_catalog_and_licensing.sql` | Commerce catalog and license registry | `products`, `product_variants`, `product_attributes`, `product_attribute_terms`, `product_media`, `variant_attribute_mapping`, `inventory_items`, `package_activations`, `freemius_plans`, `freemius_pricing` |
-| `00000000000004_setup_fulfillment_shipping_taxes_and_currencies.sql` | Order lifecycle + shipping/tax + currencies | `orders`, `order_items`, `order_invoice_number_seq`, `shipping_zones`, `shipping_zone_locations`, `shipping_zone_methods`, `tax_rates`, `currencies` + 12 functions + 7 triggers |
-| `00000000000005_setup_functions_and_triggers.sql` | Business logic layer | Auth helpers, first-user bootstrap, timestamp triggers, invoice sequence, inventory RPC |
-| `00000000000006_setup_rls_and_grants.sql` | Security policies | Enables RLS on all tables; declares SELECT/INSERT/UPDATE/DELETE policies |
-| `00000000000007_setup_indexes.sql` | Performance indexes | 38 indexes across all domains |
-| `00000000000008_seed_platform_defaults.sql` | Baseline platform state | English/French languages, USD as default currency, site_settings defaults |
-| `00000000000009_seed_translations.sql` | Internationalization content | Hundreds of en/es/fr i18n rows |
-| `00000000000010_seed_content_scaffold.sql` | Starter content | Default logos, home/articles pages, featured posts, navigation |
-| `00000000000011_setup_cortex_ai_settings.sql` | AI settings | Cortex AI configuration |
-| `00000000000012_setup_commerce_coupons.sql` | Commerce coupons | Coupon tables and constraints |
-| `00000000000013_setup_cortex_ai_db_mutation_audit.sql` | AI audit | Cortex AI database mutation audit support |
-| `00000000000014_setup_content_drafts.sql` | Content drafts | Visual-editing draft support |
-| `00000000000015_setup_product_drafts.sql` | Product drafts | Product draft workflow support |
-| `00000000000016_add_feature_image_to_pages.sql` | CMS page media | Optional page feature image relationship |
-
-Per Section 2.4.5, the **numbered migration files in `libs/db/src/supabase/migrations/` must remain applied in order**; out-of-sequence application will violate referential integrity. For live/shared databases, new changes must be appended as new non-destructive migrations. Do not rewrite, recycle, squash, reorder, or delete migrations that may already be recorded in production.
+| `02000_catchup_gen1.sql` | Version-aware replay of the retired generation-1 forward migrations | Converges databases that sat behind generation 1; skipped on empty databases and on databases already at generation ≥ 2; sets `site_settings.migration_baseline_generation` |
+| `02001_baseline_schema.sql` | Schema | All enums, functions, tables, sequences and defaults (`IF NOT EXISTS` / `CREATE OR REPLACE`); the `auth.users` → `handle_new_user` trigger |
+| `02002_baseline_constraints_and_indexes.sql` | Integrity + performance | Primary/unique/check/foreign-key constraints (catalog-guarded) and every index |
+| `02003_baseline_security_and_grants.sql` | Security | RLS enablement on every table, all policies, business/timestamp triggers, grants |
+| `02004_baseline_seed.sql` | Seed | Canonical demo content (languages, currencies, site settings, translations, media, pages/posts/blocks, navigation, shipping defaults, themes) — runs only on an empty database |
+
+Per Section 2.4.5, the **numbered migration files in `libs/db/src/supabase/migrations/` must remain applied in order**; out-of-sequence application will violate referential integrity. For live/shared databases, new changes must be appended as new non-destructive migrations. Do not rewrite, recycle, reorder, or delete migration files outside the documented squash runbook (`docs/04-DATABASE-AND-AUTH.md` → "Squashing migrations"); a squash always ships a catch-up so existing databases converge.
 
 ##### 6.2.3.1.1 Migration Command Surface
 
@@ -6000,7 +5991,7 @@ The root `package.json` exposes the following migration-related scripts:
 | `db:migrate:check` | `node tools/scripts/push-db-migrations.js --check` | Dry-run pending remote migrations |
 | `db:migrate` / `db:push` | `node tools/scripts/push-db-migrations.js --confirm` | Apply pending migration files only; no reset, sandbox seed, function deploy, or config push |
 | `db:migrate:repair-history:check` | `node tools/scripts/repair-db-migration-history.js --check` | Preview baseline migration-history repair |
-| `db:migrate:repair-history` | `node tools/scripts/repair-db-migration-history.js --confirm` | Mark existing baseline migrations as applied without running their SQL |
+| `db:migrate:repair-history` | `node tools/scripts/repair-db-migration-history.js --confirm` | Mark existing baseline migrations as applied without running their SQL; with `-- --reconcile-squash`, record a migration squash (revert retired versions, mark the new generation applied) |
 | `db:migrate:fresh` | `node tools/scripts/push-db-migrations.js --confirm --allow-baseline-replay` | Apply the full baseline only to a brand-new empty database |
 | `db:reset` | `supabase db reset --workdir libs/db/src` | Full local reset and replay |
 | `db:link` | `dotenv + supabase-link` via `tools/scripts/supabase-link.js` | Link local workspace to remote project |
@@ -6191,11 +6182,11 @@ All three paths **fail closed**: missing env vars, query errors, or non-`active`
 
 #### 6.2.4.2 Backup and Fault-Tolerance Policies
 
-Detailed in §6.2.2.8. In summary: Supabase-managed PITR and managed backups (primary DR); `pg_dump` / `psql` scripts (operator-initiated); 11 migrations as schema-of-truth (rebuild); hybrid snapshot/diff revisions (content rollback). The Sandbox Reset Cron at 03:00 UTC daily (60s `maxDuration`) doubles as a reconstruction rehearsal, as documented in §4.5.
+Detailed in §6.2.2.8. In summary: Supabase-managed PITR and managed backups (primary DR); `pg_dump` / `psql` scripts (operator-initiated); 11 migrations as schema-of-truth (rebuild); hybrid snapshot/diff revisions (content rollback). The Sandbox Reset Cron every 15 minutes (60s `maxDuration`) doubles as a reconstruction rehearsal, as documented in §4.5.
 
 #### 6.2.4.3 Privacy Controls via Row-Level Security
 
-RLS is **enabled on every table** in migration `00000000000006_setup_rls_and_grants.sql`. The policy matrix distributes into four access tiers.
+RLS is **enabled on every table** in migration `02001_baseline_schema.sql`. The policy matrix distributes into four access tiers.
 
 | Access Tier | Representative Scope | Tables |
 |-------------|----------------------|--------|
@@ -6327,7 +6318,7 @@ Application-layer details:
 
 | Batch Workload | Mechanism | Frequency |
 |----------------|-----------|-----------|
-| Sandbox reset (cron) | Service-role client replays seed migrations | Daily 03:00 UTC, 60s `maxDuration` |
+| Sandbox reset (cron) | Service-role client replays seed migrations | Every 15 minutes, 60s `maxDuration` |
 | Currency exchange-rate sync (cron) | Service-role client updates `currencies.exchange_rate` from Frankfurter API | Daily 18:00 UTC, 30s `maxDuration` |
 | Bulk variant upsert | `upsert_product_with_variants(jsonb)` PL/pgSQL function — admin-only via `is_admin()` | Ad-hoc, CMS-triggered |
 | Migration seeds | Direct SQL in migrations `00000000000008` through `00000000000010` with `ON CONFLICT` merge logic preserving existing values | At deploy time |
@@ -6479,17 +6470,17 @@ The local Supabase stack is configured through `libs/db/src/supabase/config.toml
 
 #### 6.2.9.1 Files Examined
 
-- `libs/db/src/supabase/migrations/00000000000000_setup_foundation_and_enums.sql` — Enums and schema grants
-- `libs/db/src/supabase/migrations/00000000000001_setup_cms_core.sql` — Core CMS tables (profiles, media, languages, translations)
-- `libs/db/src/supabase/migrations/00000000000002_setup_content_tables.sql` — Pages, posts, blocks, revisions, navigation
-- `libs/db/src/supabase/migrations/00000000000003_setup_catalog_and_licensing.sql` — Commerce catalog and license registry
-- `libs/db/src/supabase/migrations/00000000000004_setup_fulfillment_shipping_taxes_and_currencies.sql` — Orders, shipping, tax, currencies
-- `libs/db/src/supabase/migrations/00000000000005_setup_functions_and_triggers.sql` — Business logic functions and triggers
-- `libs/db/src/supabase/migrations/00000000000006_setup_rls_and_grants.sql` — Row-Level Security policy matrix
-- `libs/db/src/supabase/migrations/00000000000007_setup_indexes.sql` — 38 secondary indexes
-- `libs/db/src/supabase/migrations/00000000000008_seed_platform_defaults.sql` — Baseline platform seed
-- `libs/db/src/supabase/migrations/00000000000009_seed_translations.sql` — Internationalization seed
-- `libs/db/src/supabase/migrations/00000000000010_seed_content_scaffold.sql` — Starter content seed
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — Enums and schema grants
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — Core CMS tables (profiles, media, languages, translations)
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — Pages, posts, blocks, revisions, navigation
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — Commerce catalog and license registry
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — Orders, shipping, tax, currencies
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — Business logic functions and triggers
+- `libs/db/src/supabase/migrations/02003_baseline_security_and_grants.sql` — Row-Level Security policy matrix
+- `libs/db/src/supabase/migrations/02002_baseline_constraints_and_indexes.sql` — 38 secondary indexes
+- `libs/db/src/supabase/migrations/02004_baseline_seed.sql` — Baseline platform seed
+- `libs/db/src/supabase/migrations/02004_baseline_seed.sql` — Internationalization seed
+- `libs/db/src/supabase/migrations/02004_baseline_seed.sql` — Starter content seed
 - `libs/db/src/supabase/config.toml` — Supabase local stack configuration
 - `libs/db/src/lib/supabase/client.ts` — Browser client factory
 - `libs/db/src/lib/supabase/server.ts` — Server / SSR / service-role client factories
@@ -6829,7 +6820,7 @@ All "events" in this system are either **HTTP webhooks delivered by external pro
 | Stripe | `checkout.session.completed` (others ignored) | `libs/ecommerce/src/lib/stripe/webhooks.ts` |
 | Freemius | `install.upgraded`, `license.activated` (others ignored) | `apps/nextblock/app/api/webhooks/freemius/route.ts` |
 | Supabase DB Triggers | Row INSERT/UPDATE/DELETE on `pages` / `posts` | `apps/nextblock/app/api/revalidate/route.ts` |
-| Vercel Cron Ticks | Scheduled GET at `0 3 * * *` / `0 18 * * *` | `/api/cron/reset-sandbox`, `/api/cron/sync-currencies` |
+| Vercel Cron Ticks | Scheduled GET at `*/15 * * * *` / `0 18 * * *` | `/api/cron/reset-sandbox`, `/api/cron/sync-currencies` |
 
 ##### 6.3.3.1.2 Stripe Event Dispatcher Discipline
 
@@ -6862,12 +6853,12 @@ The revalidation flow functions as a degenerate "stream" with batch size 1: ever
 
 #### 6.3.3.4 Batch Processing Flows
 
-Two daily Vercel cron jobs constitute the entire batch processing surface, declared explicitly in `vercel.json`:
+Two Vercel cron jobs constitute the entire batch processing surface, declared explicitly in `vercel.json`:
 
 ```mermaid
 flowchart LR
     subgraph CronDecl["vercel.json crons[]"]
-        A[path: /api/cron/reset-sandbox<br/>schedule: 0 3 * * *]
+        A[path: /api/cron/reset-sandbox<br/>schedule: */15 * * * *]
         B[path: /api/cron/sync-currencies<br/>schedule: 0 18 * * *]
     end
 
@@ -6916,7 +6907,7 @@ flowchart LR
     SA6 --> SA7
 ```
 
-##### 6.3.3.4.1 Sandbox Reset Cron (03:00 UTC, maxDuration 60s)
+##### 6.3.3.4.1 Sandbox Reset Cron (every 15 minutes, maxDuration 60s)
 
 Purpose: Reconstruct the public demo environment from scratch so that visitor-driven modifications do not pollute the demo. The handler executes eleven ordered steps including R2 bucket clearing via `ListObjectsV2Command` + `DeleteObjectsCommand`, seed asset re-upload via `PutObjectCommand`, SQL bootstrap via the `postgres` driver, media record normalization, Freemius product synchronization, and commerce catalog seeding. The `finally { db.end() }` block guarantees Postgres connection teardown even on error.
 
@@ -7370,7 +7361,7 @@ Per Section 5.1.4.2, each external integration carries explicit SLA-like propert
 | Freemius | HTTPS + `x-freemius-signature` HMAC-SHA-256 | Sandbox bypass when `NEXT_PUBLIC_IS_SANDBOX===true` |
 | Frankfurter | HTTPS (JSON) | Cron daily 18:00 UTC; `maxDuration: 30s` |
 | SMTP | SMTP + TLS | Best-effort from server actions |
-| Vercel Cron | HTTPS + Bearer CRON_SECRET | 03:00 UTC (reset-sandbox 60s); 18:00 UTC (sync-currencies 30s) |
+| Vercel Cron | HTTPS + Bearer CRON_SECRET | every 15 min (reset-sandbox 60s); 18:00 UTC (sync-currencies 30s) |
 | Google Tag Manager | HTTPS (JS) | GTM id from `privacy_settings` (site_settings); allowlisted in CSP |
 
 #### 6.3.6.2 Known Integration Limitations
@@ -7403,7 +7394,7 @@ The `shipping_zone_locations.postal_code` column exists in the schema but the cu
 - **Four canonical patterns** (outbound HTTPS, signed webhook, token webhook, scheduled cron) cover every integration.
 - **Seven authentication mechanisms** coexist, each tailored to its upstream provider's requirements.
 - **Three-layer authorization** (cookie session → path-prefix guard → RLS + license gate) provides defense in depth.
-- **Batch processing** is limited to two daily Vercel crons (sandbox reset at 03:00 UTC, currency sync at 18:00 UTC).
+- **Batch processing** is limited to two Vercel crons (sandbox reset every 15 minutes, currency sync daily at 18:00 UTC).
 - **Error handling** is classified into strict-fail, dual-path, and best-effort categories with the RPC + SQL fallback for inventory deduction being the most sophisticated resilience primitive.
 - **Known limitations** include incomplete Freemius reconciliation, a package alias mismatch, FX schema coupling, and an unused postal-code column.
 
@@ -7428,7 +7419,7 @@ The `shipping_zone_locations.postal_code` column exists in the schema but the cu
 
 #### Files Examined
 
-- `vercel.json` — Cron schedule declarations (`reset-sandbox` at 03:00 UTC, `sync-currencies` at 18:00 UTC)
+- `vercel.json` — Cron schedule declarations (`reset-sandbox` every 15 minutes, `sync-currencies` at 18:00 UTC)
 - `libs/environment.d.ts` — NodeJS.ProcessEnv augmentation declaring all external-integration environment variables
 - `.env.example` — Authoritative environment variable template
 - `apps/nextblock/proxy.ts` — 272-line request proxy consolidating session sync, RBAC, locale, security headers, CSP, and page-type classification
@@ -7507,7 +7498,7 @@ Security controls are layered so that the failure of any single layer does not r
 |-------|----------------------|------------------|
 | Edge | Request proxy — session refresh, path-prefix RBAC, security headers, CSP | `apps/nextblock/proxy.ts` |
 | Application | Client-layout role guard, server-action `verifyAdmin()`, role-gated page components | `app/cms/CmsClientLayout.tsx`, `app/cms/users/actions.ts` |
-| Data | Row-Level Security policies, SECURITY DEFINER helpers, service-role bypass | `libs/db/src/supabase/migrations/00000000000006_setup_rls_and_grants.sql` |
+| Data | Row-Level Security policies, SECURITY DEFINER helpers, service-role bypass | `libs/db/src/supabase/migrations/02003_baseline_security_and_grants.sql` |
 | Integration | Webhook signature verification, Bearer-secret cron, HMAC-verified callbacks | `/api/webhooks/*`, `/api/cron/*`, `/api/revalidate/route.ts` |
 
 #### 6.4.1.3 Security Architecture Topology
@@ -7617,7 +7608,7 @@ The system manages three distinct token classes, each with differentiated lifecy
 | OAuth Authorization Code | Short-lived code exchange | URL query parameter, consumed immediately at `/auth/callback` |
 | Supabase Service Role Key | Server-only RLS bypass | Vercel environment variable (`SUPABASE_SERVICE_ROLE_KEY`) |
 
-A **per-request nonce** is generated via `crypto.randomUUID()` in `proxy.ts` and used for the nonce-based CSP (see §6.4.4.5). JWT claims are read inside Postgres by the `get_my_claim(claim text)` SECURITY DEFINER function via `current_setting('request.jwt.claims', true)::jsonb`, which is defined in `libs/db/src/supabase/migrations/00000000000005_setup_functions_and_triggers.sql`.
+A **per-request nonce** is generated via `crypto.randomUUID()` in `proxy.ts` and used for the nonce-based CSP (see §6.4.4.5). JWT claims are read inside Postgres by the `get_my_claim(claim text)` SECURITY DEFINER function via `current_setting('request.jwt.claims', true)::jsonb`, which is defined in `libs/db/src/supabase/migrations/02001_baseline_schema.sql`.
 
 The **service role key** requires two independent compile-time and runtime guards to prevent leakage into the browser bundle:
 
@@ -7715,7 +7706,7 @@ The `resolvePostAuthRedirect` helper enforces four rules as a gate against open-
 
 #### 6.4.3.1 Role-Based Access Control Model
 
-Authorization is driven by the `user_role` enum declared in migration `00000000000000_setup_foundation_and_enums.sql`, which admits three values plus an implicit fourth (Supabase's `service_role`) for server-only privilege elevation:
+Authorization is driven by the `user_role` enum declared in migration `02001_baseline_schema.sql`, which admits three values plus an implicit fourth (Supabase's `service_role`) for server-only privilege elevation:
 
 | Role | Assignment Mechanism | Zone Capabilities |
 |------|---------------------|-------------------|
@@ -7728,7 +7719,7 @@ Role assignment at bootstrap is governed by the `handle_new_user()` SECURITY DEF
 
 #### 6.4.3.2 Permission Management and SECURITY DEFINER Helpers
 
-Role checks executed inside SQL contexts use SECURITY DEFINER helper functions declared in `libs/db/src/supabase/migrations/00000000000005_setup_functions_and_triggers.sql`. SECURITY DEFINER elevates the function's execution privileges to the function owner, bypassing caller-side RLS for the function body while `SET search_path = ''` prevents search-path hijacking attacks.
+Role checks executed inside SQL contexts use SECURITY DEFINER helper functions declared in `libs/db/src/supabase/migrations/02001_baseline_schema.sql`. SECURITY DEFINER elevates the function's execution privileges to the function owner, bypassing caller-side RLS for the function body while `SET search_path = ''` prevents search-path hijacking attacks.
 
 | Function | Purpose | Security Annotation |
 |----------|---------|---------------------|
@@ -7741,7 +7732,7 @@ These helpers form the primitive vocabulary of all RLS policies: a user's effect
 
 #### 6.4.3.3 Resource Authorization Matrix
 
-RLS is enabled on every table in migration `00000000000006_setup_rls_and_grants.sql` (872 lines). The matrix distributes into four access tiers:
+RLS is enabled on every table in migration `02001_baseline_schema.sql` (872 lines). The matrix distributes into four access tiers:
 
 | Access Tier | Typical Policy Predicate | Representative Tables |
 |-------------|--------------------------|------------------------|
@@ -8127,7 +8118,7 @@ The security control matrix below enumerates the principal threats, their mitiga
 
 | Threat | Mitigation | Migration or File |
 |--------|-----------|-------------------|
-| Public data exposure through writes | RLS writes restricted; public read only for intended tables and statuses | `migrations/00000000000006_setup_rls_and_grants.sql` |
+| Public data exposure through writes | RLS writes restricted; public read only for intended tables and statuses | `migrations/02003_baseline_security_and_grants.sql` |
 | Draft content leakage | Anon policy `status='published'` on pages; `status='published' AND published_at<=now()` on posts | `migration 00000000000006` |
 | Path traversal in uploads | `sanitizeFolder()` collapses `../`, strips leading slashes, removes illegal chars | `/api/upload/presigned-url/route.ts` |
 | Search-path hijacking in SECURITY DEFINER | `SET search_path = ''` on auth helper functions | `migration 00000000000005` |
@@ -8196,7 +8187,7 @@ For details beyond the scope of this section, consult:
 
 - `apps/nextblock/proxy.ts` — 272-line edge proxy (session sync, RBAC, locale, CSP, headers, page-type signaling)
 - `apps/nextblock/next.config.js` — 91-line image security config + `compiler.removeConsole`
-- `apps/nextblock/vercel.json` — Cron schedule declarations (03:00 reset-sandbox, 18:00 sync-currencies)
+- `apps/nextblock/vercel.json` — Cron schedule declarations (every-15-minutes reset-sandbox, 18:00 sync-currencies)
 
 #### Authentication and Authorization
 
@@ -8226,9 +8217,9 @@ For details beyond the scope of this section, consult:
 
 #### Database Security Surface
 
-- `libs/db/src/supabase/migrations/00000000000000_setup_foundation_and_enums.sql` — `user_role` enum declaration
-- `libs/db/src/supabase/migrations/00000000000005_setup_functions_and_triggers.sql` — `handle_new_user`, `get_current_user_role`, `is_admin`, `get_my_claim` SECURITY DEFINER functions
-- `libs/db/src/supabase/migrations/00000000000006_setup_rls_and_grants.sql` — 872-line RLS policy matrix
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — `user_role` enum declaration
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — `handle_new_user`, `get_current_user_role`, `is_admin`, `get_my_claim` SECURITY DEFINER functions
+- `libs/db/src/supabase/migrations/02003_baseline_security_and_grants.sql` — 872-line RLS policy matrix
 - `libs/db/src/supabase/config.toml` — 341-line Supabase Auth + MFA + rate-limit configuration
 - `libs/db/src/supabase/templates/` — Six transactional email templates
 
@@ -8546,7 +8537,7 @@ No dedicated `/api/health` or `/api/readiness` endpoint exists in the repository
 
 ##### 6.5.3.1.2 Scheduled-Execution Health Signal
 
-The two Vercel cron schedules in `vercel.json` serve a dual purpose: they perform their business function (sandbox reset and currency sync) while simultaneously producing a daily heartbeat that is visible on the Vercel dashboard. A cron invocation that returns HTTP 500 is therefore the closest the system comes to an automated unhealthy signal, because it is automatically surfaced in Vercel's cron execution history.
+The two Vercel cron schedules in `vercel.json` serve a dual purpose: they perform their business function (sandbox reset and currency sync) while simultaneously producing a recurring heartbeat that is visible on the Vercel dashboard. A cron invocation that returns HTTP 500 is therefore the closest the system comes to an automated unhealthy signal, because it is automatically surfaced in Vercel's cron execution history.
 
 #### 6.5.3.2 Performance Metrics
 
@@ -8608,7 +8599,7 @@ SLAs are encoded directly in configuration files (`vercel.json`, `next.config.js
 | Sync-currencies `maxDuration` | 30 seconds | `vercel.json` + route |
 | Reset-sandbox `maxDuration` | 60 seconds | `vercel.json` + route |
 | Currency sync schedule | `0 18 * * *` (18:00 UTC daily) | `vercel.json` |
-| Sandbox reset schedule | `0 3 * * *` (03:00 UTC daily) | `vercel.json` |
+| Sandbox reset schedule | `*/15 * * * *` (every 15 minutes) | `vercel.json` |
 | Max source image width | 2560 pixels | `/api/process-image` |
 | Lighthouse performance target | 100/100 | `README.md` |
 | CLI scaffold target | ≤ 30 seconds | `README.md` |
@@ -8651,9 +8642,9 @@ flowchart LR
         HstsHeader[HSTS Header<br/>2 years max-age]
     end
 
-    subgraph Scheduled[" Scheduled Daily "]
+    subgraph Scheduled[" Scheduled (Vercel Cron) "]
         CurrencyDay[18:00 UTC<br/>Sync Currencies]
-        ResetDay[03:00 UTC<br/>Sandbox Reset]
+        ResetDay[Every 15 min<br/>Sandbox Reset]
     end
 ```
 
@@ -8764,7 +8755,7 @@ Operators have four primary recovery mechanisms, all described in detail in Sect
 1. **Content rollback via revisions.** `page_revisions` and `post_revisions` tables store hybrid snapshot/diff records (JSON Patch via `fast-json-patch`) keyed by `UNIQUE (page_id, version)`. Any published state can be restored without a database restore.
 2. **Supabase Point-in-Time Recovery.** Platform-level PITR is the authoritative recovery path for catastrophic data loss.
 3. **Schema reconstruction from migrations.** The eleven canonical SQL files in `libs/db/src/supabase/migrations/` (`000_foundation_and_enums` through `010_seed_content_scaffold`) allow deterministic schema rebuild on a fresh Supabase project.
-4. **Nightly sandbox reset as reconstruction rehearsal.** The 03:00 UTC `/api/cron/reset-sandbox` job exercises the full R2-clear → SQL-bootstrap → media-normalize → seed pipeline daily, serving as continuous validation that the recovery procedure still works.
+4. **15-minute sandbox reset as reconstruction rehearsal.** The 15-minute `/api/cron/reset-sandbox` job exercises the full R2-clear → SQL-bootstrap → media-normalize → seed pipeline every 15 minutes, serving as continuous validation that the recovery procedure still works.
 
 #### 6.5.4.5 Post-mortem Processes
 
@@ -8856,7 +8847,7 @@ The following observability gaps are acknowledged and documented for honest stak
 - **Alert routing is manual.** The primary alert path is the `FeedbackModal` → `submitFeedback` → SMTP → `feedback@nextblock.dev` flow; platform alerts are configured in Vercel/Supabase consoles.
 - **No distributed tracing, no alert manager, no runbooks, no post-mortems, no persistent audit log table.** These absences are deliberate for the system's scale and are documented as explicit gaps.
 - **SLAs are codified in config, not monitored actively.** The canonical SLA table (Section 4.12) lists all timing constraints; crossings surface as HTTP errors or terminated function invocations in the Vercel log stream.
-- **Disaster recovery rests on Supabase PITR, canonical migrations, content revisions, and the nightly sandbox-reset reconstruction rehearsal** (detailed in Section 6.1.6 and Section 5.4.6).
+- **Disaster recovery rests on Supabase PITR, canonical migrations, content revisions, and the 15-minute sandbox-reset reconstruction rehearsal** (detailed in Section 6.1.6 and Section 5.4.6).
 
 #### 6.5.7.2 Cross-References to Related Sections
 
@@ -8899,7 +8890,7 @@ The following observability gaps are acknowledged and documented for honest stak
 - `libs/ecommerce/src/lib/stripe/webhooks.ts` — Stripe webhook handler with `[Stripe Webhook Error]` prefix; `console.error` on missing `STRIPE_WEBHOOK_SECRET` and on `constructEvent` failure
 - `libs/db/src/lib/package-validation.ts` — License gate with `console.error` and 60-second `unstable_cache` tagged `'package-activation'`
 - `libs/environment.d.ts` — `NodeJS.ProcessEnv` augmentation declaring external-service env vars (Supabase, R2/S3, SMTP, Freemius, OpenRouter/Cortex AI). GTM is no longer env-configured — it lives in `privacy_settings`.
-- `vercel.json` — Two cron schedule declarations: `0 3 * * *` reset-sandbox (60s) and `0 18 * * *` sync-currencies (30s)
+- `vercel.json` — Two cron schedule declarations: `*/15 * * * *` reset-sandbox (60s) and `0 18 * * *` sync-currencies (30s)
 - `package.json` (root) — Dependency declarations including `@vercel/speed-insights` and `@next/third-parties`
 - `apps/nextblock/package.json` — Template-level dependency declarations including `@vercel/analytics` (declared but not imported)
 - `docs/05-DEVELOPER-GUIDE.md` — Operational handbook, deployment notes, sandbox operations
@@ -9102,7 +9093,7 @@ Because no integration test suite exists, there is no dedicated test environment
 |:--|:--|
 | Local Supabase via `libs/db/src/supabase/config.toml` | Developer database for hand-driven verification |
 | Vercel Preview Deployments | Per-branch verification prior to production |
-| Sandbox production environment | End-to-end smoke testing via `NEXT_PUBLIC_IS_SANDBOX=true` flag with nightly reset cron |
+| Sandbox production environment | End-to-end smoke testing via `NEXT_PUBLIC_IS_SANDBOX=true` flag with a 15-minute reset cron |
 
 ---
 
@@ -9112,7 +9103,7 @@ Because no integration test suite exists, there is no dedicated test environment
 
 No E2E test framework (Playwright, Cypress, WebdriverIO, Puppeteer) is installed. This is explicitly documented as the accepted tradeoff in ADR §5.3.1: *"Vitest-only — Limited end-to-end coverage."* The absence is compensated by:
 
-1. **Sandbox reset cron as reconstruction rehearsal.** The `/api/cron/reset-sandbox` endpoint (§6.1.6.2) runs nightly at 03:00 UTC, clearing R2, running `SANDBOX_RESET_SQL`, normalizing legacy media, re-seeding commerce and content. A successful reset validates that the full happy-path data pipeline — migrations, storage, seeding — functions end-to-end.
+1. **Sandbox reset cron as reconstruction rehearsal.** The `/api/cron/reset-sandbox` endpoint (§6.1.6.2) runs every 15 minutes, clearing R2, running `SANDBOX_RESET_SQL`, normalizing legacy media, re-seeding commerce and content. A successful reset validates that the full happy-path data pipeline — migrations, storage, seeding — functions end-to-end.
 2. **Lighthouse performance score targeting 100/100.** Per §5.3.4 and §5.4.5, the 100/100 Lighthouse target provides an observational E2E signal on a per-deployment basis.
 3. **Production monitoring via Vercel Speed Insights + structured `console.warn`/`console.error`.** Per §6.4.3.5, production diagnostics survive `compiler.removeConsole` stripping and provide post-release observability.
 
@@ -9545,7 +9536,7 @@ The accepted tradeoff in §5.3.1 ("Vitest-only — Limited end-to-end coverage")
 - `apps/create-nextblock/package.json` — npm-init stub `"test": "echo \"Error: no test specified\" && exit 1"`
 - `apps/nextblock/project.json` — No test target declared
 - `tools/scripts/release-lib.js` — Library release pipeline; runs `npx nx run ${nxProject}:build --skip-nx-cache --with-deps` with no test invocation
-- `vercel.json` — Cron declarations (03:00 UTC reset-sandbox; 18:00 UTC sync-currencies); no test hooks
+- `vercel.json` — Cron declarations (every-15-minutes reset-sandbox; 18:00 UTC sync-currencies); no test hooks
 - `docs/05-DEVELOPER-GUIDE.md` — Developer command reference; no test commands documented
 - `.agent/skills/nx-operations/SKILL.md` — Front matter mentions tests but body documents only Building, Linting, and Development
 
@@ -10564,7 +10555,7 @@ The repository supports three deployment environments, with promotion driven by
 | Preview / Staging | Push to non-deployment branch or PR | Vercel Preview Deployment (unique URL per commit) |
 | Production | Push to Vercel-integrated deployment branch (default base: `master`) | Vercel Production Deployment (`NEXT_PUBLIC_URL`) |
 
-A special **Sandbox production environment** is gated by `NEXT_PUBLIC_IS_SANDBOX=true` and is reset nightly at 03:00 UTC via the `/api/cron/reset-sandbox` endpoint. Sandbox serves as a public demonstration site and as a continuous reconstruction rehearsal for the disaster recovery pipeline (see §8.2.2.5).
+A special **Sandbox production environment** is gated by `NEXT_PUBLIC_IS_SANDBOX=true` and is reset every 15 minutes via the `/api/cron/reset-sandbox` endpoint. Sandbox serves as a public demonstration site and as a continuous reconstruction rehearsal for the disaster recovery pipeline (see §8.2.2.5).
 
 #### 8.2.2.4 Environment Promotion Flow Diagram
 
@@ -10575,7 +10566,7 @@ flowchart LR
     Preview[Vercel Preview Deployment<br/>Per-commit URL<br/>Shared Supabase preview]
     Merge[Merge to master]
     Prod[Vercel Production Deployment<br/>NEXT_PUBLIC_URL<br/>Production Supabase]
-    Sandbox[Sandbox Production<br/>NEXT_PUBLIC_IS_SANDBOX=true<br/>Nightly reset 03:00 UTC]
+    Sandbox[Sandbox Production<br/>NEXT_PUBLIC_IS_SANDBOX=true<br/>Reset every 15 min]
     ResetCycle[R2 clear +<br/>SANDBOX_RESET_SQL +<br/>media normalize +<br/>seed content]
 
     Dev --> PR
@@ -10585,7 +10576,7 @@ flowchart LR
     Prod -.parallel branch.-> Sandbox
 
     Sandbox -->|cron/reset-sandbox| ResetCycle
-    ResetCycle -.nightly.-> Sandbox
+    ResetCycle -.every 15 min.-> Sandbox
 
     style Dev fill:#e0f2fe,stroke:#0284c7
     style Preview fill:#fef3c7,stroke:#d97706
@@ -10602,7 +10593,7 @@ Disaster recovery relies on **four compounding recovery mechanisms**, none of wh
 | Supabase Point-in-Time Recovery (PITR) | Catastrophic data loss | Platform-managed by Supabase |
 | Content revisions | Accidental edits / content rollback | `page_revisions` + `post_revisions` tables with JSON Patch diffs (via `fast-json-patch`), `UNIQUE(page_id, version)` |
 | Schema reconstruction from migrations | Cold-start rebuild | 11 canonical SQL files in `libs/db/src/supabase/migrations/` applied in order |
-| Nightly sandbox reset (reconstruction rehearsal) | Continuous validation that recovery pipeline works | `/api/cron/reset-sandbox` at 03:00 UTC |
+| 15-minute sandbox reset (reconstruction rehearsal) | Continuous validation that recovery pipeline works | `/api/cron/reset-sandbox` every 15 minutes |
 
 Backup responsibility matrix:
 
@@ -10787,7 +10778,7 @@ Security is enforced across four layers, with compliance-relevant controls conce
 |:--|:--|:--|
 | Edge | Nonce-based CSP, HSTS, X-Frame-Options SAMEORIGIN, X-Content-Type-Options nosniff, Referrer-Policy origin-when-cross-origin, Permissions-Policy, COOP same-origin | `proxy.ts` |
 | Application | RBAC via `cmsRoutePermissions` (`/cms` ADMIN/WRITER; `/cms/admin`, `/cms/users`, `/cms/settings` ADMIN only); `verifyAdmin()` in server actions | `proxy.ts`, server actions |
-| Data | RLS policies + SECURITY DEFINER helpers (`get_my_claim`, `get_current_user_role`, `is_admin`, `handle_new_user`) | Migration `00000000000006_setup_rls_and_grants.sql` (872 lines) |
+| Data | RLS policies + SECURITY DEFINER helpers (`get_my_claim`, `get_current_user_role`, `is_admin`, `handle_new_user`) | Migration `02001_baseline_schema.sql` (872 lines) |
 | Integration | Stripe `constructEvent` signature verification; Freemius HMAC-SHA-256; `CRON_SECRET` Bearer auth; `REVALIDATE_SECRET_TOKEN` via `x-revalidate-secret` header | Webhook + cron route handlers |
 
 **Service role key hardening**: `SUPABASE_SERVICE_ROLE_KEY` is guarded at runtime via `typeof window !== 'undefined'` checks and build-time via `import 'server-only'` directives to prevent browser exposure.
@@ -11047,7 +11038,7 @@ Scheduled jobs deploy automatically with the application via `vercel.json`:
 ```json
 {
   "crons": [
-    {"path": "/api/cron/reset-sandbox", "schedule": "0 3 * * *"},
+    {"path": "/api/cron/reset-sandbox", "schedule": "*/15 * * * *"},
     {"path": "/api/cron/sync-currencies", "schedule": "0 18 * * *"}
   ]
 }
@@ -11055,7 +11046,7 @@ Scheduled jobs deploy automatically with the application via `vercel.json`:
 
 | Cron | Schedule (UTC) | maxDuration | Authentication |
 |:--|:--|:--|:--|
-| `/api/cron/reset-sandbox` | `0 3 * * *` (03:00 daily) | 60s | `Authorization: Bearer ${CRON_SECRET}` |
+| `/api/cron/reset-sandbox` | `*/15 * * * *` (every 15 minutes) | 60s | `Authorization: Bearer ${CRON_SECRET}` |
 | `/api/cron/sync-currencies` | `0 18 * * *` (18:00 daily) | 30s | `Authorization: Bearer ${CRON_SECRET}` |
 
 Purpose: `reset-sandbox` performs R2 clear + `SANDBOX_RESET_SQL` + media normalize + content seed; `sync-currencies` performs Frankfurter FX fetch + currency row update.
@@ -11111,7 +11102,7 @@ flowchart TB
     subgraph CronPipeline["Scheduled Jobs - Vercel Cron"]
         CronDecl[vercel.json crons array]
         CronRuntime[Vercel Cron Dispatcher]
-        ResetJob[/api/cron/reset-sandbox<br/>03:00 UTC]
+        ResetJob[/api/cron/reset-sandbox<br/>every 15 min]
         SyncJob[/api/cron/sync-currencies<br/>18:00 UTC]
     end
 
@@ -11285,7 +11276,7 @@ Per §4.12, the following are the codified timing constraints. Breaches surface
 | Sync-currencies maxDuration | 30s | `vercel.json` + route export |
 | Reset-sandbox maxDuration | 60s | `vercel.json` + route export |
 | Currency sync schedule | 18:00 UTC daily | `vercel.json` |
-| Sandbox reset schedule | 03:00 UTC daily | `vercel.json` |
+| Sandbox reset schedule | every 15 minutes | `vercel.json` |
 | Max source image width | 2560 px | `/api/process-image` |
 | Image derivative widths | 1920, 1280, 768, 384, 128 | `next.config.js` `deviceSizes`/`imageSizes` |
 | Image quality presets | 60, 75 | `next.config.js` `qualities` |
@@ -11300,7 +11291,7 @@ Per §4.12, the following are the codified timing constraints. Breaches surface
 | Vercel function invocations | Vercel dashboard | Auto-scaled; `maxDuration` capping |
 | Vercel bandwidth | Vercel dashboard | 1-year image cache TTL, AVIF compression |
 | Vercel image optimization count | Vercel dashboard | `minimumCacheTTL: 31_536_000` |
-| Supabase DB CPU/IO | Supabase dashboard | RLS indexing (`00000000000007_setup_indexes.sql`) |
+| Supabase DB CPU/IO | Supabase dashboard | RLS indexing (`02001_baseline_schema.sql`) |
 | Supabase egress | Supabase dashboard | Server-side aggregation; `count` head queries |
 | R2 storage | Cloudflare dashboard | Folder path sanitization prevents duplicates |
 | R2 Class A writes | Cloudflare dashboard | Single direct-upload via presigned URL (vs through server) |
@@ -11411,7 +11402,7 @@ graph TB
 | Review Vercel log stream | Daily / on-alert | Vercel console |
 | Review Supabase Advisors | Weekly | Supabase console |
 | Review feedback inbox | Daily | `feedback@nextblock.dev` |
-| Sandbox reset validation | Automated | `/api/cron/reset-sandbox` nightly at 03:00 UTC |
+| Sandbox reset validation | Automated | `/api/cron/reset-sandbox` every 15 minutes |
 | FX rate sync | Automated | `/api/cron/sync-currencies` daily at 18:00 UTC |
 | Dependency audit | Per release | `npm audit`, manual review |
 | Security patch review | On advisory | `npm update` + regression testing |
@@ -11543,12 +11534,12 @@ Operators should select tiers based on expected monthly active users, storage fo
 - **Vercel-native, platform-delegated deployment**: no Docker, no Kubernetes, no Terraform, no GitHub Actions — all four absences are intentional ADRs documented in §5.3.7.3 and §3.7.1.
 - **Three managed platform providers** compose the production footprint: Vercel (app + edge + cron + RUM), Supabase (PostgreSQL 17 + Auth + Storage metadata), Cloudflare R2 (S3-compatible object storage).
 - **Hybrid CI/CD** combines Vercel Git integration (for application deployment) with three Node.js release scripts under `tools/scripts/` (for library/CLI/DB releases).
-- **Two Vercel cron schedules** in `vercel.json`: `/api/cron/reset-sandbox` at 03:00 UTC (60s max) and `/api/cron/sync-currencies` at 18:00 UTC (30s max).
+- **Two Vercel cron schedules** in `vercel.json`: `/api/cron/reset-sandbox` every 15 minutes (60s max) and `/api/cron/sync-currencies` at 18:00 UTC (30s max).
 - **Infrastructure as Code is declarative**, distributed across `vercel.json`, `nx.json`, `libs/db/src/supabase/{migrations/, config.toml, templates/}`, `.env.example`, and per-project `project.json` files.
 - **Library publication uses a Twin Package Strategy** for `@nextblock-cms/ecom`: stub to public npm registry + real module to private GitHub Packages.
 - **11 canonical SQL migrations** compose the database schema; re-running them from a fresh Supabase project deterministically reconstructs the system.
 - **Monitoring is intentionally minimal**: Vercel Speed Insights for RUM, GTM for client analytics, structured `console.warn`/`console.error` logs for server-side events. No Prometheus/Grafana/Datadog/PagerDuty.
-- **Disaster recovery relies on four compounding mechanisms**: Supabase PITR, content revisions with JSON Patch diffs, schema reconstruction from migrations, and nightly sandbox reset as a continuous reconstruction rehearsal.
+- **Disaster recovery relies on four compounding mechanisms**: Supabase PITR, content revisions with JSON Patch diffs, schema reconstruction from migrations, and 15-minute sandbox reset as a continuous reconstruction rehearsal.
 - **Cost optimization is designed in**: zero egress on R2, platform-delegated scaling on Vercel, 1-year image cache TTL, daily (not per-request) FX sync.
 
 ### 8.11.2 Cross-References to Other Sections
@@ -11582,7 +11573,7 @@ Operators should select tiers based on expected monthly active users, storage fo
 **Files Examined**
 
 - `.env.example` — Authoritative inventory of 40+ environment variables across 7 categories (Platform, Secrets, FX, Supabase, R2, SMTP, Stripe, Freemius)
-- `vercel.json` — Declarative cron schedule definitions (2 crons: reset-sandbox at 03:00 UTC, sync-currencies at 18:00 UTC)
+- `vercel.json` — Declarative cron schedule definitions (2 crons: reset-sandbox every 15 minutes, sync-currencies at 18:00 UTC)
 - `package.json` (root) — Workspace identity (`nextblock`), 51 npm scripts, Nx plugin versions, dependency overrides, `packageManager`
 - `nx.json` — Workspace orchestration: 6 plugins, `defaultBase: master`, production named-input exclusions, `release.version.preVersionCommand`
 - `apps/nextblock/next.config.js` — Image pipeline config, `compiler.removeConsole`, `transpilePackages`, dynamic `remotePatterns`, `turbopack.resolveAlias`
@@ -11702,15 +11693,15 @@ The following enum types are defined in the eleven canonical SQL migrations loca
 
 | Enum Type | Allowed Values | Migration |
 |:--|:--|:--|
-| `user_role` | `ADMIN`, `WRITER`, `USER` | `00000000000000_setup_foundation_and_enums.sql` |
-| `page_status` | `draft`, `published`, `archived` | `00000000000002_setup_content_tables.sql` |
-| `menu_location` | `header`, `footer`, `sidebar` | `00000000000002_setup_content_tables.sql` |
-| `revision_type` | `snapshot`, `diff` | `00000000000002_setup_content_tables.sql` |
-| `product_type` | `physical`, `digital` | `00000000000003_setup_catalog_and_licensing.sql` |
-| `payment_provider` | `stripe`, `freemius` | `00000000000003_setup_catalog_and_licensing.sql` |
-| `order_status` | `pending`, `paid`, `shipped`, `delivered`, `refunded`, `cancelled` | `00000000000004_setup_fulfillment_shipping_taxes_and_currencies.sql` |
-| `tax_calculation_mode` | `manual`, `automatic` | `00000000000004_setup_fulfillment_shipping_taxes_and_currencies.sql` |
-| `inventory_deduction_method` | `rpc`, `sql-fallback` | `00000000000004_setup_fulfillment_shipping_taxes_and_currencies.sql` |
+| `user_role` | `ADMIN`, `WRITER`, `USER` | `02001_baseline_schema.sql` |
+| `page_status` | `draft`, `published`, `archived` | `02001_baseline_schema.sql` |
+| `menu_location` | `header`, `footer`, `sidebar` | `02001_baseline_schema.sql` |
+| `revision_type` | `snapshot`, `diff` | `02001_baseline_schema.sql` |
+| `product_type` | `physical`, `digital` | `02001_baseline_schema.sql` |
+| `payment_provider` | `stripe`, `freemius` | `02001_baseline_schema.sql` |
+| `order_status` | `pending`, `paid`, `shipped`, `delivered`, `refunded`, `cancelled` | `02001_baseline_schema.sql` |
+| `tax_calculation_mode` | `manual`, `automatic` | `02001_baseline_schema.sql` |
+| `inventory_deduction_method` | `rpc`, `sql-fallback` | `02001_baseline_schema.sql` |
 
 Cross-reference: Section 6.2 (Database Design), Section 4.11 (Validation Rules and Compliance Checkpoints).
 
@@ -11771,7 +11762,7 @@ Reproduced from Section 4.12 for quick reference during operational work. Values
 | Sync-currencies `maxDuration` | 30 seconds | `api/cron/sync-currencies` |
 | Reset-sandbox `maxDuration` | 60 seconds | `api/cron/reset-sandbox` |
 | Currency sync schedule | `0 18 * * *` (18:00 UTC daily) | `vercel.json` |
-| Sandbox reset schedule | `0 3 * * *` (03:00 UTC daily) | `vercel.json` |
+| Sandbox reset schedule | `*/15 * * * *` (every 15 minutes) | `vercel.json` |
 | Max source image width | 2560 pixels | `api/process-image` |
 | Image derivative widths | 1920, 1280, 768, 384, 128 | `api/process-image` |
 | Lighthouse performance target | 100/100 | `README.md` |
@@ -12149,7 +12140,7 @@ The glossary defines domain-specific, product-specific, and platform-specific te
 
 **Sandbox Mode** — The demonstration environment activated by `NEXT_PUBLIC_IS_SANDBOX=true`. The `cms.nextblock.dev` deployment operates in sandbox mode with demo credentials `demo@nextblock.dev` / `password`.
 
-**Sandbox Reset** — The nightly 03:00 UTC cron job at `/api/cron/reset-sandbox` that clears R2, bootstraps SQL, normalizes media, and re-seeds content.
+**Sandbox Reset** — The 15-minute cron job at `/api/cron/reset-sandbox` that clears R2, bootstraps SQL, normalizes media, and re-seeds content.
 
 **Scope Tag** — An Nx project tag (`scope:public` or `scope:premium`) validated by the `@nx/enforce-module-boundaries` ESLint rule. See Section 9.1.5.
 
@@ -12430,10 +12421,10 @@ The appendices above synthesize material from the following sections of this spe
 
 - `libs/environment.d.ts` — Typed `NodeJS.ProcessEnv` augmentation used to enumerate every environment variable listed in Section 9.1.1
 - `.env.example` — Environment variable inventory and sample values cross-checked against the typed augmentation
-- `libs/db/src/supabase/migrations/00000000000000_setup_foundation_and_enums.sql` — `user_role` enum definition
-- `libs/db/src/supabase/migrations/00000000000002_setup_content_tables.sql` — `page_status`, `menu_location`, `revision_type` enum definitions
-- `libs/db/src/supabase/migrations/00000000000003_setup_catalog_and_licensing.sql` — `product_type`, `payment_provider` enum definitions
-- `libs/db/src/supabase/migrations/00000000000004_setup_fulfillment_shipping_taxes_and_currencies.sql` — `order_status`, `tax_calculation_mode`, `inventory_deduction_method` enum definitions
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — `user_role` enum definition
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — `page_status`, `menu_location`, `revision_type` enum definitions
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — `product_type`, `payment_provider` enum definitions
+- `libs/db/src/supabase/migrations/02001_baseline_schema.sql` — `order_status`, `tax_calculation_mode`, `inventory_deduction_method` enum definitions
 - `libs/db/src/supabase/config.toml` — Supabase local port allocation reproduced in Section 9.1.9
 - `apps/nextblock/proxy.ts` — Security header set (Section 9.1.12), prefetch priority mapping (Section 9.1.13), CSP nonce, structured cache observability log schema
 - `apps/nextblock/app/layout.tsx` — `PUBLIC_LAYOUT_REVALIDATE_SECONDS` constant reproduced in SLA ledger