[v2] Add v1 launch-command aliases or migration hints #2173

Automatically submitted on behalf of the user by an AI agent.

Problem

After upgrading from v1 to v2.0.0-beta.7, familiar launch commands fail without telling me what to use instead:

executor web
ERROR: Unknown subcommand "web" for "executor"

executor service start
ERROR: Unknown subcommand "service" for "executor"
Did you mean this? serve

In v2, running executor with no subcommand starts the server and opens the dashboard; executor serve starts it without opening a browser. The service start suggestion can therefore send someone to the headless command when they were trying to open the dashboard.

Request

Please preserve aliases for v1 launch commands where their behavior still maps cleanly. If aliases are not desired, detect these legacy forms and print the v2 equivalent, distinguishing the dashboard-opening executor command from headless executor serve. A short v1-to-v2 command mapping in the CLI docs would help too.

Environment

• Executor v2.0.0-beta.7, upgraded from v1.6.10
• Windows 11 Pro x64 (build 10.0.26300)
• PowerShell 7.6.6, Node.js v26.10.0, Bun 1.4.2

I found an older closed report about executor web failing (#438), but it concerned an accidentally installed 2.0.0 package. This report is from the documented v2 beta CLI and also covers the misleading service start suggestion.