chore(release): 0.12.1

[eaitbrahim]

What this is

The version-bump PR for 0.12.1, following #591'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.0 the only user-facing change is #594, and #592 ships no runtime code. No new interfaces, so the patch is right.

What ships in 0.12.1

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

• feat(web): the browser UI wears keeltrading.com's identity #594 — the browser UI wears keeltrading.com's identity (The browser UI wears keeltrading.com's identity — same palette, same logo #593): the UI wears keeltrading.com's palette; the keeltrading.com mark lands on every icon; the hull closes and the caps land — the mark is the site's, measured.
• fix(release): the Windows attestation subjects are newline-separated, not space-separated #592 — the release-workflow attestation fix: the Windows attestation subjects are newline-separated, not space-separated (the space-separated form is one path to the action, and the v0.12.0 dispatch failed at exactly that step). Workflow-only; no runtime code ships.
• Everything else since v0.12.0 is docs (docs(analysis-feed): the Analyzer proposes, the gate decides #579's analysis-feed decision record).

Files bumped

• pyproject.toml — version 0.12.0 → 0.12.1, 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.0 finds only inert prose — the example ISCC.exe /DKeelVersion=0.12.0 invocation comment in packaging/keel.iss (the real value is passed as a define by the workflow; the #ifndef default is 0.0.0), and the two comments narrating the historical v0.12.0 attestation dispatch failure in tests/test_desktop_packaging.py and .github/workflows/release.yml. No live pins or expectations 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.0'; it must be 'keel-core==0.12.1'

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 — 4422 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.