chore: release v0.20.0

Author: claude

Formula/slmcode.rb

@@ -9,7 +9,7 @@
 class Slmcode < Formula
   desc "Coding harness for SLMs and any OpenAI-compatible LLM — building blocks, language packs, Studio UI"
   homepage "https://unicolab.ai"
-  version "0.19.1"
+  version "0.20.0"
   license "MIT"
 
   # ── About the sha256 values below ────────────────────────────────────────
@@ -42,22 +42,22 @@ class Slmcode < Formula
   on_macos do
     on_arm do
       url "https://github.com/UnicoLab/smlcode/releases/download/v#{version}/slmcode_#{version}_darwin_arm64"
-      sha256 "9da45f2fb51bed02a13d4dc3a3cddc8edd46c8944d19dc6907ae8f97e4a1e1ae" # v0.19.1
+      sha256 "0000000000000000000000000000000000000000000000000000000000000000"
     end
     on_intel do
       url "https://github.com/UnicoLab/smlcode/releases/download/v#{version}/slmcode_#{version}_darwin_amd64"
-      sha256 "91314d8caf6696798dd0c5eab61cdb016ce25da4ff30ad5c5fa22b9a31e3df3e" # v0.19.1
+      sha256 "0000000000000000000000000000000000000000000000000000000000000000"
     end
   end
 
   on_linux do
     on_arm do
       url "https://github.com/UnicoLab/smlcode/releases/download/v#{version}/slmcode_#{version}_linux_arm64"
-      sha256 "859fa23c74573f1101c22821292eedf2a4d214abed2a17b3afd16a2c8b941024" # v0.19.1
+      sha256 "0000000000000000000000000000000000000000000000000000000000000000"
     end
     on_intel do
       url "https://github.com/UnicoLab/smlcode/releases/download/v#{version}/slmcode_#{version}_linux_amd64"
-      sha256 "202709cec061d0f072cc14555e5493216f37389604c584e713b9a57866d016f0" # v0.19.1
+      sha256 "0000000000000000000000000000000000000000000000000000000000000000"
     end
   end
 

Makefile

@@ -1,6 +1,6 @@
 MODULE := github.com/UnicoLab/slmcode
 BIN    := slmcode
-VERSION ?= 0.19.1
+VERSION ?= 0.20.0
 PREFIX ?= $(HOME)/.local
 GIT_COMMIT := $(shell git rev-parse --short HEAD 2>/dev/null || echo unknown)
 BUILD_TIME := $(shell date -u +%Y-%m-%dT%H:%M:%SZ)

RELEASE.md

@@ -63,8 +63,8 @@ generated commit-subject dump is a fallback for patch releases, not a substitute
 ## 1. Bump, gate, commit and tag
 
 ```bash
-scripts/prepare-release.sh 0.19.1 --dry-run     # look at the diff; nothing is committed
-scripts/prepare-release.sh 0.19.1               # for real
+scripts/prepare-release.sh 0.20.0 --dry-run     # look at the diff; nothing is committed
+scripts/prepare-release.sh 0.20.0               # for real
 ```
 
 What it does, in order:
@@ -78,15 +78,15 @@ What it does, in order:
 5. Runs `scripts/check-version.sh --tag vX.Y.Z`, `scripts/check-repo-refs.sh`, `make check`.
 6. Commits `chore: release vX.Y.Z` and creates the tag. **It does not push.**
 
-For **v0.19.1 specifically**, the version and the changelog entry are already in the tree,
+For **v0.20.0 specifically**, the version and the changelog entry are already in the tree,
 so the script reports *"No file changes needed — proceeding as a tag-only release"*, runs
 the gate, and creates the tag with no release commit. That is correct.
 
 Review before pushing:
 
 ```bash
 git show --stat HEAD
-git tag -v v0.19.1 2>/dev/null || git show v0.19.1 --stat | head
+git tag -v v0.20.0 2>/dev/null || git show v0.20.0 --stat | head
 ```
 
 ---
@@ -95,7 +95,7 @@ git tag -v v0.19.1 2>/dev/null || git show v0.19.1 --stat | head
 
 ```bash
 git push origin main
-git push origin v0.19.1          # this is what starts the release
+git push origin v0.20.0          # this is what starts the release
 ```
 
 Pushing the tag is the point of no return for the automation. Everything before it is
@@ -131,10 +131,10 @@ served "Studio not built" to every user without failing.
 Published artifacts:
 
 ```
-slmcode_0.19.1_darwin_arm64      slmcode_0.19.1_windows_amd64.exe
-slmcode_0.19.1_darwin_amd64      slmcode_0.19.1_windows_arm64.exe
-slmcode_0.19.1_linux_arm64       install.sh  install.ps1  install.cmd
-slmcode_0.19.1_linux_amd64       SHA256SUMS
+slmcode_0.20.0_darwin_arm64      slmcode_0.20.0_windows_amd64.exe
+slmcode_0.20.0_darwin_amd64      slmcode_0.20.0_windows_arm64.exe
+slmcode_0.20.0_linux_arm64       install.sh  install.ps1  install.cmd
+slmcode_0.20.0_linux_amd64       SHA256SUMS
 ```
 
 ---
