docs: upgrade guides still describe check-only wheels upgrade + manual zip swap

[bpamiri]

After #3039, wheels upgrade apply performs the swap (explicit verb; backup-by-default). The following guide pages still describe the old workflow — check-only wheels upgrade with a manual vendor/wheels/ zip swap:

Pages to update

web/sites/guides/src/content/docs/v4-0-0/command-line-tools/wheels-commands/upgrade.mdx

The entire page describes wheels upgrade as a "read-only scanner" that never touches files. The frontmatter description, synopsis, and "What gets updated" section all need updating to document wheels upgrade apply as the swap verb (with backup-by-default, --nobackup, and the pre-swap recovery announcement). The current "What gets updated" section says:

Project `vendor/wheels/`: swap the directory manually, or regenerate the app skeleton against the new release and port your `app/` into it.

This should now read: run `wheels upgrade apply`.

web/sites/guides/src/content/docs/v4-0-0/start-here/release-channels.mdx (line 199)

wheels upgrade check --to=<version>

…followed by "or just re-scaffold the app's `vendor/wheels/` from a fresh `wheels new`" — needs an `apply` path added alongside `check`.

web/sites/guides/src/content/docs/v4-0-0/upgrading/3x-to-4x.mdx (line 389)

wheels upgrade check

This is the recommended upgrade CLI command under "Deprecating `box wheels upgrade`". After #3039, the full sequence is `check` first, then `apply`.

References

• wheels upgrade: apply mode — swap the app's vendored framework from the CLI bundle #3035 — introduced the apply verb
• feat(cli): wheels upgrade applies the framework swap from the CLI bundle #3039 — hardened: backup-by-default, pre-swap recovery announcement, explicit verb everywhere

🤖 Generated with Claude Code

[wheels-bot]

Wheels Bot — Triage

Classified as docs-request.

Docs scope

Three existing guide pages still document the pre-#3039 workflow (check-only wheels upgrade plus a manual vendor/wheels/ zip swap) and need updating to document the new explicit wheels upgrade apply verb (backup-by-default, --nobackup, pre-swap recovery announcement):

• command-line-tools/wheels-commands/upgrade.mdx — the main change: frontmatter description, synopsis, and the "What gets updated" section currently describe wheels upgrade as a read-only scanner with a manual vendor/wheels/ swap; rewrite to document apply as the swap verb.
• start-here/release-channels.mdx (~line 199) — add an apply path alongside the existing wheels upgrade check --to=<version> example.
• upgrading/3x-to-4x.mdx (~line 389) — the recommended sequence under "Deprecating box wheels upgrade" becomes check first, then apply.

Confidence: high

The gap is concrete (specific verb to document across three named, existing pages) and the work is translation-of-code grounded in #3035/#3039, with no structural docs-architecture decisions required.

[wheels-bot]

Wheels Bot — Docs proposed

Draft PR: #3046

Pages updated:

• command-line-tools/wheels-commands/upgrade.mdx — frontmatter description, synopsis, flags table (split to check-specific), new wheels upgrade apply section (pre-swap announcement, backup convention, --to as assertion, --nobackup, example), updated "What gets updated" and rollback sections.
• start-here/release-channels.mdx — added wheels upgrade apply to the channel-switch sequence.
• upgrading/3x-to-4x.mdx — extended the "Deprecating box wheels upgrade" block with apply after check.

Screenshots needed: none

A human review is required before merge. The Reviewer will weigh in shortly.