@humanbased/crosscheck 1.2.0-beta.37 → 1.2.0-beta.57

package/get-started.md

@@ -161,10 +161,16 @@ reviews the diff as usual — it never errors.
 Separate from enrichment above, which only *reads*. When `linear.enabled: true`,
 crosscheck mirrors each review verdict onto the PR's Linear issue.
 
-Two tiers. `api_key` (T0) reuses `LINEAR_API_KEY` and tags writes with a
-`🤖 crosscheck · crosscheck` signature line, but Linear still attributes them to
-your account. `client_credentials` (T1) uses an OAuth app in your workspace so
-writes render as the app itself:
+`crosscheck onboard` asks which rung of the attribution ladder you want and writes
+the config for you.
+
+**Start with `api_key`.** It reuses `LINEAR_API_KEY`, works immediately, and posts
+the comment — the feature is fully functional. Comments attribute to your Linear
+account, led by a `🤖 crosscheck · <model>` signature line.
+
+Climb to `client_credentials` when more than one thing writes to your workspace and
+you need them told apart. It uses an OAuth app — one per workspace, not per user —
+so comments post as crosscheck itself with its own icon:
 
 ```bash
 export LINEAR_CLIENT_ID=...
@@ -174,6 +180,25 @@ export LINEAR_CLIENT_SECRET=...
 A failed T1 token mint aborts the run rather than falling back to `api_key` —
 a silent downgrade would put agent writes back under a human's name.
 
+`crosscheck onboard` walks you through the choice:
+
+<p align="center">
+  <img src="./assets/linear-onboard.svg" alt="crosscheck onboard — choosing a Linear attribution rung" width="700" />
+</p>
+
+Before opening a PR, `crosscheck linear-test` exercises the whole path and posts nothing —
+identity, issue lookup, verdict filter, and the exact comment body:
+
+<p align="center">
+  <img src="./assets/linear-test.svg" alt="crosscheck linear-test — dry-run verification" width="700" />
+</p>
+
+`crosscheck status` shows which rung is active whenever `linear.enabled` is true:
+
+<p align="center">
+  <img src="./assets/linear-status.svg" alt="crosscheck status — the Linear identity section" width="620" />
+</p>
+
 Full walkthrough, including the two Linear UI gotchas that trip people up:
 [docs/linear-identity.md](docs/linear-identity.md).
 
@@ -1037,6 +1062,7 @@ vendors:
     enabled: true
     auth: subscription      # subscription | api-key
     model: gpt-5.6-terra    # pins the review model; unset = tier model (api-key) / CLI default (subscription)
+    effort: medium          # low | medium | high | xhigh | max | ultra (ultra: terra/sol only)
     # timeout_sec: 1200     # max seconds per CLI call; unset = tier-based (300/600/1200)
 
   claude:
@@ -1176,10 +1202,10 @@ linear:                       # write review verdicts back to a Linear issue (op
     scopes: "read,write"      # comma-separated; initiative:* are separate scopes
   identity:
     actor: crosscheck
-    signature: "🤖 {actor} · {product}"
+    signature: "🤖 {actor} · {model}"   # {actor} {product} {model} {reviewer} {icon}
+    icon_url: ""              # rendered where {icon} appears; app avatar is preferred
     per_step_actor: true      # crosscheck/review vs crosscheck/fix in Linear
-  comment_on:                 # verdicts mirrored to the issue
-    - APPROVE
+  comment_on:                 # verdicts mirrored to the issue (default omits APPROVE)
     - NEEDS_WORK
     - BLOCK
   team_keys: []               # e.g. [IN] — required to match bare refs like IN-42
@@ -1315,6 +1341,8 @@ codex review --base <base-branch> --title "<pr-title>"
 
 The `--base` flag diffs current HEAD against the base branch — exactly the PR diff. An explicit `vendors.codex.model` (or matching `model_tiers` entry) is passed as `-c model=...` under either auth mode. When unset: `auth: subscription` passes no model flag (the Codex CLI picks its default), while `auth: api-key` selects the model by quality tier (`fast` → `gpt-5.6-luna`, `balanced` → `gpt-5.6-terra`, `thorough` → `gpt-5.6-sol`).
 
+Reasoning effort comes from `vendors.codex.effort` and is always passed through as `-c model_reasoning_effort=...`. The values match the codex CLI tiers 1:1 — `low` (Light), `medium`, `high`, `xhigh` (Extra High), `max`, `ultra`. Not every model supports every tier: `ultra` is terra/sol only, and pre-5.6 models stop at `xhigh` — the CLI rejects unsupported combinations. Higher tiers can multiply review wall-clock time; pair them with `timeout_sec`.
+
 ### How Claude reviews run
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@humanbased/crosscheck",
-  "version": "1.2.0-beta.37",
+  "version": "1.2.0-beta.57",
   "description": "AI code review pipeline that turns agent-written PRs into merge-ready patches",
   "bin": {
     "crosscheck": "dist/cli.js",