chore(release): 0.10.0

[eaitbrahim]

Step 1 of docs/RELEASING.md: the version bump, in a reviewed PR, because the release workflow refuses to change the version itself.

Why minor and not patch

Three things since v0.9.3 change what an implementor or a deployment can rely on:

• A new distribution. keel-broker-alpaca (feat(broker-alpaca): keel-broker-alpaca — original Alpaca port adapter, conformance green #382, fix(broker-alpaca): NaN-safe money coercion, host-map-only construction, quoted path segments #384) and the paper-equities profile that selects it (feat(paper-equities): the equities paper profile — tracked config, venue selection, deployment artifacts, runbook (#370 B2) #386) — a deployment can now be US equities via the broker port, not crypto only.
• The port contract moved twice. market_clock/market_schedule made venues session-aware (feat(port): session-aware venues — market clock in the port, closed-session semantics in the engine (#370 B1) #385); place_order gained idempotency_key (feat(brokers): give the port an idempotency key so a placement retry is safe #419). Both carry defaults so no caller breaks, but a third-party adapter that doesn't accept them is no longer a Broker — the conformance suite now says so. A patch bump must not hide that.
• The operator console. The TUI became keel's console across refactor(cli): extract command bodies into the shared service layer (#387 C1) #399–feat(tui): the console completed — account menu, ceremony audit, thinness pin, runbook (#392 C6) #408, and keel update (Self-update: pull the latest release, deploy into the launch folder, relaunch the TUI #415/feat(update): self-update — pull, deploy into the launch folder, relaunch (#415) #417) makes a deployment self-updating.

Every pin moves with it

All seven distributions, and the == cross-pins:

keel-trader        0.9.3 -> 0.10.0   (+ 3 pinned deps)
keel-core          0.9.3 -> 0.10.0
keel-broker-api    0.9.3 -> 0.10.0   (+ 1)
keel-broker-coinbase                 (+ 2)
keel-broker-alpaca                   (+ 2)
keel-broker-robinhood                (+ 2)
keel-broker-fake                     (+ 2)

The four production distributions are required == at the same version (RELEASING.md, "Release assets"), so a bump that missed one installs a mixed set — the keel-trader 0.5.7 against keel-core 0.5.5 failure keel versions exists to catch, and which ~/keel actually ran across two releases. No 0.9.3 remains anywhere in the workspace.

Verified

Full suite 3797 passed, 3 skipped. ruff check clean.

After merge

Actions → Release → Run workflow, entering 0.10.0. The workflow validates the input against pyproject.toml, runs tests + ruff, stamps the commit, builds all packages, installs into a clean venv by path and asserts a clean [release] identity, verifies the live config asset is mode: confirm, tags v0.10.0, and publishes.

One stale doc, not fixed here

RELEASING.md's asset table predates keel-broker-alpaca — it lists six distributions and describes the fake and Robinhood wheels as published-but-not-deployed, with no row for Alpaca. uv build --all-packages will build and publish it regardless, and keel versions discovers distributions from installed metadata rather than a hardcoded list, so nothing is functionally wrong. Worth a follow-up rather than scope in a release bump — particularly since keel update downloads exactly four production wheels, which means the equities profile is not self-updatable today.

🤖 Generated with Claude Code