Users struggle with getting started with Cloudflare because of friction in authorizing and bootstrapping the DOStateStore.

Currently, the getting started experience looks like this:

1. Generate an ALCHEMY_STATE_TOKEN manually and store in .env
2. Create the alchemy.run.ts and configure the DOStateStore
3. Run bun ./alchemy.run.ts which creates the store and uploads the store

Ideally, we'd reduce these steps to a single alchemy bootstrap command that automates this with best practices.

Another point of friction is that wrangler login has fixed OAuth scopes. For example, it's impossible to have wrangler login request scopes required to create Account Access Tokens, which are important for creating Access/Secret keys for accessing R2 (for example). This all leads to manual steps, high friction and drop-off.

Another problem is that people have more than one cloudflare account and it's hard to manage the different accounts. Ideally, we'd provide a similar experience to the AWS CLI's profiles (and default profile) by storing a config in ~/.alchemy/config which have a list of profiles. Use YAML (not TOML).

Then a user could do:

alchemy login # default profile
alchemy login --profile dev
alchemy login --profile prod