Move the resource commands onto the CLI engine, and rename database to postgres

[wmadden-electric]

The CLI is moving onto @prisma/cli-engine, the library that owns a run from argv to exit code. This PR moves 31 resource commands across and renames the database group to postgres.

Here is what "on the engine" means, shown as one command in both of its output lanes:

$ prisma-cli project list
ℹ Listing projects for the authenticated workspace.
workspace: Will's Prisma Workspace
- No projects found.
→ Ask the user whether to link an existing Project or create a new one
→ Link the chosen Project: prisma-cli project link <id-or-name>
→ Create and link a new Project: prisma-cli project create <name>

The identical run with --json:

{
  "ok": true,
  "commandId": "project.list",
  "result": {
    "context": { "workspace": "Will's Prisma Workspace" },
    "items": [],
    "count": 0,
    "localBinding": { "status": "not-linked" }
  },
  "exitCode": 0,
  "diagnostics": [],
  "nextActions": [
    {
      "kind": "run-command",
      "label": "Link the chosen Project",
      "command": "prisma-cli project link <id-or-name>",
      "reason": "Linking writes the durable local Project binding for this directory."
    }
  ]
}

Every command here produces that shape. The human lane and the machine lane are two renderings of one result, not two code paths — so a follow-up step is a typed action with a reason attached rather than a sentence a caller has to parse, and the exit code is part of the result rather than something set on the way out.

Nothing changes for users yet

This is worth saying before anything else, because it sets how much risk is in the diff: the published CLI is unchanged. The package still declares exactly one binary, prisma-cli, still pointing at the old shell. The ported commands run through a second entry point that only exists inside this repo, reached by pnpm prisma-v8 …. Swapping the binary over is a separate, later change.

So this PR adds a parallel implementation and its tests. It does not switch anyone onto it.

What a command looks like now

One file per command, holding both its definition and its handler. The handler does not reimplement any API flow — it calls the same controller and provider functions the old shell calls, through a client the engine constructs and owns.

That is the single most useful thing to know when reading the diff: it is large, but almost none of it is new behaviour. It is command definitions, presentation, and tests, sitting on top of operations that already existed and are unchanged.

What the engine takes over

Errors. Flat codes become dotted ones scoped to their group — PROJECT_NOT_FOUND becomes PROJECT.NOT_FOUND, DATABASE_BACKUP_NOT_FOUND becomes POSTGRES.BACKUP_NOT_FOUND. The wording is carried over as it stands. Two phrases are rewritten because they describe machinery the new runtime does not have: --trace becomes --log-level verbose, and the offer to "rerun the command in a TTY to sign in interactively" is dropped, since there is no auto-login to rerun into.

Exit codes. Every failure now exits 2. Most of these paths exited 1, and a few exited 0 while reporting a problem.

Consent. Seven destructive commands — removing a project or a database, transferring a project, restoring a database, rotating or removing a connection, deleting a bucket — ask you to type the exact resource id. Scripts pass --confirm <id> exactly as before. The difference is that the prompt, the scripted grant and the refusal are now one implementation the engine injects, rather than seven flags each command declared and could drift on. --yes deliberately does not satisfy it.

Waiting. git connect still waits for you to approve a GitHub App installation, but it hands the engine the URL, the question to poll and the cadence, instead of running its own loop. The announcement, the browser open and the clock all live in one place.

Secrets. One-time connection URLs and bucket access keys are the only thing on stdout, so prisma-cli postgres create db | pbcopy gives you the bare URL, while the card printed beside it shows the value masked.

The rename

database becomes postgres throughout: every path, command id, help string, example, and every command reference inside error text. There is no alias to the old name.

The word "database" survives where it is the noun rather than the group — these are still Prisma Postgres databases, and postgres show <database> still takes one.

What is and is not in scope

In: project including project env, postgres including backup and connection, bucket including bucket key, branch list, and git connect|disconnect.

