fix: fall back to SANITY_API_WRITE_TOKEN if SANITY_API_TOKEN is missing

Vercel has SANITY_API_WRITE_TOKEN from the original project setup.
Our code uses SANITY_API_TOKEN. Now checks both for compatibility.

Author: Miriad

lib/sanity-write-client.ts

@@ -2,13 +2,14 @@ import { createClient } from "next-sanity";
 
 import { apiVersion, dataset, projectId } from "@/sanity/lib/api";
 
-// Server-side Sanity client with write access (uses SANITY_API_TOKEN)
+// Server-side Sanity client with write access
+// Checks SANITY_API_TOKEN first, falls back to SANITY_API_WRITE_TOKEN for compatibility
 export const sanityWriteClient = createClient({
 	projectId,
 	dataset,
 	apiVersion,
 	useCdn: false,
-	token: process.env.SANITY_API_TOKEN,
+	token: process.env.SANITY_API_TOKEN || process.env.SANITY_API_WRITE_TOKEN,
 });
 
 // Alias for compatibility

lib/sanity/dashboard.ts

@@ -9,7 +9,7 @@ import { projectId, dataset, apiVersion } from "@/sanity/lib/api";
  * Returns null if SANITY_API_TOKEN is not set (e.g., during build).
  */
 function createDashboardClient(): SanityClient | null {
-	const token = process.env.SANITY_API_TOKEN;
+	const token = process.env.SANITY_API_TOKEN || process.env.SANITY_API_WRITE_TOKEN;
 	if (!token) {
 		console.warn(
 			"SANITY_API_TOKEN not set — dashboard queries will return empty results",

lib/services/video-pipeline.ts

@@ -54,7 +54,7 @@ interface SponsorLeadDocument {
 // --- Sanity Write Client ---
 
 function getSanityWriteClient(): SanityClient {
-  const token = process.env.SANITY_API_TOKEN;
+  const token = process.env.SANITY_API_TOKEN || process.env.SANITY_API_WRITE_TOKEN;
   if (!token) {
     throw new Error('[VIDEO-PIPELINE] Missing SANITY_API_TOKEN environment variable');
   }