chore: bump to 0.6.0

[eaitbrahim]

Bumps the root distribution and all five workspace packages to 0.6.0, and refreshes uv.lock. Same file set as the 0.5.7 bump (#191), plus keel-broker-robinhood, which did not exist then.

release.yml refuses to publish unless pyproject.toml already carries the version being released, so this must merge before the release is dispatched.

Labelled norelease so the bump itself does not appear in its own release notes.

Why minor, not patch

1. Schema migration. SCHEMA_VERSION 9 → 10 (#223). Both deployed databases are at 9 and must be migrated before this build can use them.

2. Behaviour requiring operator action. #223 adds a second attested claim — what contract a venue listing is, not only what the underlying asset is. It fails closed with no backfill, deliberately, so after this lands keel assets screen REJECTS every product — BTC-USD included — with instrument_wrapper: UNATTESTED until keel assets attest-instrument is run once per product. Live trading is unaffected: rail 1 gates buys on config.allowlist, not on the screen.

3. Live scoring changed. #227 fixed is_round_number, which returned True for every 2dp-quoted price and handed BTC/ETH/PAXG a free CTS point on every bar. Scores on those three are genuinely lower under this build than under 0.5.7.

Gates, run locally on this branch

ruff              All checks passed!
mypy              Success: no issues found in 221 source files
pytest            2664 passed, 1 skipped
migration_smoke   fresh and downgraded both reach schema 10
live template     mode=confirm  (the assertion release.yml makes before publishing)

Deploy sequence after this merges

1. Dispatch release.yml with 0.6.0
2. Back up both DBs, then keel migrate each (9 → 10)
3. Install the wheel per the README's deployment flow
4. keel assets attest-instrument once per allowlisted product, or the screen stays red