deno deploy should pick up deploy-cli --json/non-interactive commands

[avocet-bot]

Problem

deno deploy currently resolves @deno/deploy from JSR and is still loading deploy-cli 0.0.99, which does not include the newer non-interactive / JSON support that has already landed in denoland/deploy-cli main.

This blocks CI/agent flows that need to discover the organization slug from only a Deploy token. Support guidance currently points users at:

deno deploy whoami --json
deno deploy orgs list --json

…but those commands are not available in the released/bundled CLI yet.

Reproduction

With current Deno:

$ deno --version
deno 2.8.2

$ deno deploy --version
0.0.99

$ deno deploy whoami --json
error: Unknown option "--json". Did you mean option "--prod"?

deno deploy --help also has no whoami, orgs, or global --json option.

Expected

deno deploy should expose the deploy-cli commands/options that were added for non-interactive usage:

• global --json
• --non-interactive / -y
• whoami --json
• orgs list --json

At minimum, Deno should pick up a deploy-cli release containing these changes once it is published.

Relevant deploy-cli changes

These are already merged in denoland/deploy-cli:

• feat: add --json, --non-interactive flags and exit-code taxonomy deploy-cli#91
• feat: add deno deploy whoami and conflict hint deploy-cli#95
• feat(whoami): consume account.me to populate user identity deploy-cli#101

Possible Deno-side issue

cli/tools/deploy.rs currently fetches @deno/deploy/meta.json and chooses:

let latest_version = info.versions.keys().max()

That is a lexicographic max over version strings. It works while the latest is 0.0.99, but when deploy-cli publishes 0.0.100, lexicographic ordering will still prefer 0.0.99 over 0.0.100.

It may be safer to use the registry latest field from the JSR metadata (or semver ordering) rather than string max, otherwise publishing the deploy-cli fix may not actually upgrade deno deploy.