Commit release build artifacts for admin, user-app, and API.

Refresh hashed frontend bundles and the API release bundle after build:release.

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

apps/api/release/vendor/.prisma/client/deno/edge.d.ts

@@ -1,9 +0,0 @@
-class PrismaClient {
-  constructor() {
-    throw new Error(
-      '@prisma/client/deno/edge did not initialize yet. Please run "prisma generate" and try to import it again.',
-    )
-  }
-}
-
-export { PrismaClient }

apps/api/release/vendor/.prisma/client/package.json

@@ -1,5 +1,5 @@
 {
-  "name": "prisma-client-2865f0245bc905fafa9ec2b299c03c4ad7a157188246b5449e2f920f2b3a6c3d",
+  "name": "prisma-client-86c4201ec5d85046e85296e9de2d6ef3f60a1f01ce3e33d5e30cbeb3cd52c16a",
   "main": "index.js",
   "types": "index.d.ts",
   "browser": "index-browser.js",

apps/api/release/vendor/.prisma/client/schema.prisma

@@ -1428,16 +1428,16 @@ model CustomerOtp {
 /// so it is **kept and never written to or deleted from** (DEAD-07).
 ///
 /// It is declared here purely so `prisma migrate diff` stops proposing
-/// `DROP TABLE "_goldbank_migrations"` — an undeclared table reads as drift.
+/// `DROP TABLE "_hedenagold_migrations"` — an undeclared table reads as drift.
 /// `@@ignore` keeps it out of Prisma Client: nothing in the application should
 /// ever read or write it, and Prisma Migrate will not manage its shape either.
 ///
 /// Prisma's own ledger is `_prisma_migrations`, which is separate and is never
 /// edited by hand (D14).
-model goldbank_migrations {
+model hedenagold_migrations {
   name      String   @id
   appliedAt DateTime @default(now()) @map("applied_at") @db.Timestamptz(6)
 
-  @@map("_goldbank_migrations")
+  @@map("_hedenagold_migrations")
   @@ignore
 }