feat(settings): store Khanegi keys in settings tables instead of tenant JSON

Template defaults seed from deploy_settings_const; new tenants copy them, import decides per key, and /get_settings reads the per-tenant rows.

Co-authored-by: Cursor <cursoragent@cursor.com>

package.json

@@ -36,7 +36,8 @@
     "prisma:copy-sms-between-tenants": "ts-node --transpile-only prisma/copy-sms-between-tenants.ts",
     "prisma:list-tenants": "ts-node --transpile-only prisma/list-tenants.ts",
     "replicas:sync": "bash deploy/sync-replica-schema.sh",
-    "replicas:check": "bash deploy/sync-replica-schema.sh --check"
+    "replicas:check": "bash deploy/sync-replica-schema.sh --check",
+    "settings:seed-templates": "echo 'Templates seed on first GET /api/setting-templates or POST /api/setting-templates/seed'"
   },
   "prisma": {
     "seed": "ts-node --transpile-only prisma/seed.ts"