Seed Data Parity: Dev ↔ Prod

The Problem

Dev and prod can drift out of sync because:

Config data seeds are blocked on prod. seedBrands, seedVideos, and seedEntitlements all call assertNotProduction(), but they contain reference/config data that prod actually needs (brand dropdowns, video blog, vendor plans).
No single command seeds all config data. You have to remember 6+ separate npx convex run commands and their order.
Config seeds aren't truly idempotent. They check "does any record exist?" and bail entirely. If templates change in code, you have to manually clear* then re-seed — easy to forget on one environment.

What's Config Data vs Demo Data

Type	Tables	Should run on prod?
Config	`defaultTaskTemplates`, `defaultQuestionTemplates`, `defaultQuestionTemplateOptions`, `qualificationTemplates`, `vendorPlans`, `planEntitlementRules`, `accountStatusModifierRules`, `brands`, `videos`, `homepageContent`	Yes
Demo	`users` (demo accounts), `growers`, `vendors`, `trials`, `products`, `trialParticipants`, `shipments`, etc. created by `seedAccounts`/`seedDemoAdmin`/`seedDemoGrower`	No

Changes to Make

1. Remove `assertNotProduction()` from config seeds

These files call it but shouldn't:

convex/seed/seedBrands.ts — Remove from seedBrands handler
convex/seed/seedVideos.ts — Remove from seedVideos handler
convex/seed/seedEntitlements.ts — Remove from seedEntitlements handler

seedDefaultTasks, seedDefaultQuestions, and seedDefaultQualifications already don't have the guard — no change needed.

2. Make config seeds upsert by name instead of skip-if-any-exist

Currently every config seed does this:

const existing = await ctx.db.query("someTable").first();
if (existing) return "already exists";

This means if one record exists, the entire seed is skipped — even if new templates were added to the code. Change each to upsert by name/key:

seedDefaultTasks.ts — For each task in DEFAULT_TASKS:

const existing = await ctx.db
  .query("defaultTaskTemplates")
  .filter((q) => q.eq(q.field("name"), task.name))
  .first();

if (existing) {
  await ctx.db.patch(existing._id, { ...task, updatedAt: now });
} else {
  await ctx.db.insert("defaultTaskTemplates", { ...task, createdAt: now, updatedAt: now });
}

seedDefaultQuestions.ts — Same pattern, match on name:

const existing = await ctx.db
  .query("defaultQuestionTemplates")
  .filter((q) => q.eq(q.field("name"), question.name))
  .first();

if (existing) {
  await ctx.db.patch(existing._id, { ...questionData, updatedAt: now });
  // Delete + recreate options for this template
} else {
  // Insert template + options
}

seedDefaultQualifications.ts — Same pattern, match on name.

seedBrands.ts — Already somewhat handled (skip-if-any), but should upsert per slug:

const existing = await ctx.db
  .query("brands")
  .withIndex("by_slug", (q) => q.eq("slug", brand.slug))
  .first();

if (existing) {
  await ctx.db.patch(existing._id, { name: brand.name, category, updatedAt: now });
} else {
  await ctx.db.insert("brands", { ...brand, category, isActive: true, createdAt: now, updatedAt: now });
}

Note: seedEntitlements already upserts correctly — no change needed there.

3. Create a unified `seedConfigData` action

Create convex/seed/seedConfigData.ts:

import { action } from "../_generated/server";
import { api, internal } from "../_generated/api";

/**
 * Seed all config/reference data. Safe to run on both dev and prod.
 * Idempotent — upserts everything, never duplicates.
 *
 * Run with: npx convex run seed/seedConfigData:seedConfigData
 * For prod: npx convex run --prod seed/seedConfigData:seedConfigData
 */
export const seedConfigData = action({
  args: {},
  handler: async (ctx) => {
    const results: Record<string, unknown> = {};

    // 1. Entitlements (plans + rules + modifiers)
    results.entitlements = await ctx.runMutation(api.seed.seedEntitlements.seedEntitlements, {});

    // 2. Default task templates
    results.tasks = await ctx.runMutation(api.seed.seedDefaultTasks.seedDefaultTasks, {});

    // 3. Default question templates
    results.questions = await ctx.runMutation(api.seed.seedDefaultQuestions.seedDefaultQuestions, {});

    // 4. Default qualification templates
    results.qualifications = await ctx.runMutation(
      api.seed.seedDefaultQualifications.seedDefaultQualifications, {}
    );

    // 5. Brands
    results.brands = await ctx.runMutation(api.seed.seedBrands.seedBrands, {});

    // 6. Videos
    results.videos = await ctx.runMutation(api.seed.seedVideos.seedVideos, {});

    // 7. Homepage content
    results.homepage = await ctx.runMutation(internal.homepage.seedDefaultHomepageContent, {});

    return { success: true, results };
  },
});

4. Update the seed run order docs

After these changes, the full setup for either environment is:

# Config data (safe on both dev and prod)
npx convex run seed/seedConfigData:seedConfigData

# Demo accounts (dev only — blocked on prod by assertNotProduction)
npx convex run seed/seedAccounts:seedAccounts
npx convex run seed/seedDemoAdmin:seedDemoAdmin
npx convex run seed/seedDemoGrower:seedDemoGrower

For prod, just the config:

npx convex run --prod seed/seedConfigData:seedConfigData

Checklist

Remove assertNotProduction() from seedBrands, seedVideos, seedEntitlements
Change seedDefaultTasks to upsert by name instead of skip-if-any-exist
Change seedDefaultQuestions to upsert by name (and recreate options)
Change seedDefaultQualifications to upsert by name
Change seedBrands to upsert by slug
Create convex/seed/seedConfigData.ts unified action
Run seedConfigData on prod to backfill any missing config data
Update convex/seed/CLAUDE.md with the new commands