@evident-ai/cli 3.4.1-dev.b1151a3 → 3.4.1-dev.b2ce99d

package/README.md

@@ -99,11 +99,9 @@ Options:
   warns and comes online anyway rather than failing. Env:
   `EVIDENT_OPENCODE_START_TIMEOUT` (seconds).
 - `--opencode-version <v1|v2>` — Which OpenCode major version to launch: `v1` or
-  `v2` (default: `v1`). Env: `EVIDENT_OPENCODE_VERSION`. **`v2` currently only works
-  against an already-running, unauthenticated `opencode2` process** — auto-starting
-  one is hard-gated off pending
-  [#2075](https://github.com/sroze/evident/issues/2075) and errors immediately
-  otherwise.
+  `v2` (default: `v1`). Env: `EVIDENT_OPENCODE_VERSION`. When selected, the CLI
+  starts or attaches to `opencode2` and authenticates its local requests with the
+  generated server credential when it starts the process. V1 remains the default.
 - `--litestream-config <path>` — Start `litestream replicate` for the OpenCode
   session database with this config file. Use this for runner images that persist
   the session database; the file is produced by `runner-synchroniser litestream-config`.
@@ -221,6 +219,9 @@ targets the **production** Evident platform by default.
 - `OPENCODE_LOG_LEVEL` — OpenCode log level when `evident run` starts an
   image-owned process: `DEBUG`, `INFO`, `WARN`, or `ERROR` (default: `INFO`).
   Invalid values fall back to `INFO`.
+  Under `--opencode-version v2`, the accepted set is
+  `all|trace|debug|info|warn|warning|error|fatal|none` and invalid values fall back to
+  `info`.
 - `EVIDENT_LOG_LEVEL` — Equivalent to `--log-level`; the flag wins if both are
   set, and `-v`/`--verbose` also outranks this env var.
 - `EVIDENT_OPENCODE_START_TIMEOUT` — Equivalent to `--opencode-start-timeout`