fix: revalidate /customize (not /settings) after customize-panel mutations

The invites/onboarding/areas/roles/tiers admin panels moved to /customize, but
their actions still revalidated the old /settings route, so the /customize
Router Cache went stale after a write. Point them at /customize (keeping the
other cross-page revalidations).

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

lib/actions/areas.ts

@@ -41,7 +41,7 @@ export async function createArea(formData: {
 
   if (error) return { error: error.message }
 
-  revalidatePath('/settings')
+  revalidatePath('/customize')
   revalidatePath('/tasks')
   revalidatePath('/projects')
   revalidatePath('/ops')
@@ -75,7 +75,7 @@ export async function updateArea(formData: {
 
   if (error) return { error: error.message }
 
-  revalidatePath('/settings')
+  revalidatePath('/customize')
   revalidatePath('/tasks')
   revalidatePath('/projects')
   revalidatePath('/ops')
@@ -103,7 +103,7 @@ export async function deleteArea(areaId: string) {
 
   if (error) return { error: error.message }
 
-  revalidatePath('/settings')
+  revalidatePath('/customize')
   revalidatePath('/tasks')
   revalidatePath('/projects')
   revalidatePath('/ops')