🐛 fix(server): preserve approval decision payloads across HTTP routes - #1428
🐛 fix(server): preserve approval decision payloads across HTTP routes#1428roninjin10 wants to merge 10 commits into
Conversation
|
❌ smithers review failed: 6 file reviews failed — run |
Automated code reviewReviewed 4 file(s) in the diff against
|
…pe rankings - select/rank validation rejects requests whose option entries were all dropped as malformed, instead of accepting arbitrary decisions - rank validation rejects mixed-type ranked arrays outright so the persisted decisionJson honors the string[] contract - re-export approvalDecision from the package index so TypeScript consumers can import it (regenerated index.d.ts) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
06ee7e8 to
2badce5
Compare
Co-Authored-By: Codex Sol <noreply@openai.com>
Co-Authored-By: Codex Sol <noreply@openai.com>
Co-Authored-By: Codex Sol <noreply@openai.com>
Co-Authored-By: Codex Sol <noreply@openai.com>
Co-Authored-By: Codex Sol <noreply@openai.com>
Co-Authored-By: Codex Sol <noreply@openai.com>
Co-Authored-By: Codex Sol <noreply@openai.com>
Co-Authored-By: Codex Sol <noreply@openai.com>
Closes #1421
Threaded approval decisions through legacy routes, added shared validation, regression tests, and API docs.
Filed from the aomi labs deep-dive (2026-07-27).
Pipeline: Fable investigated, Codex Luna implemented, Fable + Codex Sol both approved in a review loop, a human reviewed at the landing gate.
🤖 Generated with Claude Code