docs: update create-prisma compute template support

Author: AmanVarshney01

prisma-compute/references/create-prisma.md

@@ -27,11 +27,11 @@ Use `create-prisma@latest` for new-project scaffolding after verifying `--deploy
 | `tanstack-start` | Yes | Yes |
 | `nest` | Yes | No |
 | `svelte` | Yes | No |
-| `astro` | Yes | Verify current release |
-| `nuxt` | Yes | Verify current release |
-| `turborepo` | Yes | Verify current release; config target is usually `api` |
+| `astro` | Yes | Yes |
+| `nuxt` | Yes | Yes |
+| `turborepo` | Yes | Yes; config target is usually `api` |
 
-The distinction matters: a template can be scaffold-ready while deploy/config generation is still rolling out. Check generated `package.json`, `prisma.compute.ts`, and README instead of assuming from the template name alone.
+The distinction matters for non-latest releases: a template can be scaffold-ready while deploy/config generation differs by version. Check generated `package.json`, `prisma.compute.ts`, and README instead of assuming from the template name alone.
 
 ## Basic Commands
 

prisma-compute/references/frameworks.md

@@ -340,11 +340,11 @@ Use these notes only when the project was scaffolded with `create-prisma` or the
 | `tanstack-start` | Yes | Yes | `prisma.compute.ts` or flag-backed `--framework tanstack-start` script |
 | `nest` | Yes | No | scaffold only |
 | `svelte` | Yes | No | scaffold only |
-| `astro` | Yes | Verify current release | `prisma.compute.ts` with `framework: "astro"` when generated |
-| `nuxt` | Yes | Verify current release | `prisma.compute.ts` with `framework: "nuxt"` when generated |
-| `turborepo` | Yes | Verify current release | `prisma.compute.ts` with `apps.api`; script may run `app deploy api` |
+| `astro` | Yes | Yes | `prisma.compute.ts` with `framework: "astro"` |
+| `nuxt` | Yes | Yes | `prisma.compute.ts` with `framework: "nuxt"` |
+| `turborepo` | Yes | Yes | `prisma.compute.ts` with `apps.api`; script may run `app deploy api` |
 
-The distinction matters: generated deploy/config support is rolling out independently from template scaffolding. Inspect the generated `package.json`, `prisma.compute.ts`, and README before assuming support from the template name alone. Existing apps should still be evaluated against the current `@prisma/cli app deploy` surface.
+The distinction matters for non-latest releases: generated deploy/config support can differ from template scaffolding. Inspect the generated `package.json`, `prisma.compute.ts`, and README before assuming support from the template name alone. Existing apps should still be evaluated against the current `@prisma/cli app deploy` surface.
 
 The generated templates import Prisma Client from local generated paths such as:
 

prisma-compute/scripts/verify-compute-surface.mjs

@@ -16,7 +16,10 @@ const checks = [
       ["has hono template", /\bhono\b/i],
       ["has elysia template", /\belysia\b/i],
       ["has next template", /\bnext\b/i],
+      ["has astro template", /\bastro\b/i],
+      ["has nuxt template", /\bnuxt\b/i],
       ["has tanstack-start template", /\btanstack-start\b/i],
+      ["has turborepo template", /\bturborepo\b/i],
     ],
   },
   {