@userland.fun/cli 0.1.3 → 0.3.0

package/README.md

@@ -17,45 +17,121 @@ npm install -g @userland.fun/cli
 Then run:
 
 ```sh
-userland signup --username <username>
-userland login --username <username>
+userland login
+userland login --no-browser
+userland signup
 userland auth status
-userland auth save-key --username <username> --api-key <api-key>
+userland auth save-key --api-key <api-key>
+userland auth logout
+userland auth logout --revoke
 userland accounts list
 userland accounts use <account-id>
+userland accounts status --account <account-id>
+userland accounts limits --account <account-id>
+userland accounts downgrade preview --to free --account <account-id>
 userland apps publish examples/<example-slug>
 userland apps publish examples/<example-slug> --account <account-id>
 userland apps list
 USERLAND_ACCOUNT_ID=<account-id> userland apps list
+userland apps status <app-id>
 userland apps releases <app-id>
+userland versions <app-id>
 userland apps rollback <app-id> <release-id>
 userland apps secrets set <app-id> <NAME> --value <value>
 userland apps events <app-id>
+userland apps routes list <app-id>
+userland apps slugs add <app-id> <slug>
+userland apps domains add <app-id> <hostname>
+userland apps domains verify <app-id> <hostname>
 ```
 
 From this repo, the same commands can be run from source:
 
 ```sh
-npm run userland -- signup --username <username>
-npm run userland -- login --username <username>
+npm run userland -- login
+npm run userland -- login --no-browser
+npm run userland -- signup
 npm run userland -- auth status
-npm run userland -- auth save-key --username <username> --api-key <api-key>
+npm run userland -- auth save-key --api-key <api-key>
+npm run userland -- auth logout
+npm run userland -- auth logout --revoke
 npm run userland -- accounts list
 npm run userland -- accounts use <account-id>
+npm run userland -- accounts status --account <account-id>
+npm run userland -- accounts limits --account <account-id>
+npm run userland -- accounts downgrade preview --to free --account <account-id>
 npm run userland -- apps publish examples/<example-slug>
 npm run userland -- apps publish examples/<example-slug> --account <account-id>
 npm run userland -- apps list
 npm run userland -- apps list --account <account-id>
+npm run userland -- apps status <app-id>
 npm run userland -- apps releases <app-id>
+npm run userland -- versions <app-id>
 npm run userland -- apps rollback <app-id> <release-id>
 npm run userland -- apps secrets set <app-id> <NAME> --value <value>
 npm run userland -- apps events <app-id>
+npm run userland -- apps routes list <app-id>
+npm run userland -- apps slugs add <app-id> <slug>
+npm run userland -- apps domains add <app-id> <hostname>
+npm run userland -- apps domains verify <app-id> <hostname>
 ```
 
-`signup`, `login`, and `auth save-key` save the API key to `~/.userland/credentials.json` with `0600` permissions. Account username and password are stored in the OS keychain: macOS Keychain, Windows Credential Manager, or Linux Secret Service through `secret-tool`. App commands prefer `USERLAND_API_KEY` when it is set, then fall back to the saved API key.
+`login` starts a browser device-authorization flow. The CLI prints a verification URL and user code, opens the browser when possible, waits for approval, then saves the returned API key to `~/.userland/credentials.json` with `0600` permissions. `signup` is an alias for the same flow; if the email is new, account creation happens in the browser after email proof.
+
+The CLI does not store platform passwords. App commands prefer `USERLAND_API_KEY` when it is set, then fall back to the saved API key. `auth save-key` remains available for CI, support, and manually copied API keys.
 
 Most users do not need to select an account. If no account is selected, the API uses the actor's default account. Team, client, and agency workflows can select an account with `--account <account-id>`, `USERLAND_ACCOUNT_ID`, or `userland accounts use <account-id>`. Platform account members manage apps, releases, secrets, billing, and settings; they are separate from app users inside a published app.
 
+Status and limits:
+
+```sh
+userland accounts status --account <account-id>
+userland accounts limits --account <account-id>
+userland accounts downgrade preview --to starter --account <account-id>
+userland apps status <app-id> --account <account-id>
+```
+
+`accounts limits` includes plan features, manifest limits, deployment limits, runtime limits, release limits, usage limits, current usage, and route counts.
+
+Route management:
+
+```sh
+userland apps routes list <app-id> --account <account-id>
+userland apps slugs list <app-id> --account <account-id>
+userland apps slugs add <app-id> <slug> --account <account-id>
+userland apps slugs remove <app-id> <slug> --account <account-id>
+userland apps domains list <app-id> --account <account-id>
+userland apps domains add <app-id> <hostname> --account <account-id>
+userland apps domains verify <app-id> <hostname> --account <account-id>
+userland apps domains remove <app-id> <hostname> --account <account-id>
+```
+
+Internal/platform-admin only operations are routed by the CLI but authorized server-side:
+
+```sh
+userland ops accounts status <account-id>
+userland ops accounts flag <account-id> suspended_abuse --reason "spam"
+userland ops accounts clear <account-id> suspended_abuse --reason "reviewed"
+userland ops apps status <app-id>
+userland ops apps flag <app-id> suspended_security --reason "incident"
+userland ops apps clear <app-id> suspended_security --reason "resolved"
+userland ops apps takedown <app-id> --reason "legal review"
+userland ops routes disable <route-id> --status disabled_abuse --reason "abuse"
+userland ops routes enable <route-id> --reason "resolved"
+```
+
+Structured API errors keep details on separate lines:
+
+```text
+API 402: Monthly request quota exceeded for the current plan.
+error=quota_exceeded
+metric=requests.monthly.max
+plan_key=free
+limit=10000
+current=10000
+upgrade_required=true
+```
+
 ## Validation
 
 Build and inspect the publish tarball: