cmd/cue: help inputs needs to more precisely define semantics of "import paths"

[myitcv]

What version of CUE are you using (cue version)?

$ cue version
cue version v0.0.0-20240530095928-7ab80025ba4b

go version go1.22.3
      -buildmode exe
       -compiler gc
  DefaultGODEBUG httplaxcontentlength=1,httpmuxgo121=1,tls10server=1,tlsrsakex=1,tlsunsafeekm=1
     CGO_ENABLED 1
          GOARCH arm64
            GOOS linux
             vcs git
    vcs.revision 7ab80025ba4bd4f0e643b0e5a8cd83b5fee6235a
        vcs.time 2024-05-30T09:59:28Z
    vcs.modified false
cue.lang.version v0.9.0

Does this issue reproduce with the latest release?

Yes

What did you do?

Ran cue help inputs and viewed https://cuelang.org/docs/reference/cli/cue-inputs/.

What did you expect to see?

A clear (bullet list) definition/explanation of the rules behind what CUE accepts as inputs:

• Is the term "import path" complete/correct? Or is package path more correct? Are we consistent with the modules reference?
• When ... is allowed and not?
• What do we call a ./ or ../ prefixed input?
• What are the cmd/cue semantics for ./x, and the various permutations of what is included in x (package named x, multiple packages, package not named x, tool files, test files...)
• ...

The distinction with import paths (for modules and packages, see https://cuelang.org/docs/reference/modules/) should also be clear.

What did you see instead?

Old docs that are more relevant to the Go semantics.