clavue 8.8.129 → 8.9.0

package/README.md

@@ -1,4 +1,4 @@
-# Clavue v8.8.129
+# Clavue v8.9.0
 
 ![Clavue cover](https://unpkg.com/clavue/image.png)
 
@@ -15,7 +15,7 @@ Clavue is built around a simple operating model: the user owns the workflow, the
 - Fast first run: install, choose an API configuration mode, paste URL/key or token, set model slots if needed, then start coding.
 - Visible configuration: `/provider` and `clavue provider` expose the active route, saved profiles, credential mode, model slots, validation, repair, and current environment state.
 - Practical autonomy: permission setup should make development smoother while still being explicit about trust boundaries.
-- Continuity over spectacle: long-context recovery, compaction, `/mao`, `/team`, and `/retro` exist to keep work moving, not to add noise.
+- Continuity over spectacle: long-context recovery, compaction, `/team`, and `/retro` exist to keep work moving, not to add noise.
 
 ## What Clavue Is
 
@@ -34,7 +34,6 @@ Canonical primary command surfaces:
 - `/init`: create or refresh generated project rule files: `clavue.md`, `AGENTS.md`, and compatibility `CLAUDE.md`.
 - `/provider`: configure, switch, validate, repair, copy, edit, delete, or save provider profiles.
 - `/permissions` (`/approvals` compatibility alias): set the default permission mode so trusted development environments can run with less friction; use `/permissions autonomous` for an opt-in high-autonomy local development lane.
-- `/mao` (`/codex` compatibility alias): run bundled Codex-style review, rescue, and delivery-gate flows through the active Clavue provider profile.
 - `/team`: inspect local team readiness, active team config, and capability state.
 - `/retro`: run a multi-round repo retrospective and upgrade loop.
 - `/tasks`: inspect task-board state for long-running work.
@@ -65,8 +64,8 @@ npx -y clavue
 Run a specific version with `npx`:
 
 ```bash
-npx -y clavue@8.8.129 --version
-npx -y clavue@8.8.129
+npx -y clavue@8.9.0 --version
+npx -y clavue@8.9.0
 ```
 
 Install globally from npm when you want the `clavue` command to stay available:
@@ -86,7 +85,7 @@ curl -fsSL https://unpkg.com/clavue/install.sh | bash
 Install a specific version globally:
 
 ```bash
-curl -fsSL https://unpkg.com/clavue@8.8.129/install.sh | bash -s -- 8.8.129
+curl -fsSL https://unpkg.com/clavue@8.9.0/install.sh | bash -s -- 8.9.0
 ```
 
 ## Quick Start: Custom API
@@ -191,7 +190,7 @@ Version check:
 ```bash
 clavue --version
 npx -y clavue --version
-npx -y clavue@8.8.129 --version
+npx -y clavue@8.9.0 --version
 # available after a global install and launcher setup
 clavue --version
 ```
@@ -229,19 +228,7 @@ clavue setup-token
 /provider clear
 ```
 
-`/mao` is the preferred Codex surface. It reuses the active clavue provider profile directly, verifies `/v1/responses` reachability on the current route, and avoids a separate global Codex setup flow. `/codex` remains a compatibility alias. Mao jobs use the bundled Codex `exec` runtime by default; `CLAVUE_MAO_CODEX_RUNTIME=app-server` is recognized for setup diagnostics only in this release. `/mao gate` refreshes the silent supervisor ledger and reports whether final delivery, release, publish, tag, or push is currently allowed.
-
-```text
-/mao setup
-/mao review --background
-/mao adversarial-review --base main auth and retry handling
-/mao rescue --write fix the provider override bug and verify it
-/mao rescue --resume apply the top fix from the previous Mao run
-/mao status
-/mao gate
-/mao gate --json
-/mao result
-```
+The Mao supervisor ledger is still used internally by delivery gates; user-facing `/mao` and `/codex` command surfaces are hidden while native Team/Agent workflows remain the public agent system.
 
 `/team` inspects real local team state from the active config root instead of giving a generic explanation. By default that is `~/.clavue/teams`, but it follows `CLAVUE_CONFIG_DIR` if you launch clavue against a different config root.