CLI authentication

The CLI should authenticate with a Hamstik Personal Access Token rather than a browser session cookie. Create tokens from Account → Developer Settings, copy the complete value once, and store it in the CLI’s secure configuration mechanism when available.

The token’s effective access is the intersection of its scopes and resource restrictions with the user’s current Organization membership. A token never grants Organization membership by itself.

See Personal Access Tokens for scope and resource behavior. The exact CLI configuration command is intentionally deferred until the CLI repository’s public command surface is available.