release api/v1.2.0

Webber through the boilerroom wrapper: flavor-adaptive tool_choice,
session identity at rank 20, and the sanitized-client wiring fix
that makes the choke point real.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

webber-api/CHANGELOG.md

@@ -7,6 +7,37 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.2.0] - 2026-09-13
+
+### Added
+
+- Backend adaptation at the provider choke point (workspace T-137):
+  the local backend's flavor is probed once — the boilerroom wrapper
+  names itself on `/health`, a bare llama-server serves `/props`,
+  Ollama answers neither — and every completion adapts. The agents'
+  `tool_choice: "required"` survives only on Ollama, where it is a
+  useful advisory nudge; llama-server enforces it per request, which
+  through the wrapper is an unbreakable tool loop. Through the wrapper
+  every completion carries webber's session identity —
+  `session: webber`, `eviction_order: 20` per the decided ranking
+  (tatlock phases 40, experts 35, librarian 30; lower parks sooner),
+  configurable via `BACKEND_SESSION_NAME`/`BACKEND_SESSION_RANK` —
+  and the wrapper's `balancing`/`compaction_due` body signals are
+  logged. A transport failure during the probe answers "ollama"
+  without caching, so a backend that was down at first call is
+  re-probed rather than misclassified forever.
+
+### Fixed
+
+- The sanitized OpenAI client was never used: the provider assigned
+  `self._openai_client`, an attribute nobody reads —
+  `OllamaProvider.client` serves `self._client`. Every completion
+  bypassed the null-content sanitizer since the class was introduced;
+  exposed 2026-09-13 when the wrapper 503'd a session-less request
+  that the choke point should have named. The sanitized client now
+  goes through the constructor's official `openai_client` parameter,
+  and a wiring test pins `provider.client` to the sanitized type.
+
 ## [1.1.0] - 2026-08-11
 
 ### Added