The V2 Phases section lists "subcommand groups" as a future capability. But the "Command Shape" section of the same document already documents App.subcommand() with working code examples and states it is part of the current API. The V2 entry implies App.subcommand() is unshipped, directly contradicting the earlier section.
Fix: Remove "subcommand groups" from the V2 future list if App.subcommand() is already a V1 capability. If V2 genuinely adds something more (e.g., nested multi-level groups), rename the V2 entry to be specific about what is new. The V1/V2 distinction should be unambiguous throughout the document.
File: docs/base-cli.md
The V2 Phases section lists "subcommand groups" as a future capability. But the "Command Shape" section of the same document already documents
App.subcommand()with working code examples and states it is part of the current API. The V2 entry impliesApp.subcommand()is unshipped, directly contradicting the earlier section.Fix: Remove "subcommand groups" from the V2 future list if
App.subcommand()is already a V1 capability. If V2 genuinely adds something more (e.g., nested multi-level groups), rename the V2 entry to be specific about what is new. The V1/V2 distinction should be unambiguous throughout the document.File:
docs/base-cli.md