/**
 * Backfill the walk-in QR permissions for admins who predate them.
 *
 * Context. Before the walk-in QR permission split, creating / editing /
 * deleting a walk-in QR required canManageSettings — every write route was
 * gated by requireFlag('canManageSettings'). The split introduced three
 * dedicated flags (canViewWalkInQr / canAddWalkInQr / canDeleteWalkInQr),
 * each defaulting to false, and restored access in migration SQL.
 *
 * Two gaps that left admins without the "New QR" button they used to have:
 *   1. The migration backfilled from the visitor flags (canAddVisitors /
 *      canDeleteVisitors) rather than the gate that was actually in force,
 *      canManageSettings.
 *   2. Environments whose schema is applied with `prisma db push` never run
 *      migration SQL at all, so no backfill happened there.
 *
 * This script closes both. It only ever grants — nothing is revoked — so it
 * is safe to re-run, and safe on an environment where the migrations did
 * apply cleanly.
 *
 * Dry run (default):  npx ts-node -r dotenv/config src/scripts/backfillWalkInQrPermissions.ts
 * Apply:              npx ts-node -r dotenv/config src/scripts/backfillWalkInQrPermissions.ts --apply
 */
export {};
//# sourceMappingURL=backfillWalkInQrPermissions.d.ts.map