## Summary

User-visible CLI surfaces still said "Prisma Next" after the rename.
This changes them to **"Prisma ORM"**, which is version-independent —
these strings do not need revisiting at each major release.

Fixes #30062

## Surfaces changed

- `orm init` command summary and its bug-report string
- `lsp` command summary and description
- The scaffolded quick-reference templates (postgres + mongo)
- The scaffolded `README.md` templates (postgres + mongo)
- The telemetry first-run consent notice — the first branded sentence a
new user sees
- The three config-validation diagnostics (`No Prisma ORM configuration
was loaded`, etc.)
- The two install-fallback warnings printed during `orm init`
- The remaining internal doc comments in `cli/src`, so the source uses
one name throughout

After this change there is no occurrence of "Prisma Next" anywhere in
`packages/1-framework/3-tooling/cli/src`.

## Deliberately unchanged

- `QUICK_REFERENCE_FILE = 'prisma-next.md'` and every reference to it
*by filename*. This is covered by the standing allowance at
`scripts/lint-legacy-name.mjs:60`, which names the file specifically and
tracks its removal to **ROADMAP § 3**. The filename/greeting mismatch is
a known, tracked interim state.
- `TELEMETRY_DOCS_URL` and the `prisma-next.dev` URLs — live
infrastructure, not brand strings.
- `PRISMA_NEXT_DISABLE_TELEMETRY` — renaming it would break existing
opt-outs.
- The `// use prisma-next` schema directive — a language construct, same
allowance.
- Legacy skill slugs in `skill-sources.ts`.

The issue's fourth complaint (skills labeled "Prisma Next agent-skill")
is **moot**: `orm init` no longer installs skills at all
(`commands/init/skill-sources.ts:1-5`).

## Follow-ups, not in this PR

- Runtime error strings in the target packs still say "Prisma Next":
`packages/3-targets/3-targets/postgres/src/core/migrations/runner.ts:322`,
`issue-planner.ts:516`,
`packages/3-targets/3-targets/sqlite/src/core/migrations/runner.ts:335`.
A different surface, not raised by the issue.
- Package READMEs and `package.json` descriptions across
`packages/3-targets/**` and `packages/3-extensions/**` — explicitly
deferred by the issue ("internal package names, repo docs … can lag").

## Testing

Verified against the built bin rather than the diff: all help screens
render "Prisma ORM" and contain no "Prisma Next"; a real `orm init`
scaffold produces 11 "Prisma ORM" occurrences across `README.md` and
`prisma-next.md` and zero legacy ones.

- CLI package suite: 115 files, 1436 tests, green
- Init-related integration tests (`cli.init-templates`,
`cli.init-facade-imports`, `cli.init-skill-distribution`,
`cli.config-section-requirements`, `cli.bin-smoke`): 5 files, 37 tests,
green
- `node scripts/lint-legacy-name.mjs`: clean
- `pnpm lint` and `pnpm typecheck`: clean

Per review feedback, the two rename-assertion tests added earlier were
removed rather than adjusted — they only asserted the absence of strings
this PR deletes, which is not coverage worth carrying. The existing
template snapshots already pin the scaffolded output.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01UcqoY3CKfnubdZt5YQk2Rq


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Updated CLI help text, diagnostics, telemetry notices, and generated
MongoDB/PostgreSQL templates to consistently use “Prisma ORM” branding.
* Refreshed related setup guidance, sample descriptions, headings, and
references across generated documentation.
* Clarified terminology in control API and ORM configuration
documentation.
* **Tests**
* Updated diagnostic expectations to reflect the “Prisma ORM”
terminology.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Steven McClankerton <tatarintsev@prisma.io>
Co-authored-by: Steven McClankerton <tatarintsev@prisma.io>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>