docs: aggregate CLI error codes from prisma/prisma-cli (#8184)

* docs: aggregate CLI error codes from prisma/prisma-cli

Extends the error-reference pipeline (generator + daily sync + completeness
check) to a second source repo, following the same pattern used for
prisma/prisma. The CLI gets its own page at /docs/cli/error-reference
because the CLI.* namespace exists in both repos with different meanings
(CLI.PROMPT_REQUIRED collides).

- generate-error-reference.mjs takes --target orm|cli; orm output is
  unchanged
- both workflows also check out prisma/prisma-cli and run its own
  scripts/list-error-codes.mjs to verify page completeness, exactly as
  they do with prisma/prisma's scanner
- the generated CLI page (128 codes) is committed, with a sidebar entry
  under the CLI section's Introduction group
- next.config.mjs redirects the path form …/error-reference/<CODE> to
  the #<CODE> anchor for both the ORM and CLI pages — the CLI engine
  composes docsUrls in path form from a family docsBaseUrl, and the ORM
  family's links were 404ing on this before

Companion PR (must merge first): prisma/prisma-cli#234, which adds the
canonical registry and scanner this consumes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

* docs: regenerate the CLI error page after the upstream cleanup

prisma/prisma-cli#234 removed the code-rewriting boundary layer, so the
registry no longer documents a passthrough rule and no longer carries the
two entries that had no raise site. 128 codes -> 126.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

* docs: sync the ORM error reference with prisma/prisma main

The completeness check caught real upstream drift: MIGRATION.PLAN_ORIGIN_UNKNOWN
shipped in prisma/orm#30122 and the page had not been regenerated since.
Also picks up wording changes in three existing entries.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

* docs: teach the spellchecker the CLI error page's real terms

Two genuine names the dictionary lacked: stricli (the argument parser the
engine wraps) and UNWRITABLE (part of the INIT.CONFIG_UNWRITABLE and
INIT.PACKAGE_JSON_UNWRITABLE codes), alongside the existing UNLOADABLE and
UNPARSEABLE entries.

The page itself is regenerated after prisma/prisma-cli fixed four British
spellings and one invented word at the source, rather than adding those to
the dictionary here.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

* docs: publish the CLI error page with the site's REST API name

The docs site does not reintroduce "Management API" in prose (see
apps/docs/CLAUDE.md); prisma-cli uses that name because the SDK it calls
through is literally `@prisma/management-api-sdk`, which is right in that
repo. The generator already exists to bridge that kind of mismatch for the
ORM target, so the CLI target gets the same treatment: 13 prose occurrences
become "REST API".

The rewrite skips fenced blocks and inline code spans, so identifiers keep
their real names — the exception apps/docs/CLAUDE.md calls out.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

* docs: treat every markdown code form as opaque in the generator

The prose rewriter recognized only triple-backtick fences and single-backtick
spans, so a tilde fence or a multi-backtick span would have had its contents
rewritten — the identifiers the rewrite exists to protect.

assertMdxSafe had the same blind spot from the other direction: a brace inside
a tilde fence looked like unescaped MDX and would have failed the build for
text that is only ever displayed.

Both now read one CODE_SEGMENT covering backtick and tilde fences and spans of
any delimiter length, and the rewriter walks matches instead of splitting, so
it no longer depends on the pattern having exactly one capture group.

Verified against both fence styles, one/two/three-backtick spans, and mixed
prose; both pages regenerate byte-identically.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

---------

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Ankur Datta <64993082+ankur-arch@users.noreply.github.com>

Author: 3 people

.github/workflows/error-reference-check.yml

@@ -1,9 +1,10 @@
 name: Error Reference Check
 
-# The published error-reference page must list every structured error code the
-# product (prisma/prisma main) can emit — each emitted error links to
-# /docs/orm/reference/error-reference#<CODE>. This check fails if any
-# known code is missing from the page, even if the sync workflow breaks.
+# The published error-reference pages must list every structured error code
+# the products can emit — prisma/prisma (main) errors link to
+# /docs/orm/reference/error-reference#<CODE>, prisma/prisma-cli (main) errors
+# to /docs/cli/error-reference#<CODE>. This check fails if any known code is
+# missing from its page, even if the sync workflow breaks.
 #
 # Runs on pushes to main, on PRs that touch the page or its tooling, and on a
 # daily schedule so drift introduced upstream is flagged without blocking
@@ -15,6 +16,7 @@ on:
   pull_request:
     paths:
       - apps/docs/content/docs/orm/reference/error-reference.mdx
+      - apps/docs/content/docs/cli/error-reference.mdx
       - apps/docs/scripts/generate-error-reference.mjs
       - .github/workflows/error-reference-check.yml
       - .github/workflows/sync-error-reference-docs.yml
@@ -43,10 +45,21 @@ jobs:
           path: prisma-src
           persist-credentials: false
 
+      - name: Checkout prisma/prisma-cli (main)
+        uses: actions/checkout@v4
+        with:
+          repository: prisma/prisma-cli
+          ref: main
+          path: prisma-cli-src
+          persist-credentials: false
+
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
           node-version: "20"
 
-      - name: Verify page lists every known error code
+      - name: Verify ORM page lists every known error code
         run: node prisma-src/scripts/list-error-codes.mjs --root prisma-src --verify apps/docs/content/docs/orm/reference/error-reference.mdx
+
+      - name: Verify CLI page lists every known error code
+        run: node prisma-cli-src/scripts/list-error-codes.mjs --root prisma-cli-src --verify apps/docs/content/docs/cli/error-reference.mdx

.github/workflows/sync-error-reference-docs.yml

@@ -32,28 +32,44 @@ jobs:
           path: prisma-src
           persist-credentials: false
 
+      - name: Checkout prisma/prisma-cli (main)
+        uses: actions/checkout@v4
+        with:
+          repository: prisma/prisma-cli
+          ref: main
+          path: prisma-cli-src
+          persist-credentials: false
+
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
           node-version: "20"
 
-      - name: Generate error reference page
+      - name: Generate ORM error reference page
         working-directory: apps/docs
-        run: node ./scripts/generate-error-reference.mjs --source ../../prisma-src/docs/reference/error-reference.md
+        run: node ./scripts/generate-error-reference.mjs --target orm --source ../../prisma-src/docs/reference/error-reference.md
 
-      - name: Verify page lists every known error code
+      - name: Verify ORM page lists every known error code
         run: node prisma-src/scripts/list-error-codes.mjs --root prisma-src --verify apps/docs/content/docs/orm/reference/error-reference.mdx
 
+      - name: Generate CLI error reference page
+        working-directory: apps/docs
+        run: node ./scripts/generate-error-reference.mjs --target cli --source ../../prisma-cli-src/docs/reference/error-reference.md
+
+      - name: Verify CLI page lists every known error code
+        run: node prisma-cli-src/scripts/list-error-codes.mjs --root prisma-cli-src --verify apps/docs/content/docs/cli/error-reference.mdx
+
       - name: Check for changes
         id: changes
         run: |
-          if [[ -z "$(git status --porcelain --untracked-files=all -- apps/docs/content/docs/orm/reference/error-reference.mdx)" ]]; then
-            echo "changed=false" >> $GITHUB_OUTPUT
+          PAGES=(apps/docs/content/docs/orm/reference/error-reference.mdx apps/docs/content/docs/cli/error-reference.mdx)
+          if [[ -z "$(git status --porcelain --untracked-files=all -- "${PAGES[@]}")" ]]; then
+            echo "changed=false" >> "$GITHUB_OUTPUT"
             echo "No changes detected"
           else
-            echo "changed=true" >> $GITHUB_OUTPUT
+            echo "changed=true" >> "$GITHUB_OUTPUT"
             echo "Changes detected:"
-            git status --short -- apps/docs/content/docs/orm/reference/error-reference.mdx
+            git status --short -- "${PAGES[@]}"
           fi
 
       - name: Commit and push
@@ -65,7 +81,7 @@ jobs:
         run: |
           git config user.email "prismabots@gmail.com"
           git config user.name "Prismo"
-          git add apps/docs/content/docs/orm/reference/error-reference.mdx
+          git add apps/docs/content/docs/orm/reference/error-reference.mdx apps/docs/content/docs/cli/error-reference.mdx
           git commit -m "chore(docs): sync Prisma 8 error reference"
           git push "https://x-access-token:${BOT_TOKEN}@github.com/${TARGET_REPO}.git" "HEAD:${TARGET_REF}"