Not in: the service, app, build, agent and feedback groups, init, deleting the old shell, and the binary cutover. The old shell is untouched and still serves everything this PR does not cover.

Reviewing this

Every behavioural difference from the old commands is recorded — one entry per change, one row per command — in parity-divergences-s2b.md. The three most worth arguing with: auto-login is gone, so an unauthenticated run reports it rather than opening a browser; project env remove loses its rm alias; and git connect now refuses to run non-interactively at all, where before it sometimes succeeded.

Three known problems are recorded rather than fixed, because each needs a decision rather than a patch. project list reports an empty workspace at exit 0 when the API actually rejects the request — inherited from the old shell, and it reaches every command that resolves a project by name. git connect refuses non-interactive runs even when no waiting would have been needed. And two stdout values are still formatted for humans, so a pipe consumer cannot use them: a size printed as 2.0 KiB, and a status column that holds a different fact when the status is null.

Changes to existing files: 43 export keywords, no changed function bodies

So the new commands can call code that already exists:

• controllers/app-env.ts — resolveEnvWriteSource, resolveEnvWriteInput, resolveScopeToApi, resolveListScopeToApi, formatScopeFlag, listVariables, listOverviewVariables
• controllers/branch.ts — RawBranchRecord, sortBranches, listBranches, toBranchSummary
• controllers/database.ts — parseUsageDate, parseBackupLimit, resolveDatabase, ensureProjectId, sortDatabases, defaultConnectionName
• controllers/project.ts — GITHUB_INSTALL_POLL_INTERVAL_MS, GITHUB_INSTALL_POLL_TIMEOUT_MS, readProjectListLocalBinding, transferRecipientRequiredError, transferRecipientUnavailableError, cleanupLocalPinForProject, rewriteOrClearLocalPinForProject, InstalledRepositoryMatch, SourceRepositoryApiError, SourceRepositoryApiClient, findRepositoryInInstallations, readPositiveIntegerEnv, listScmInstallations, createGitHubInstallIntent, readFirstSourceRepository, toRepositoryConnection, unsupportedRepositoryProviderError, repoNotConnectedError, repoInstallationRequiredError, repoNotAccessibleError, repoAlreadyConnectedError, repositoryFullNamesMatch, repoConnectionApiError
• presenters/app-env.ts — scopeLabel, listTargetLabel
• presenters/project.ts — formatGitConnectionDetail

The old shell's fixture tests for the ported commands are deleted. Unit tests for helpers and providers the new commands still call are kept.

Alternatives considered

Keeping a database alias. Rejected. The point of the rename is one name per concept, and an alias keeps the old one alive in help, in documentation and in muscle memory indefinitely.

Leaving --confirm on each command. Rejected. That is seven implementations of one prompt, each free to drift, and scripted callers get one consistent behaviour out of the engine version.

Hand-rolling the installation poll in git connect. Rejected. It would duplicate the announcement, the browser open and the clock, and this would have been the third copy of that pattern.

Rewriting the operations onto the engine instead of calling them. Rejected for this PR, and worth explaining because it is the biggest judgement call here. Doing both at once would mix a runtime migration with a behavioural rewrite, and make the parity record above impossible to check — every difference would be attributable to either change. It is also the wrong order: the tests this PR adds are what make a later rewrite safe to attempt, because they pin the behaviour from outside. That rewrite is planned as its own change, before the next group of commands is ported.

[coderabbitai]

Actionable comments posted: 19

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.drive/projects/prisma-cli-v8/specs/s2b-design/conventions.md:
- Around line 263-279: Update the “Tests” harness guidance around createTestCli
and the v8-auth.test.ts reference to remove the required ../src/auth mock and
specify the current ctx.activeCredential() seeding or mocking contract, ensuring
resource-command tests provide the workspace credential source they require.

