chore(release): 0.14.0 — the honest cockpit, and a book that can prove it was not edited

[eaitbrahim]

Version bump only. Thirty-seven PRs since 0.13.3.

⚠️ This release carries four schema migrations

v0.13.3 shipped SCHEMA_VERSION = 16. This release is 20, so an upgraded deployment applies four steps, not one:

	adds
v17	candle_series_feed (#696)
v18	venue_cash_postures (#666)
v19	equity_points (#698)
v20	orders.quote_provenance, orders.client_order_id, attest_due_ts on both attestation tables, cycle_balances, audit_events (#721)

keel serve migrates for you, once, at bind time (server.ensure_schema) — a missing database is left alone as a first run. What it deliberately does not do is migrate per request: the pages auto-reload every 15 seconds, and a view calling itself read-only must not take a schema write lock on a database the agent may be mid-cycle on, four times a minute.

keel mcp does not migrate at all (keel/mcp/tools.py), and against a database still at v16–v17 its doctor tool raises sqlite3.OperationalError: no such table: venue_cash_postures rather than reporting the gap. Only the audit chain carries a table_present guard; the cash-posture and equity readers do not. Tracked in #751 — run keel migrate before pointing an MCP client at an upgraded deployment.

The honest cockpit (#700–#708)

Positions, Balances, Activity, Orders, the Research Hub's four views, session identity on every page, and an inverted Plans page.

The pattern underneath all of it: a view was built against a record the engine didn't keep, and the fix was always in the engine. #703's audit export said NOT RECORDED in every hash cell until #721 chained the book. #708's Evidence Matrix couldn't exist until #726 stopped throwing away what trials pbo computed.

What the engine now writes down

• An append-only, hash-chained record of every write to orders, transactions and the attestation tables ([engine] Append-only SHA-256 hash chaining for orders, transactions and attestations #721) — the activity export carries real hashes and a per-row verdict on whether the chain vouches for them
• Quote provenance and client order id behind each placement ([engine] Schema v20: persist quote_provenance and client_order_id on orders, at placement #715)
• When an attestation's window closes ([engine] Record an attestation window: attest_due_ts on asset_attestations and instrument_attestations #718)
• The per-currency balance pair a cycle observed ([engine] Persist the per-currency settled/available/total balance pair into the cycle snapshot #719)
• The full CSCV, DSR and Monte Carlo artifacts a gauntlet run produces (Engine: persist comprehensive gauntlet artifacts (Monte Carlo quantiles, DSR inputs and score, full CSCV result) when the gauntlet runs #726)

Two new operator surfaces

keel journal — the discretionary journal, wired at last after sitting in the schema unused since the beginning. CLI-only by constitution: no web form, and add takes no value options, so an entry can't be scripted past the terminal gate.

keel orders cancel — the cancel asymmetry. Cancelling an entry refuses risk and asks once; cancelling an exit or protective bracket removes protection and takes a typed phrase naming the order. The console classifies and hands over the command; it never cancels, because keel serve holds no venue credential and this release doesn't change that.

One behaviour change to know about

A deployment that has never attested a cash posture now sends a webhook event, if notifications are on. attest.cash_posture was registered for delivery and nothing produced it (#732) — so rail 22 could veto every entry while the operator heard nothing.

Checks

pyproject.toml and all seven workspace packages moved together, uv.lock refreshed (#424). 6,305 passed / 3 skipped; ruff clean apart from a pre-existing E501 in docs/experiments/.

After merge: Actions → Release → Run workflow, entering 0.14.0.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KZZxmspQXe5qJ9FAsG13s6