Rebuild admin pages around DataTable/AdminModal; restructure categories/groups and v2 groups API

Remove the generic $lib/svelte-admin CRUD layer and AdminTable.svelte; each
admin route now owns its own form/modal logic. Add DataTable.svelte,
superform-errors.ts, and profile-specific modal/field components.

Flatten proclamation categories/groups and drop subscription levels; add the
v2 groups API; update v1/v2 endpoints, serializers, auth, and regenerated
Prisma client with the new migrations.

Document the overhaul plan in docs/ADMIN_OVERHAUL.md.

docs/ai/svelte-patterns.md

@@ -36,13 +36,13 @@ Always destructure $props() with defaults.
 Preferred pattern:
 
 let {
-	record = {} as Record<string, unknown>,
-	fieldErrors = {} as Record<string, string>,
-	isSuper = false
+record = {} as Record<string, unknown>,
+fieldErrors = {} as Record<string, string>,
+isSuper = false
 }: {
-	record?: Record<string, unknown>;
-	fieldErrors?: Record<string, string>;
-	isSuper?: boolean;
+record?: Record<string, unknown>;
+fieldErrors?: Record<string, string>;
+isSuper?: boolean;
 } = $props();
 
 Do not assume props exist.
@@ -66,7 +66,7 @@ Correct:
 let name = $state('');
 
 $effect(() => {
-	name = String(record.name ?? '');
+name = String(record.name ?? '');
 });
 
 Use $effect whenever component state needs to follow changing props.
@@ -88,11 +88,11 @@ Example:
 let dirty = $state(false);
 
 $effect(() => {
-	dirty = false;
+dirty = false;
 });
 
 $effect(() => {
-	name = String(record.name ?? '');
+name = String(record.name ?? '');
 });
 
 This ensures a new record starts clean.
@@ -116,9 +116,10 @@ This can fail to update correctly.
 Use:
 
 <select onchange={(e) => frequency = e.currentTarget.value}>
-	<option value="1" selected={frequency === '1'}>
-		One
-	</option>
+
+<option value="1" selected={frequency === '1'}>
+One
+</option>
 </select>
 
 Use selected on options.