avorelo 0.2.0 → 0.3.0

package/README.md

@@ -4,25 +4,25 @@
 work focused, keeps secrets out of the model and out of cloud, and saves proof of what actually happened,
 locally.
 
-> Status: **early access** (`0.0.1-alpha.x`). Local-first and deterministic. See the limitations below.
+> Status: **private alpha** (`0.2.0`). Local-first and deterministic. See the limitations below.
 
 ## Quickstart
 
-No signup, no cloud account, no credentials, no network required. From a local checkout:
+No signup, no cloud account, no credentials, no network required.
 
 ```
-npm run build                                   # build the bundled CLI (dist/avorelo.mjs)
-
-# Run the CLI from the checkout (always current). `npm run cli:local -- <cmd>` works too.
-node src/avorelo/surfaces/cli/avorelo.ts init --target .            # 1. initialize a local workspace
-node src/avorelo/surfaces/cli/avorelo.ts status --target .          # 2. is the workspace ready? what's next?
-node src/avorelo/surfaces/cli/avorelo.ts run "run tests" --target . # 3. run your first focused task
-node src/avorelo/surfaces/cli/avorelo.ts control-center --target .  # 4. read-only local operator view
+npx avorelo@latest activate        # detect your project, set up local state, start getting value
+npx avorelo@latest status          # what's the workspace state? what's next?
+npx avorelo@latest run "run tests" # run your first focused task
+npx avorelo@latest control-center  # read-only local operator view
 ```
 
-`init` writes only local metadata under `.avorelo/` (gitignored) — no source, env, or secrets. `status`
-always tells you the next command. `readiness` is the *canonical phase gate* (most meaningful against the
-Avorelo repo itself); `status` is the per-workspace readiness signal for your own repo.
+Run `npx avorelo@latest activate` to start with the latest validated Avorelo CLI.
+Global install: `npm install -g avorelo` — then run `avorelo doctor` to check for updates.
+
+`activate` writes only local metadata under `.avorelo/` (gitignored) — no source, env, or secrets.
+`status` always tells you the next command. `readiness` is the *canonical phase gate* (most meaningful
+against the Avorelo repo itself); `status` is the per-workspace readiness signal for your own repo.
 
 ## What it does
 
@@ -85,7 +85,6 @@ Node.js >= 24.
 ## Current Limitations
 
 - Cloud sync is **dry-run + local-queue only** — no live credentialed transmission in this version.
-- Install is from tarball or source checkout — no globally published package yet.
 - No hosted dashboard; no billing or pricing active.
 
 ## License