trade-evaluationlisted

# Trade Evaluation: Two-Sided Assessment Judge a specific trade from **both** rosters' perspectives. Raw player value is the start, not the verdict — value only counts when it reaches a starting lineup. ## Step 1: Load context Read `leagues.md` from the project root first — the fields that matter here are scoring, starting slots, roster/bench size, playoff weeks, trade deadline, and whether trades face a veto vote. If the file is missing or blank, ask and suggest running `fantasy-league-setup:league-config`. If more than one league is defined, use the one marked `(default)`. Gather both full rosters, both records/standings, and the exact terms. Without the other team's roster only half an evaluation is possible — say so and evaluate provisionally. For any in-season evaluation, make the timing explicit: - State the verdict **as of** a concrete date/time. - Refresh injuries, suspensions, depth-chart changes, and any same-week news if the inputs are stale or undated. Trade advice that turns on a Tuesday hamstring report should not be delivered as if it were timeless. - For any consequential injury-based value swing, require **both** the official team/game status and a second credible source. One unsupported report is not enough to move a player multiple tiers. ## Step 2: Who originated the offer? — ask this first **An incoming offer is adversely selected.** The proposer built it after looking at both rosters and concluded it helps them. That is not bad faith; it is what