Confusing results if email address (instead of username) given for --token

Nobody has claimed this yet.

When I first ran --token I gave it my email address instead of my username.

This works enough to be confusing! Specifically, the tile source upload works (presumably the API is willing to accept an email instead of a username?), but then the geojson validation fails because "layers.my_layer_name.source does not belong to account 'myusername'.", because it had interpolated the given username into the name of the tile source in the recipe file.

Suggestion: Resolve the situation gracefully, either by somehow ascertaining the username from email, or simply by refusing to accept a username that contains a "@", or perhaps just detecting the mismatch and giving a more pointed error message?

Start at the --token argument handling and trace how the supplied value reaches tile source upload, the recipe file, and geojson validation. Compare the behavior for a username and an email address; done means the mismatch is handled consistently with a pointed result, as decided by the project maintainers.

Written by the indexing model from the issue text.