chore(release): 0.16.0 -- brackets reach the venue, and exits name their rule (#806)

MINOR, not a patch, because #805 ships schema v21: `positions.rule_id`. A deployment
must run `keel migrate` on every database before the new build trades, and the version
is the only signal an operator gets before reading the notes.

What lands:

  #804 (#802) -- bracket prices quantized to the venue tick, stop UP and target DOWN.
  Until now every protective bracket was rejected with "Too many decimals in order
  price", so the stop-loss and take-profit machinery had never fired on the live
  deployment at all. Nothing distinguished that from DCA's legitimate bracket-lessness.

  #805 (#803) -- `positions.rule_id`, so the protective SELL that exits a tranche names
  the rule that owns it. Both exit paths build their intent from a position, so every
  bracket, roll and scale-out was written unattributed while its entry carried the name.

Eight workspace versions and the fourteen inter-package `==` pins move together, plus the
refreshed `uv.lock` the workflow checks first.


Claude-Session: https://claude.ai/code/session_01AoGRoExgHVCsWDHT3ej8mD

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: eaitbrahim

packages/keel-broker-alpaca/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "keel-broker-alpaca"
-version = "0.15.1"
+version = "0.16.0"
 description = "Alpaca Trading API adapter for keel (US equities, cash account)"
 license = "Apache-2.0"
 requires-python = ">=3.14"
@@ -9,7 +9,7 @@ requires-python = ">=3.14"
 # deliberately NO `alpaca-py` SDK: Alpaca's Trading + Market Data APIs are plain
 # JSON-over-HTTPS with two header credentials, so the SDK would add a version-churning
 # dependency for nothing the port needs.
-dependencies = ["keel-core==0.15.1", "keel-broker-api==0.15.1", "requests>=2.32.0"]
+dependencies = ["keel-core==0.16.0", "keel-broker-api==0.16.0", "requests>=2.32.0"]
 
 [project.entry-points."keel.brokers"]
 alpaca = "keel_broker_alpaca:AlpacaAdapter"

packages/keel-broker-api/pyproject.toml

@@ -1,12 +1,12 @@
 [project]
 name = "keel-broker-api"
-version = "0.15.1"
+version = "0.16.0"
 description = "Broker port, domain types, capability model, and conformance suite for keel"
 license = "Apache-2.0"
 requires-python = ">=3.14"
 # Pinned `==`: see the note in the root `pyproject.toml`. An unpinned sibling is satisfied by
 # whatever is already installed, which is how a deployment ends up running mixed versions.
-dependencies = ["keel-core==0.15.1"]
+dependencies = ["keel-core==0.16.0"]
 
 [project.optional-dependencies]
 conformance = ["pytest>=9.1.1"]

packages/keel-broker-coinbase/pyproject.toml

@@ -1,12 +1,12 @@
 [project]
 name = "keel-broker-coinbase"
-version = "0.15.1"
+version = "0.16.0"
 description = "Coinbase Advanced Trade adapter for keel"
 license = "Apache-2.0"
 requires-python = ">=3.14"
 # Siblings pinned `==` (see the root `pyproject.toml`); the third-party SDK is not, because it
 # has its own release cycle and is not cut from this repo.
-dependencies = ["keel-core==0.15.1", "keel-broker-api==0.15.1", "coinbase-advanced-py>=1.8.4"]
+dependencies = ["keel-core==0.16.0", "keel-broker-api==0.16.0", "coinbase-advanced-py>=1.8.4"]
 
 [project.entry-points."keel.brokers"]
 coinbase = "keel_broker_coinbase:CoinbaseAdapter"

packages/keel-broker-fake/pyproject.toml

@@ -1,11 +1,11 @@
 [project]
 name = "keel-broker-fake"
-version = "0.15.1"
+version = "0.16.0"
 description = "A deliberately divergent second broker adapter, to keep the port honest"
 license = "Apache-2.0"
 requires-python = ">=3.14"
 # Pinned `==`: see the note in the root `pyproject.toml`.
-dependencies = ["keel-core==0.15.1", "keel-broker-api==0.15.1"]
+dependencies = ["keel-core==0.16.0", "keel-broker-api==0.16.0"]
 
 [project.entry-points."keel.brokers"]
 fake = "keel_broker_fake:FakeAdapter"

packages/keel-broker-kraken/pyproject.toml

@@ -1,13 +1,13 @@
 [project]
 name = "keel-broker-kraken"
-version = "0.15.1"
+version = "0.16.0"
 description = "Kraken adapter for keel (port-complete stub; every data/market method raises)"
 license = "Apache-2.0"
 requires-python = ">=3.14"
 # Siblings pinned `==` (see the root `pyproject.toml`). There is deliberately NO third-party
 # dependency: this package is a stub (#313) that handles no keys and makes no network calls,
 # so a Kraken SDK (and its credentials) arrive with the real implementation, not before it.
-dependencies = ["keel-core==0.15.1", "keel-broker-api==0.15.1"]
+dependencies = ["keel-core==0.16.0", "keel-broker-api==0.16.0"]
 
 [project.entry-points."keel.brokers"]
 kraken = "keel_broker_kraken:KrakenAdapter"

packages/keel-broker-robinhood/pyproject.toml

@@ -1,14 +1,14 @@
 [project]
 name = "keel-broker-robinhood"
-version = "0.15.1"
+version = "0.16.0"
 description = "Robinhood Crypto Trading API v2 adapter for keel"
 license = "Apache-2.0"
 requires-python = ">=3.14"
 # `pynacl` is here and nowhere else in the workspace: Robinhood signs every request with an
 # Ed25519 key, which no other venue keel talks to requires. Keeping it a dependency of this
 # package alone means an engine that never installs this adapter never installs the crypto stack
 # either -- the whole point of adapters being separate distributions.
-dependencies = ["keel-core==0.15.1", "keel-broker-api==0.15.1", "pynacl>=1.5.0", "requests>=2.32.0"]
+dependencies = ["keel-core==0.16.0", "keel-broker-api==0.16.0", "pynacl>=1.5.0", "requests>=2.32.0"]
 
 [project.entry-points."keel.brokers"]
 robinhood = "keel_broker_robinhood:RobinhoodAdapter"

packages/keel-core/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "keel-core"
-version = "0.15.1"
+version = "0.16.0"
 description = "Shared domain types, configuration, and logging for keel"
 license = "Apache-2.0"
 requires-python = ">=3.14"

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "keel-trader"
-version = "0.15.1"
+version = "0.16.0"
 description = "Offline-first, broker-agnostic, rule-based spot-trading agent (halal policy by default)"
 license = "Apache-2.0"
 readme = "README.md"
@@ -23,15 +23,15 @@ dependencies = [
     # in one build, so `==` states a fact rather than guessing at compatibility. The cost is that
     # a version bump must move these numbers too -- the bump already edits every package's
     # `version`, and `tests/test_packaging.py` fails the build if a pin is left behind.
-    "keel-core==0.15.1",
-    "keel-broker-api==0.15.1",
+    "keel-core==0.16.0",
+    "keel-broker-api==0.16.0",
     # The default venue resolves through the keel.brokers entry points (#524), so the adapter
     # is a hard runtime dependency, not a convenience: without it installed, every config --
     # including one with no `broker:` section -- fails at broker construction. The CLI also
     # imports the SDK directly to build the adapter's RESTClient transport
     # (`keel/commands/_common.py`); moving that construction into the adapter package is
     # Phase B's, with cb_client.py's deletion.
-    "keel-broker-coinbase==0.15.1",
+    "keel-broker-coinbase==0.16.0",
 ]
 
 [project.scripts]