docs: Windows install tab on Start Here points users at the wrong Chocolatey package (v1.x legacy)

[bpamiri]

Found during a fresh-VM onboarding test. Documented but not actually executed (test machine was macOS) — paste-ready failure path for any Windows user following the tutorial today.

Where

start-here/installing — Windows tab, "Install via Chocolatey" section.

Severity

Major (silent footgun for Windows users).

What the guide says

Open PowerShell as Administrator: choco install wheels

What actually happens

The deeper CLI Installation reference admits:

The wheels package at community.chocolatey.org/packages/wheels is still the v1.x legacy (CommandBox-based) release. The v2.x LuCLI-based package is built and tested in wheels-dev/chocolatey-wheels but has not been pushed to the public feed yet.

So a Windows user following Start Here → Installing will run choco install wheels, get the wrong binary (v1 CommandBox-based CLI, different commands, can't drive the v4 tutorial at all), and have no warning on the Start Here page.

The warning only appears in the deeper CLI reference page that most first-time users won't read.

Suggested fix

Two parts:

1. On Start Here → Installing (Windows tab): replace the bare choco install wheels line with the manual JAR install instructions that the CLI reference page already has, plus an explicit "do not use the public Chocolatey package yet — it's the unsupported v1.x release." Link the underlying issue tracking the v2 publish (will be filed at wheels-dev/chocolatey-wheels).
2. Once the v2 Chocolatey package is published, restore the choco install wheels instructions and remove the warning.

Companion publish-side issue: wheels-dev/chocolatey-wheels (filed separately).

Source

Same fresh-VM onboarding test that produced #2294.