LLeMbas CLI 2.0.0-beta.1; harness spec 3.0.0

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

CHANGELOG.md

@@ -6,6 +6,8 @@ All notable changes to LLeMbas CLI. The format follows
 
 ## [Unreleased]
 
+## [2.0.0-beta.1] — 2026-11-03
+
 LLeMbas CLI 2.0 works with LLeMbas 2.0 and nothing else: it uses the server it is logged in to,
 keeps tool results short without ever rewriting what the model has already read, and reads every
 instruction file on the way down to where it was started. Harness spec 3.0.0.

harness/README.md

@@ -62,11 +62,10 @@ page *Harness-parity* in LLeMbas CLI's wiki.
   every mode; `plan_submit` only in plan mode, where it is the approval. Their permission key is
   `plan` (`permission/defaults.json`), which a rule written for the former `todo` key still reaches.
 
-## 3.0.0 (draft)
+## 3.0.0
 
-`VERSION` says `3.0.0-draft` while the spec is written ahead of both implementations: a SemVer
+Written ahead of both implementations as `3.0.0-draft`, and `3.0.0` once both carried it (LLeMbas
-pre-release, ordered below `3.0.0`, which no stable release of either project carries. It becomes
+CLI 2.0.0-beta.1, LLeMbas 2.0.0-beta.1). **Two worlds, one harness**: a chat works in the server's file
-`3.0.0` when both implement it. **Two worlds, one harness**: a chat works in the server's file
 system, an agent session on its device's disk, and neither sees the other's files; what is shared is
 this design.
 

harness/VERSION

@@ -1 +1 @@
-3.0.0-draft
+3.0.0

package.json

@@ -1,6 +1,6 @@
 {
   "name": "lembas-cli",
-  "version": "1.5.2",
+  "version": "2.0.0-beta.1",
   "description": "LLeMbas CLI: a terminal coding agent and project manager for a LLeMbas server — OpenTUI, memory, skills, MCP, git-native.",
   "license": "MIT",
   "private": true,