In @.drive/projects/prisma-cli-v8/specs/s2b-design/d1-project.md:
- Around line 286-291: Remove command-owned confirm flag declarations from
project remove in .drive/projects/prisma-cli-v8/specs/s2b-design/d1-project.md
lines 286-291 and project transfer lines 313-319; remove the declarations from
postgres restore in
.drive/projects/prisma-cli-v8/specs/s2b-design/d2-postgres.md lines 343-345,
postgres remove lines 387-388, postgres connection rotate lines 486-487, and
postgres connection remove lines 520-521. In d2-postgres.md lines 104-122,
replace the obsolete helper, mapper error-code, metadata, and
requirePostgresConfirmation requirements with the parent engine-owned shared
--confirm consent contract.

In @.drive/projects/prisma-cli-v8/specs/s2b-design/d3-bucket-branch-git.md:
- Around line 386-391: Update the test-list bullet in the D3 bucket-branch Git
design document to remove the three-event “endpoint → status waiting → status
connected” assertion and describe the single endpoint event instead, matching
the pinned rule and shipped test behavior. Leave the other listed test cases
unchanged.

In @.drive/projects/prisma-cli-v8/specs/s2b-design/facts/facts-d2-postgres.md:
- Line 44: Correct the statement describing resolveProjectTarget in the Postgres
facts so it no longer claims that PRISMA_PROJECT_ID is allowed or affects these
commands. Document that requireDatabaseContext invokes resolveProjectTarget
without envProjectId, while preserving the listed resolution order and error
mappings.

In
@.drive/projects/prisma-cli-v8/specs/s2b-design/facts/facts-d3-bucket-branch-git.md:
- Around line 1-3: Remove developer-specific absolute workstation and worktree
paths from the facts metadata. In
.drive/projects/prisma-cli-v8/specs/s2b-design/facts/facts-d3-bucket-branch-git.md
lines 1-3, replace the source path with a repository-relative path; make the
same replacement in
.drive/projects/prisma-cli-v8/specs/s2b-design/facts/facts-v8-patterns.md lines
1-3, preserving the surrounding branch and provenance details.

In `@packages/cli/src/v8/bucket/delete.ts`:
- Line 44: Replace the hardcoded binary names in
packages/cli/src/v8/bucket/delete.ts#L44-L44 and both occurrences in
packages/cli/src/v8/git/connect.ts#L181-L182 with CLI_NAME-derived command
strings, following the existing naming pattern so user-facing guidance remains
correct if the published binary name changes.

In `@packages/cli/src/v8/bucket/key-delete.ts`:
- Around line 35-52: Add an exact confirmation gate in the handler before
calling deleteKey, using keyId as the consent token via ctx.prompt.consent;
retain the existing validation and credential requirement. Document the
--confirm <key-id> option for this command and add tests covering successful
matching consent and rejection of missing or mismatched confirmation.

In `@packages/cli/src/v8/bucket/list.ts`:
- Line 40: Sanitize tab and newline characters in every cell before emitting
tab-joined rows. Update the stdout mapping in
packages/cli/src/v8/bucket/list.ts#L40-L40 for bucketRows(result.buckets) and
packages/cli/src/v8/bucket/key-list.ts#L33-L33 for bucketKeyRows(result.keys),
using an identical shared helper in packages/cli/src/v8/bucket/presentation.ts
so downstream pipe consumers receive one stable row per bucket or key.

In `@packages/cli/src/v8/git/connect.ts`:
- Around line 65-97: Initialize inspectableInstallationCount from the first
inspect(ctx.signal) result before handling first.match, while preserving the
existing immediate return for a match. Keep the poll callback updating the count
from later inspections so timeout handling passes the latest known value to
installWaitFailedError and selects the correct error outcome.

In `@packages/cli/src/v8/git/context.ts`:
- Line 34: Document the intentional cast in the return statement of the
surrounding context function: explain that the SDK client supports the required
source-repository paths and request shapes, and that the cast adapts it to the
local narrowed SourceRepositoryApiClient contract. Keep the existing cast and
behavior unchanged.

