Fix Vercel deploy: sanitize Sentry release + drop Next.js framework preset

1) @sentry/rollup-plugin release was '@hexclave/[email protected]' — sentry-cli rejects '/' in release names; sanitize to '@[email protected]'. 2) Vercel still used the Next.js framework preset and failed looking for .next/routes-manifest.json; set framework:null since the backend is now a tsdown bundle, not a Next build.

apps/backend/tsdown.config.ts

@@ -63,7 +63,8 @@ const nextCompatPlugin: Rolldown.Plugin = {
     return nextCompatAliases.get(source) ?? null;
   },
 };
-const sentryRelease = process.env.SENTRY_RELEASE ?? `${packageJson.name}@${packageJson.version}`;
+// Sentry release names may not contain slashes/whitespace, so sanitize the scoped package name.
+const sentryRelease = process.env.SENTRY_RELEASE ?? `${packageJson.name}@${packageJson.version}`.replace(/[/\s]/g, "-");
 const shouldUploadSourcemaps = process.env.SENTRY_ORG != null
   && process.env.SENTRY_PROJECT != null
   && process.env.SENTRY_AUTH_TOKEN != null;

apps/backend/vercel.json

@@ -1,5 +1,6 @@
 {
   "$schema": "https://openapi.vercel.sh/vercel.json",
+  "framework": null,
   "crons": [
     {
       "path": "/api/latest/internal/email-queue-step",