@evident-ai/cli 3.4.1-dev.cb56b3f → 3.4.1-dev.d74adb9

package/README.md

@@ -98,6 +98,10 @@ Options:
   healthy when the runner starts it itself (default: `180`). On expiry the runner
   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`. 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`.
@@ -212,10 +216,18 @@ targets the **production** Evident platform by default.
 - `EVIDENT_RESOURCE_USAGE_REPORTING` — Equivalent to
   `--no-resource-usage-reporting`; set it to `off` to disable. The flag wins
   if both are set.
+- `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`
   (seconds); the flag wins if both are set.
+- `EVIDENT_OPENCODE_VERSION` — Equivalent to `--opencode-version`; the flag wins
+  if both are set. Defaults to `v1`.
 - `EVIDENT_SESSION_CLEANUP_MAX_AGE` — Equivalent to `--session-cleanup-max-age`;
   the flag wins if both are set.
 - `EVIDENT_SESSION_CLEANUP_MAX_COUNT` — Equivalent to