fix(settings): restrict superadmin template to can_edit=0 keys only

Superadmin was seeding all deploy_settings_const INSERT keys including
can_edit=1 entries with wrong defaults (e.g. montzar_product_id=25).
Template/catalog now follow final can_edit=0 from SQL; editable keys are
purged from setting_templates and tenant settings on boot/seed.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
2026-08-19 18:40:07 +03:30
co-authored by Cursor
parent 0b2e4b05f9
commit 71d6f6a534
6 changed files with 958 additions and 1589 deletions
+2 -1
View File
@@ -38,7 +38,8 @@
"replicas:sync": "bash deploy/sync-replica-schema.sh && bash deploy/sync-replica-data.sh --repair-if-needed",
"replicas:check": "bash deploy/sync-replica-schema.sh --check && bash deploy/sync-replica-data.sh --check",
"replicas:repair-data": "bash deploy/sync-replica-data.sh --repair",
"settings:seed-templates": "echo 'Templates seed on first GET /api/setting-templates or POST /api/setting-templates/seed'"
"settings:sync-template": "node scripts/sync-superadmin-setting-template.mjs",
"settings:seed-templates": "echo 'Templates seed on server boot or POST /api/setting-templates/seed'"
},
"prisma": {
"seed": "ts-node --transpile-only prisma/seed.ts"