In `@packages/cli/src/v8/project/context.ts`:
- Around line 38-50: Update refuseUnknownReads so the Proxy get trap allows the
string key "then" to pass through via Reflect.get, alongside existing allowed
keys and symbols. Continue throwing the adapter error for all other unknown
string properties.

In `@packages/cli/src/v8/project/create.ts`:
- Around line 49-60: Update the catch handler around createProject to check
ctx.signal.aborted first and rethrow the original cancellation error when true;
only construct projectCreateFailedError for non-cancellation failures.

In `@packages/cli/src/v8/project/env-list.ts`:
- Line 54: The stdout presentation currently reuses decorated variableRows,
producing keys with source labels that break piping. Add and export a raw-row
builder named variableStdoutRows in env-shared.ts, update listPresentations to
use it for stdout while retaining variableRows for the human table, and include
the new symbol in the import.

In `@packages/cli/src/v8/project/link.ts`:
- Around line 104-112: In the CREATE_CHOICE branch, trim the value returned by
ctx.prompt.text before using it. Validate the trimmed name with
isValidProjectSetupName, return projectSetupNameRequiredError("project link")
for invalid input, and pass the trimmed value to createProjectForLink.

In `@packages/cli/src/v8/project/transfer.ts`:
- Around line 203-224: Normalize both recipient flag values with trim before the
validation block, then use those normalized values for the mutually exclusive
and missing-recipient checks. Update the subsequent transferPresentations call
to receive the normalized workspace value so whitespace-only --to-workspace
behaves as absent and a valid --recipient-token is used.

In `@packages/cli/src/v8/resources-shared/workspace.ts`:
- Around line 31-38: Update the workspace ID validation in the activeCredential
handling to reject blank or whitespace-only values using a trimmed non-blank
check. Preserve the existing workspaceRequiredError behavior for invalid IDs,
and use the validated workspace ID when constructing the returned object.

In `@packages/cli/tests/v8-bucket.test.ts`:
- Around line 57-178: Extract the duplicated v8 command-test scaffolding into
one shared test helper module. In packages/cli/tests/v8-bucket.test.ts lines
57-178, move Call, Responder, apiFailure, pinnedCwd, unpinnedCwd, resultFrame,
and blocks into the helper, parameterizing the temporary-directory prefix, and
retain only bucket-specific routes and fixtures. In
packages/cli/tests/v8-branch.test.ts lines 34-131 and
packages/cli/tests/v8-git.test.ts lines 76-235, import the shared helpers and
remove local copies while retaining branchClient routes, or errorOf,
tickingClock, and git-specific fixtures and routes respectively.

In `@packages/cli/tests/v8-git.test.ts`:
- Around line 829-856: Align the git authentication error contract with design
§2.1: remove the 401/403-to-GIT.AUTH_REQUIRED mapping from the git error mapper
and update this test to expect CLI.CREDENTIALS_REQUIRED with its corresponding
envelope, unless the design and divergence documentation are explicitly amended
to preserve GIT.AUTH_REQUIRED.

In `@packages/cli/tests/v8-legacy-context.test.ts`:
- Around line 64-78: Add a test in the legacy context adapter suite that
accesses a symbol property on the context and verifies it passes through the
proxy without throwing the adapter error. Use a symbol key and assert the
resulting value or access behavior, covering the typeof key !== "string" guard
in legacyOperationContext while preserving the existing runtime and top-level
rejection tests.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 260b82f0-c91e-414b-83a4-1f830df78bd1

📥 Commits

Reviewing files that changed from the base of the PR and between 9bc47d0 and c813c64.

📒 Files selected for processing (83)

