clavue-v1 1.1.0 → 1.2.0

package/README.md

@@ -64,8 +64,8 @@ npx -y clavue-v1
 Run a specific version with `npx`:
 
 ```bash
-npx -y clavue-v1@1.1.0 --version
-npx -y clavue-v1@1.1.0
+npx -y clavue-v1@1.2.0 --version
+npx -y clavue-v1@1.2.0
 ```
 
 Install globally from npm when you want the `clavue-v1` command to stay available:
@@ -87,9 +87,34 @@ curl -fsSL https://unpkg.com/clavue-v1/install.sh | bash
 Install a specific version globally:
 
 ```bash
-curl -fsSL https://unpkg.com/clavue-v1@1.1.0/install.sh | bash -s -- 1.1.0
+curl -fsSL https://unpkg.com/clavue-v1@1.2.0/install.sh | bash -s -- 1.2.0
 ```
 
+## Quick Start: Official Clavue Cloud
+
+Official mode is a provider profile, not a second runtime: the same tools,
+compaction, permissions, and route inspection as every custom-API profile —
+only the credential source and the model catalog differ.
+
+1. Create a member API key at `https://www.clavue.com/account` (`cv_live_…`).
+2. Start `clavue-v1`, choose `自定义 API 配置` → `1. 添加配置`, pick the
+   `Clavue 官方` preset (API URL `https://api.clavue.com`), paste the key as
+   the auth token, and set model slots from the official family:
+
+```text
+主模型:   clavue-2.1        (official 27B coding model, 128K, premium pool)
+Haiku:    clavue-2.1-fast   (same model, fast pool — higher daily quota)
+Sonnet:   clavue-2.1-pro    (premium ceiling for planning and long-horizon work)
+Opus:     clavue-2.1-rev    (review-oriented; a different family from clavue-2.1, so it
+                             also works as CLAVUE_COMBO_REVIEW for cross-family review)
+```
+
+`auto` is also accepted. The CLI talks to `api.clavue.com/v1/messages`
+(Anthropic Messages API) and `/provider current` shows your plan and remaining
+points from the `x-clavue-points-*` response headers. Official identity is
+decided by exact host match only — a third-party gateway can never be
+mistaken for the official cloud.
+
 ## Quick Start: Custom API
 
 Fastest path for custom API users:
@@ -171,6 +196,34 @@ This package is intended for users who want an execution-first coding CLI with d
 
 On macOS, Clavue avoids Keychain by default and stores local credentials in `~/.clavue/.credentials.json` so startup does not trigger system Keychain prompts. If you explicitly want the old Keychain behavior back, launch with `CLAVUE_USE_KEYCHAIN=1 clavue-v1`.
 
+## Cross-Family Combo Review
+
+The review slot puts an independent model family between "the code changed"
+and "the work is done". Since 1.2.0 review is scheduled so it does not tax
+every edit:
+
+```bash
+CLAVUE_COMBO_MAIN=glm-5.3-flash          # developer model (any slot model is passed through verbatim)
+CLAVUE_COMBO_REVIEW=deepseek-v4-flash    # reviewer — pick a different family than main
+CLAVUE_COMBO_REVIEW_MODE=overlap         # overlap (default) | serial
+CLAVUE_COMBO_REVIEW_MIN_CHANGED_CHARS=80 # small edits accumulate; one review covers them
+CLAVUE_COMBO_REVIEW_MAX_PER_CHAIN=3      # review budget per query chain
+CLAVUE_COMBO_REVIEW_GRACE_MS=5000        # bounded wait for the final verdict at chain end
+CLAVUE_COMBO_REVIEW_FIX_LOOP=1           # opt-in: a chain-end "P0:" verdict grants one bounded fix turn
+```
+
+- `overlap` fires the review hop without blocking; the verdict is injected
+  at the next loop boundary so the developer model actually acts on it.
+  In the shipped A/B it roughly halves the review tax versus `serial`
+  (+38% vs +94% wall-clock on the hard task).
+- The reviewer is told which family wrote the code and which failure modes
+  that family is prone to. Same-family pairs still work; `/provider current`
+  flags them so you can choose an independent second opinion.
+- Review-on and the fix loop stay opt-in: on oracle-complete tasks a
+  competent developer model saturates on its own (see
+  `docs/evals/combo-review/`), so the defaults do not spend your time until
+  the discriminating experiment justifies it.
+
 ## Long-Running Session Memory
 
 Clavue automatically restarts normal long-running sessions with `--max-old-space-size=8192` before loading the full CLI. This prevents the common Node default ~4GB heap limit from killing large coding sessions with `Reached heap limit Allocation failed - JavaScript heap out of memory`.
@@ -191,7 +244,7 @@ Version check:
 
 ```bash
 npx -y clavue-v1 --version
-npx -y clavue-v1@1.1.0 --version
+npx -y clavue-v1@1.2.0 --version
 # available after a global install
 clavue-v1 --version
 ```