@everfir/az8-cli 0.4.0 → 0.5.0

package/README.md

@@ -18,7 +18,7 @@ az8 guide
 For a supplied release artifact, install the exact immutable tarball instead:
 
 ```bash
-npm install --global ./everfir-az8-cli-0.4.0.tgz
+npm install --global ./everfir-az8-cli-0.5.0.tgz
 az8 --version
 ```
 
@@ -45,18 +45,18 @@ responses for the effective Operations, permissions, input schema, History, comp
 semantics of the installed version and current account. Workflow Definition queries and
 `planGeneration` remain authoritative for current generation inputs.
 
-## Credentials and environment
+## Credentials
 
 Use browser authorization for the default local account:
 
 ```bash
-az8 login --environment test
-az8 whoami --environment test
-az8 logout --environment test
+az8 login
+az8 whoami
+az8 logout
 ```
 
-`login` opens `studio.az8.studio` or `studio.az8.art`, waits for explicit approval, validates the
-issued account, and stores the credential in the current operating-system user's private AZ8 CLI
+`login` opens AZ8 Studio, waits for explicit approval, validates the issued account, and stores the
+credential in the current operating-system user's private AZ8 CLI
 state directory. `whoami` reports the active account and credential source without exposing the
 token. `logout` closes daemon Sessions that depend on that local credential and removes it locally;
 it does not revoke copies on other machines. Use `login --no-open` when the browser must be opened
@@ -67,13 +67,11 @@ an explicit env-file path, or an inherited process environment:
 
 ```dotenv
 AZ8_TOKEN=<operator-provisioned-secret>
-AZ8_ENVIRONMENT=test
 ```
 
-`AZ8_ENVIRONMENT` accepts `test` or `production`. Command-line `--environment` overrides the env
-value. Without `--env-file`, the CLI searches from the working directory upward for `.env.local`.
+Without `--env-file`, the CLI searches from the working directory upward for `.env.local`.
 An explicit file is selected by path, for example
-`--environment test --env-file /secure/path/.env.local`. Process-environment credentials take
+`--env-file /secure/path/.env.local`. Process-environment credentials take
 precedence over env files, which take precedence over the locally saved login. The CLI never
 rewrites an env file or inherited environment. Agents must not read, print, edit, or ask users to
 paste credential contents. Tokens must not be passed through argv or stdio protocol payloads.
@@ -121,9 +119,9 @@ A new agent needs only the installed package, an authorized account, and this do
 active identity, then create its own Project and open one daemon-backed Agent Collaboration Session:
 
 ```bash
-az8 whoami --environment test
+az8 whoami
 az8 projects create --name "Agent preview workspace"
-az8 session open <project-id> --environment test
+az8 session open <project-id>
 az8 session query capabilities.summary
 az8 session operation createNote --request-id preview-note-1 \
   --input-json '{"text":"Release smoke note","position":{"x":160,"y":160}}'
@@ -488,7 +486,7 @@ from TypeScript source:
    Project, Session, persistent Canvas, one-shot, upload, and download entry points; and `az8 guide`
    plus its JSON form work without credentials or network access.
 2. With no credential, an authenticated command fails without connecting and without printing a
-   token. With the test token, `projects create` returns a new Project owned by the authenticated
+   token. With the acceptance credential, `projects create` returns a new Project owned by the authenticated
    account.
 3. A daemon-backed Session opens, becomes current, accepts a summary query and one semantic write,
    reports healthy status, delivers an interested external change through `watch`, returns `idle`
@@ -501,7 +499,7 @@ from TypeScript source:
 6. Upload one small local media file, confirm immediate detail resolution to its Core Node, replay
    the same idempotency key without another transfer, and download the resolved media to a fresh
    destination whose SHA-256 is reported.
-7. Run repository `pnpm verify`, retain the tarball SHA-512, and record the tested environment. Never
-   perform these acceptance writes against production.
+7. Run repository `pnpm verify`, retain the tarball SHA-512, and record the internal acceptance
+   target. Follow the repository-only release instructions for that target.
 
 Release and rollback commands are in `RELEASE.md`; package changes are in `CHANGELOG.md`.