• .drive/projects/prisma-cli-v8/assets/briefs/s2b-engine-requests.md
• .drive/projects/prisma-cli-v8/assets/briefs/s2b-midslice-handover.md
• .drive/projects/prisma-cli-v8/assets/briefs/windows-ci-credential-manager.md
• .drive/projects/prisma-cli-v8/assets/s2/parity-divergences-s2b.md
• .drive/projects/prisma-cli-v8/reviews/code-review.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/conventions.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/d1-project.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/d2-postgres.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/d3-bucket-branch-git.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/facts/facts-d1-project.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/facts/facts-d2-postgres.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/facts/facts-d3-bucket-branch-git.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/facts/facts-v8-patterns.md
• .drive/projects/prisma-cli-v8/specs/s2b-resources.md
• packages/cli/src/controllers/app-env.ts
• packages/cli/src/controllers/branch.ts
• packages/cli/src/controllers/database.ts
• packages/cli/src/controllers/project.ts
• packages/cli/src/presenters/app-env.ts
• packages/cli/src/presenters/project.ts
• packages/cli/src/v8/branch/errors.ts
• packages/cli/src/v8/branch/list.ts
• packages/cli/src/v8/bucket/context.ts
• packages/cli/src/v8/bucket/create.ts
• packages/cli/src/v8/bucket/delete.ts
• packages/cli/src/v8/bucket/errors.ts
• packages/cli/src/v8/bucket/key-create.ts
• packages/cli/src/v8/bucket/key-delete.ts
• packages/cli/src/v8/bucket/key-list.ts
• packages/cli/src/v8/bucket/list.ts
• packages/cli/src/v8/bucket/presentation.ts
• packages/cli/src/v8/cli.ts
• packages/cli/src/v8/git/connect.ts
• packages/cli/src/v8/git/context.ts
• packages/cli/src/v8/git/disconnect.ts
• packages/cli/src/v8/git/errors.ts
• packages/cli/src/v8/postgres/backup-list.ts
• packages/cli/src/v8/postgres/connection-create.ts
• packages/cli/src/v8/postgres/connection-list.ts
• packages/cli/src/v8/postgres/connection-remove.ts
• packages/cli/src/v8/postgres/connection-rotate.ts
• packages/cli/src/v8/postgres/context.ts
• packages/cli/src/v8/postgres/create.ts
• packages/cli/src/v8/postgres/errors.ts
• packages/cli/src/v8/postgres/list.ts
• packages/cli/src/v8/postgres/presentation.ts
• packages/cli/src/v8/postgres/remove.ts
• packages/cli/src/v8/postgres/restore.ts
• packages/cli/src/v8/postgres/show.ts
• packages/cli/src/v8/postgres/usage.ts
• packages/cli/src/v8/project/context.ts
• packages/cli/src/v8/project/create.ts
• packages/cli/src/v8/project/env-add.ts
• packages/cli/src/v8/project/env-list.ts
• packages/cli/src/v8/project/env-remove.ts
• packages/cli/src/v8/project/env-shared.ts
• packages/cli/src/v8/project/env-update.ts
• packages/cli/src/v8/project/errors.ts
• packages/cli/src/v8/project/link.ts
• packages/cli/src/v8/project/list.ts
• packages/cli/src/v8/project/presentation.ts
• packages/cli/src/v8/project/remove.ts
• packages/cli/src/v8/project/rename.ts
• packages/cli/src/v8/project/show.ts
• packages/cli/src/v8/project/transfer.ts
• packages/cli/src/v8/resources-shared/workspace.ts
• packages/cli/tests/branch.test.ts
• packages/cli/tests/bucket.test.ts
• packages/cli/tests/database-plan-limit.test.ts
• packages/cli/tests/database.test.ts
• packages/cli/tests/project-controller.test.ts
• packages/cli/tests/project-mutations.test.ts
• packages/cli/tests/project-real-mode.test.ts
• packages/cli/tests/project.test.ts
• packages/cli/tests/v8-branch.test.ts
• packages/cli/tests/v8-bucket.test.ts
• packages/cli/tests/v8-git.test.ts
• packages/cli/tests/v8-golden-rendering.test.ts
• packages/cli/tests/v8-legacy-context.test.ts
• packages/cli/tests/v8-mount-coverage.test.ts
• packages/cli/tests/v8-postgres.test.ts
• packages/cli/tests/v8-project.test.ts
• packages/cli/tests/v8-update-check.test.ts

💤 Files with no reviewable changes (7)

• packages/cli/tests/bucket.test.ts
• packages/cli/tests/project-controller.test.ts
• packages/cli/tests/project-mutations.test.ts
• packages/cli/tests/project-real-mode.test.ts
• packages/cli/tests/project.test.ts
• packages/cli/tests/branch.test.ts
• packages/cli/tests/database.test.ts

[coderabbitai]

Actionable comments posted: 3

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/cli/src/v8/project/create.ts (1)

58-67: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Use the shared CLI_NAME for project recovery commands.

Both handlers hard-code prisma-cli in recovery guidance. This violates the CLI_NAME contract and can produce invalid commands when the executable name differs.

• packages/cli/src/v8/project/create.ts#L58-L67: Interpolate CLI_NAME in nextSteps and fallbackFix.
• packages/cli/src/v8/project/link.ts#L82-L91: Interpolate CLI_NAME in nextSteps and fallbackFix.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/cli/src/v8/project/create.ts` around lines 58 - 67, Replace
hard-coded prisma-cli prefixes with the shared CLI_NAME in recovery guidance:
update nextSteps and fallbackFix in projectCreateFailedError within
packages/cli/src/v8/project/create.ts (lines 58-67), and apply the same change
to the corresponding project-link error handler in
packages/cli/src/v8/project/link.ts (lines 82-91). Preserve the existing command
arguments and guidance text.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.drive/projects/prisma-cli-v8/specs/s2b-resources.md:
- Around line 133-138: Update the list stdout contract in specs/s2b-resources.md
so backup sizes use stable raw numeric values and null statuses use an explicit
machine-readable representation instead of localized text or isDefault;
alternatively, remove these commands from the pipe-safe contract and its
acceptance criteria.

In `@packages/cli/src/v8/project/context.ts`:
- Around line 45-46: Update the proxy get logic around the key check in the
context adapter to use an own-property check on target instead of key in target,
so inherited Object.prototype keys reach the adapter error path while exposed
own properties still pass through. Preserve the PROBE_KEYS then allowlist, and
add a regression test covering an inherited key such as toString or constructor.

---

Outside diff comments:
In `@packages/cli/src/v8/project/create.ts`:
- Around line 58-67: Replace hard-coded prisma-cli prefixes with the shared
CLI_NAME in recovery guidance: update nextSteps and fallbackFix in
projectCreateFailedError within packages/cli/src/v8/project/create.ts (lines
58-67), and apply the same change to the corresponding project-link error
handler in packages/cli/src/v8/project/link.ts (lines 82-91). Preserve the
existing command arguments and guidance text.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: f9fe6799-f1cc-494d-9f4b-2a64abcbfb59

📥 Commits

Reviewing files that changed from the base of the PR and between c813c64 and 8fc8969.

📒 Files selected for processing (20)

• .drive/projects/prisma-cli-v8/assets/briefs/credential-manager-handover.md
• .drive/projects/prisma-cli-v8/assets/s2/command-inventory.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/conventions.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/d1-project.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/d2-postgres.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/d3-bucket-branch-git.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/facts/facts-d1-project.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/facts/facts-d2-postgres.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/facts/facts-d3-bucket-branch-git.md
• .drive/projects/prisma-cli-v8/specs/s2b-design/facts/facts-v8-patterns.md
• .drive/projects/prisma-cli-v8/specs/s2b-resources.md
• packages/cli/src/v8/bucket/delete.ts
• packages/cli/src/v8/git/connect.ts
• packages/cli/src/v8/project/context.ts
• packages/cli/src/v8/project/create.ts
• packages/cli/src/v8/project/env-list.ts
• packages/cli/src/v8/project/env-shared.ts
• packages/cli/src/v8/project/link.ts
• packages/cli/tests/v8-legacy-context.test.ts
• packages/cli/tests/v8-project.test.ts