Brief: D3 R2 — update Bun init E2E

Task

Fix the related CI failure in Client E2E shard 1: prisma-init-bun still asserts and reads prisma.config.ts, while the settled init contract now generates prisma7.config.ts. Update the fixture's test name, file lookup, and expected content/snapshot as needed so it verifies the new canonical filename under Bun without weakening its existing config-content assertions.

Scope

In: packages/client/tests/e2e/prisma-init-bun/ only, plus narrow directly generated fixture metadata if its focused E2E requires it.

Out: Runtime implementation, other E2E suites, unrelated snapshot churn, dependency changes, test installation behavior, and project/review artifacts.

Completed when

• The Bun E2E reads and asserts prisma7.config.ts, no longer expects prisma.config.ts, and still verifies generated config content.
• pnpm --filter @prisma/client test:e2e --verbose --runInBand prisma-init-bun passes.
• Focused lint/Prettier, diff check, and transient-ID scan pass; change is explicitly staged and committed.

Operational metadata

• Model tier: mid — focused fixture correction with one behavior-level assertion.
• Time-box: 30 minutes.
• Halt conditions: Halt if the failure is not fully explained by the filename change, if fixing it requires product code changes, or if the focused Docker E2E exposes another unrelated failure.

Carry-over

CI job 94539661296 failed because /test/prisma-init-bun/tests/prisma.config.test.ts called fs.readFile('./prisma.config.ts') after init successfully listed prisma7.config.ts.

Return shape

Report exact edits, focused E2E and formatting results, commit SHA, and any surprises. Write heartbeat; do not edit project/review artifacts, amend, or push.