The scopes bb needs, with what each one buys, in the order someone should
decide about them: read:user:bitbucket first because login itself fails
without it, then the read scopes a browsing user wants, then the grants that
only some commands need. Ordering is the only guidance a list this long can
give, since Atlassian’s picker shows two dozen Bitbucket scopes at once.
--help carries the same guidance as the interactive walkthrough, because
--email with --token-stdin skips the walkthrough entirely and a CI user
has nowhere else to read it.
The scope block both the walkthrough and --help print, one scope why
line per entry, aligned on the widest name. Rendered from SCOPES rather
than written out a second time: the walkthrough, --help and the README
each used to carry their own copy of this list, and two of the three fell
behind when repo create shipped.