Repository navigation
Conversation
Signed-off-by: Yufeng He <40085740+he-yufeng@users.noreply.github.com>
|
@warren618 Could you review the shared-grid boundary and the pair-at-a-time UI choice? The route delegates directly to the comparison tool merged in #2199. OptionsLab already permits the current strategy plus five alternatives, so the component compares any selected pair in original input order and maps The completed-snapshot behavior is covered by page-level tests, and an independent replay passed 67 backend tests, 147 frontend tests and the production build. Does the pair-at-a-time interaction fit the intended Web comparison contract? |
Summary
POST /options/strategy-compareas a thin HTTP adapter over the acceptedOptionsStrategyCompareToolused by Agent and MCP.Why
Related: #2202
Saved alternatives already share expiry curves and return metrics, but the Web UI has no way to inspect how two strategies differ across the same spot and volatility grid. This adds the roadmap's Web comparison view without reimplementing payoff mathematics in TypeScript or ranking strategies.
Changes
OptionsStrategyCompareTool, preserving strategy order andbaseline_indexsemantics.No live broker, order, payment, wallet, credential, deployment or real market-data path is changed.
Test Plan
Validation on the original candidate and an independent replay from
6ed378dee5a6e6eb87df796a6546c8ca972a8281:git diff --check, repository grep gates and private-files gate: passed.Ruff format and Black report existing whole-file formatting debt on both the unmodified baseline and this candidate, so no unrelated reformatting is included.
Checklist
src/agent/,src/session/,src/providers/).