Factory reset accepts reseed: true but cannot re-seed

POST /api/admin/reset accepts a reseed flag but cannot honour it:

    if (reseed) {
        // The seed script uses a top-level async IIFE with its own PrismaClient,
        // so it cannot be cleanly imported. Manual re-seed is required.
        reseeded = false;
    }

It returns note: 'Manual re-seed required. Run: npx prisma db seed'.

Why it matters

Minor, but the API accepts a parameter it silently declines to act on. The caller has to read the response note to discover the reset left an empty database.

Fix

Refactor the seed script to export a callable seed(prisma) function, keeping the IIFE only as the CLI entry point, then call it from the reset route. That makes reseed: true mean what it says.

Start by locating the seed script and the POST /api/admin/reset route described in the issue. Refactor the seed script around a callable seed(prisma) entry point while retaining its CLI entry point, then have the reset route invoke it for reseed: true and verify the response no longer reports that manual re-seeding is required.