v0.15.0: changelog and README

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

CHANGELOG.md

@@ -19,12 +19,36 @@ is only released once its **exit criterion** is met, not when its code lands.
 | v0.12.0 | — | The cluster's settings in the store, in force when changed; the firewall switch; wipe | released |
 | v0.13.0 | — | The whole system stopped and started from one command; Qwen3Guard judges, on a GPU and CPUs together | released |
 | v0.14.0 | — | Knowledge bases: documents from people's own machines, kept apart per tenant, answered from | released (v0.14.1: adapters, the tree over the API, the firewall on every machine; v0.14.2: pictures from ComfyUI; v0.14.3: 3D models as jobs; v0.14.4: any ComfyUI workflow as a job, presets, licences; v0.14.5: picture and 3D models that add themselves; v0.14.6: setup that explains every part and lets it be chosen, the gateway on all three HA machines; v0.14.7: the judge sized for its machine; v0.14.8: sign-in with Active Directory, several keys for one outside provider; v0.14.9: sign-in set up from the console, a node's console that shows the machine) |
+| v0.15.0 | — | The company's MCP tools and VS Code through the gateway; guardrails that ask outside services and put redacted values back; answers to similar questions | released |
 | v1.0.0 | 5 | What phase 5 has left: precise KV routing proven on vLLM, the block cost picker, defragmentation across NVLink domains, prefill/decode disaggregation | planned |
 
 Until v1.0.0 the minor version is the breaking one: configuration formats and Go
 APIs change between minors without a deprecation period.
 
-## Unreleased
+## v0.15.0 — 2026-10-25
+
+The company's tools and editors through the gateway, and guardrails that
+can lean on others. Its own MCP servers sit behind llmgw's `/mcp` under the
+guardrails, a rate and a breaker. VS Code gets the gateway's models from an
+extension the gateway serves. A guardrail policy can ask an outside
+service, and can put redacted values back in the answer. Chat goes to the
+replica answering soonest. A similar question can get the answer already
+given. A cached prompt can be priced apart. Traces follow the OpenTelemetry
+GenAI conventions, and Kong is written down from trying it. Also an install
+guide with every screen, at `/install`.
+
+**Upgrading.**
+- Migrations 0049 (`mcp_servers`), 0050 (their rate and breaker) and 0051
+  (`projects.cache_similar`), applied when the control plane starts.
+- `llmgw server init` now refuses a machine that would serve models without
+  the memory for them: the starter model and the judges need 12 GB on one
+  machine, where 8 GB was said before. `--no-model`, `--no-guard-model` or
+  `--no-node` make it fit. A running cluster is not checked again.
+- Traces carry the GenAI conventions' `gen_ai.*` attributes beside the
+  `llmgw.*` ones, which stay; docs/install.md, "Tracing", lists them.
+- Nothing else changes until it is turned on: `services` and `restore` in a
+  guardrail policy, `keys cache --similar` with
+  `router.cache.embedding_model`, `cached_per_1k` in a price.
 
 ### Added
 

README.md

@@ -41,6 +41,7 @@ Releases track the roadmap phases; see [CHANGELOG.md](CHANGELOG.md).
 | v0.12.0 | — | The cluster's settings in the store, in force when changed; the firewall switch; wipe | released |
 | v0.13.0 | — | The whole system stopped and started from one command; Qwen3Guard judges, on a GPU and CPUs together | released |
 | v0.14.0 | — | Knowledge bases: documents from people's own machines, kept apart per tenant, answered from | released (v0.14.1: adapters, the tree over the API, the firewall on every machine; v0.14.2: pictures from ComfyUI; v0.14.3: 3D models as jobs; v0.14.4: any ComfyUI workflow as a job, presets, licences; v0.14.5: picture and 3D models that add themselves; v0.14.6: setup that explains every part and lets it be chosen, the gateway on all three HA machines; v0.14.7: the judge sized for its machine; v0.14.8: sign-in with Active Directory, several keys for one outside provider; v0.14.9: sign-in set up from the console, a node's console that shows the machine) |
+| v0.15.0 | — | The company's MCP tools and VS Code through the gateway; guardrails that ask outside services and put redacted values back; answers to similar questions | released |
 | v1.0.0 | 5 | What phase 5 has left: precise KV routing proven on vLLM, the block cost picker, defragmentation across NVLink domains, prefill/decode disaggregation | planned |
 
 As of v0.6.0 a cluster runs unattended: agents report their hardware, the