chore(release): 0.12.2

[eaitbrahim]

What this is

The version-bump PR for 0.12.2, following #596's precedent exactly: one commit, every version and every == pin moves together, uv.lock moves with them. Per docs/RELEASING.md, merging this (not the workflow) is what sets the version — the release workflow then refuses to change it.

Patch, not a minor: since v0.12.1 the only user-facing change is #598. No new interfaces, so the patch is right.

What ships in 0.12.2

Enumerated from git log --oneline v0.12.1..HEAD:

• feat(web): the header is a brand, not a word — mark, home, theme choice, mode badge #598 — the header is the brand, not a word (The header is a brand, not a word: logo, click-to-home, theme toggle, and a mode badge #597): the web UI's header carries the keeltrading.com mark as the home link, a theme toggle (light/dark choice), and a mode badge; the right cluster keeps its margin when the badge degrades, and the mark pin covers rx and stroke-width. Test-first (The header is a brand, not a word: logo, click-to-home, theme toggle, and a mode badge #597's 799ed11 pinned the header brand, toggle, and mode badge before the feature landed).
• Nothing else since v0.12.1 — the log is exactly that one PR's commits plus its merge.

Files bumped

• pyproject.toml — version 0.12.1 → 0.12.2, plus the three sibling pins (keel-core, keel-broker-api, keel-broker-coinbase)
• packages/{keel-core,keel-broker-api,keel-broker-coinbase,keel-broker-alpaca,keel-broker-fake,keel-broker-robinhood,keel-broker-kraken}/pyproject.toml — each version, plus the 11 inter-package == pins
• uv.lock — regenerated with uv lock; diff is exactly 8 lines (one version per distribution), no unrelated churn; uv lock --check passes

9 files, 25 insertions, 25 deletions. Nothing else: a repo-wide grep for 0.12.1 (excluding uv.lock) finds no live pins, expectations, or even inert prose left behind.

Lock discipline

The trap from #422/#482, verified TDD-style: bumping only the root pyproject.toml's version first made tests/test_packaging.py fail exactly as designed —

FAILED tests/test_packaging.py::test_every_workspace_package_carries_the_same_version
FAILED tests/test_packaging.py::test_workspace_siblings_are_pinned_to_the_exact_version[keel-trader]
  keel-trader depends on 'keel-core==0.12.1'; it must be 'keel-core==0.12.2'

After completing the set (all 8 pyprojects, 14 pins, uv lock), the same suite is green. uv.lock rides in the same commit because the release workflow checks it is current before anything else (#424).

Gates

• uv run pytest tests/test_packaging.py -q — 22 passed
• uv run pytest -q — 4437 passed, 3 skipped
• uv run ruff check . — all checks passed
• uv run mypy — no issues in 350 source files

Do not merge unreviewed: the release workflow runs next, after merge, with this same version.