Project provisioning creates the platform default database — use the endpoint that doesn't

[wmadden-electric]

Every composer-provisioned project shows an extra, unused database in the Console: the platform default DB, named after the project. Composer already treats it as forbidden — it poisons DATABASE_URL/DATABASE_URL_POOLED with - at provision (docs/design/05-prisma-cloud/alchemy-lowering.md, packages/1-prisma-cloud/1-extensions/target/src/serializer.ts) — so the DB exists only to be quarantined.

Per the PDP team, the management API has a separate project-creation endpoint that does not create the default database. Composer appears to be calling the default-creating one; switching removes the need for the poison mechanism on new projects and stops the Console clutter.

Concrete harm observed while dogfooding (prisma/migration-runner): the default DB carries the friendly project name (e.g. notes-example) while the app's real database shows its provision id (database), so a user picking a migration target in the Console naturally picks the wrong DB. Tracked on the platform side as PFR-35.

🤖 Generated with Claude Code

[wmadden]

Validated against the management-api source: not a separate endpoint — POST /v1/projects takes createDatabase (default true; in the SDK types). Composer omits it (container.ts:88 in the lowering package), so the fix is one line: createDatabase: false. The no-DB path 403s user actors; composer deploys are workspace actors, so fine. Default DB naming comes from databaseDisplayName: name.