An extension cannot describe a command group; star mints '<name> commands' for every node above a leaf #841

An extension declares leaf commands by dotted name — gh.issues.report — and star synthesises the
intermediate groups, gh and issues, so that star gh issues report resolves. The spec has
no way to describe a group, so star mints a placeholder:

$ star gh --help
gh commands

Available Commands:
  issues      issues commands
  labels      labels commands

The leaves are fine — star gh issues report --help carries the help the spec gave it — but every
level above a leaf reads " commands". For a service node like gh, which the tree grammar
(star-extensions.md, The Shape of the Tree) makes the first thing a person types, that is the
worst place for the help to be empty.

Minted at cmd/star/main.go:473: Short: fmt.Sprintf("%s commands", parts[i]).

Wanted

A way for the spec to describe groups. Two shapes, either is fine:

groups:
  gh: GitHub under the NobleFactor classification scheme
  gh.issues: The issue report and its audits
  gh.labels: The label set every participating repository carries

or a help on the first command that names the group, inherited upward. When two extensions
contribute to one group — config show and config sync beside the built-in config verbs —
the first description seen wins and a second differing one is a load-time warning.

Until then the placeholder should at least be honest: " — see its subcommands" reads better
than " commands", which looks like a description that was never written. It is.

Observed 2026-09-06 with com.noblefactor.ops.GitHub (noblefactor-ops#140).

Epic: #445