feat: add prisma.compute.json configs and templates manifest to Compute examples

[AmanVarshney01]

Summary

Makes the three Prisma Compute examples (deployment-platforms/prisma-compute/{hono,nextjs,tanstack-start}) usable as click-to-deploy template sources for the Console gallery, in their current location.

• Adds a minimal prisma.compute.json to each example (name, framework, and httpPort: 8080 for hono which reads PORT ?? 8080). A repo/folder carrying this config connects and deploys through the platform import flow with no inference. All three configs validated against the compute SDK's loadComputeConfig.
• Adds templates.json, the manifest a gallery consumer reads (id, name, description, repo-root-relative path, framework).
• Prepends prisma generate to each example's build script: the generated client is gitignored, so a fresh copy of these folders previously could not build without the reader knowing to run db:generate first. Verified all three build from a clean generate.

The documented CLI flow (compute:deploy scripts) is unchanged; the --env .env flag still applies on top of the config.

Testing

• loadComputeConfig from @prisma/compute-sdk source resolves all three configs (hono: framework hono, port 8080; others: framework defaults)
• bun run build succeeds from a clean generated-client state in all three examples with DATABASE_URL set

Summary by CodeRabbit

• New Features

  • Added deployment templates for Hono, Next.js, and TanStack Start applications.
  • Added platform configuration for application names, frameworks, and HTTP settings.
  • Added a centralized template catalog for discovering supported deployment options.

• Bug Fixes

  • Builds now generate the Prisma client before compiling or bundling, improving build reliability across supported frameworks.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 20ff41ea-ab7e-4df4-9e0c-d7b3c8661a83

📥 Commits

Reviewing files that changed from the base of the PR and between 6d44921 and 369b26e.

📒 Files selected for processing (7)

• deployment-platforms/prisma-compute/hono/package.json
• deployment-platforms/prisma-compute/hono/prisma.compute.json
• deployment-platforms/prisma-compute/nextjs/package.json
• deployment-platforms/prisma-compute/nextjs/prisma.compute.json
• deployment-platforms/prisma-compute/tanstack-start/package.json
• deployment-platforms/prisma-compute/tanstack-start/prisma.compute.json
• deployment-platforms/prisma-compute/templates.json

---

Walkthrough

Prisma Compute configurations and template metadata were added for Hono, Next.js, and TanStack Start. Their build scripts now run prisma generate before the existing framework-specific build command.

Changes

Prisma Compute platform templates

Layer / File(s)	Summary
Framework app definitions and build generation deployment-platforms/prisma-compute/{hono,nextjs,tanstack-start}/...	Each platform now has Prisma Compute metadata, and each build script generates Prisma artifacts before compilation or framework bundling.
Template registry deployment-platforms/prisma-compute/templates.json	A versioned registry defines the Hono, Next.js, and TanStack Start deployment templates with their identifiers, paths, descriptions, and framework labels.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the added Prisma Compute configs and templates manifest, matching the main change set.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

_{Comment @coderabbitai help to get the list of available commands.}