@@ -147,18 +147,18 @@ CI verifies the bytes. These are the things only a human on a real machine can c
 
 ```bash
 cd "$(mktemp -d)"
-curl -fsSLO https://github.com/UnicoLab/smlcode/releases/download/v0.19.1/SHA256SUMS
-curl -fsSLO https://github.com/UnicoLab/smlcode/releases/download/v0.19.1/slmcode_0.19.1_darwin_arm64
+curl -fsSLO https://github.com/UnicoLab/smlcode/releases/download/v0.20.0/SHA256SUMS
+curl -fsSLO https://github.com/UnicoLab/smlcode/releases/download/v0.20.0/slmcode_0.20.0_darwin_arm64
 shasum -a 256 -c SHA256SUMS --ignore-missing        # must say OK
-chmod +x slmcode_0.19.1_darwin_arm64
-./slmcode_0.19.1_darwin_arm64 version --json        # version 0.19.1, real commit, real built
+chmod +x slmcode_0.20.0_darwin_arm64
+./slmcode_0.20.0_darwin_arm64 version --json        # version 0.20.0, real commit, real built
 ```
 
 **The install one-liner, on a machine that has never had slmcode:**
 
 ```bash
 curl -fsSL https://raw.githubusercontent.com/UnicoLab/smlcode/main/scripts/install-remote.sh | bash
-slmcode version                                     # 0.19.1
+slmcode version                                     # 0.20.0
 slmcode doctor
 ```
 
@@ -174,7 +174,7 @@ cd "$(mktemp -d)" && slmcode init && slmcode studio
 # "Studio not built" means CI shipped a placeholder: pull the release (step 6 below).
 ```
 
-**Homebrew** — only after the `chore: sync Homebrew formula checksums for v0.19.1`
+**Homebrew** — only after the `chore: sync Homebrew formula checksums for v0.20.0`
 commit has landed on `main` (CI step 14). Before that, the formula carries all-zero
 placeholder checksums and `brew install` will refuse; that is expected, not a break-in.
 
@@ -193,15 +193,15 @@ slmcode version
 ```
 
 Confirm `-> Checksum OK (sha256 …)` appears. This path had no checksum verification at all
-before 0.19.1, so it is worth watching once.
+before 0.20.0, so it is worth watching once.
 
 **Self-update from the previous release:**
 
 ```bash
 # on a machine still running 0.16.0
-slmcode update --check      # must report v0.19.1 is available
+slmcode update --check      # must report v0.20.0 is available
 slmcode update --yes
-slmcode version             # 0.19.1
+slmcode version             # 0.20.0
 ```
 
 ---
@@ -213,11 +213,11 @@ slmcode version             # 0.19.1
   The four `sha256` lines should now read `sha256 "<hex>" # vX.Y.Z` with X.Y.Z equal to the
   release you just cut — that label is what `check-version.sh` gates on, and the reason a
   rebase can no longer leave the previous release's digests under the new version line
-  (which is exactly what happened between v0.18.3 and v0.19.1).
+  (which is exactly what happened between v0.18.3 and v0.20.0).
 - Confirm the docs site rebuilt (`.github/workflows/docs.yml`) and that
   [Install](docs/install.md), [Migration notes](docs/migration.md) and
   [Changelog](docs/changelog.md) render.
-- Announce the **breaking behaviour changes**, not the feature list. For 0.19.1 those are:
+- Announce the **breaking behaviour changes**, not the feature list. For 0.20.0 those are:
   hooks fail closed, project `mcp_servers` ignored, the tiered shell allowlist,
   `slmcode apply` interactive, HITL gates blocking when attended, the Studio session token,
   and the new `.slmcode/memory` + `.slmcode/evolve` directories.
@@ -229,15 +229,15 @@ slmcode version             # 0.19.1
 **Before the tag is pushed** — nothing has happened:
 
 ```bash
-git tag -d v0.19.1
+git tag -d v0.20.0
 git reset --hard origin/main
 ```
 
 **After the tag is pushed but CI failed** — no release exists, so just fix and re-tag:
 
 ```bash
-git push --delete origin v0.19.1
-git tag -d v0.19.1
+git push --delete origin v0.20.0
+git tag -d v0.20.0
 # fix, commit, then repeat from step 1
 ```
 

cmd/slmcode/version.go

@@ -4,7 +4,7 @@ package main
 //
 //	go build -ldflags "-X main.Version=0.5.0 -X main.SourceRoot=/path -X main.GitCommit=abc -X main.BuildTime=…"
 var (
-	Version    = "0.19.1"
+	Version    = "0.20.0"
 	SourceRoot = "" // absolute path to the slmcode checkout used to build this binary
 	GitCommit  = "unknown"
 	BuildTime  = "unknown"

docs/install.md

@@ -87,7 +87,7 @@ One-liners fetch a shiny GitHub Release. Keep the compiler for contributing (or
 
     ```bash
     curl -fsSL https://raw.githubusercontent.com/UnicoLab/smlcode/main/scripts/install-remote.sh \
-      | bash -s -- --version v0.19.1
+      | bash -s -- --version v0.20.0
     ```
 
 === "🪟 PowerShell"
@@ -126,7 +126,7 @@ fetched, the installer says so loudly rather than pretending it checked.
 To check by hand, or to verify a binary you downloaded from the Releases page:
 
 ```bash
-curl -fsSLO https://github.com/UnicoLab/smlcode/releases/download/v0.19.1/SHA256SUMS
+curl -fsSLO https://github.com/UnicoLab/smlcode/releases/download/v0.20.0/SHA256SUMS
 shasum -a 256 -c SHA256SUMS --ignore-missing     # macOS
 sha256sum -c SHA256SUMS --ignore-missing         # Linux
 ```